Daily research report

Report —

Result of

Result None

0 qualified of 3 requested · 5 examined

No new role cleared every hard gate on October 31. Five postings were examined. Two are near-misses because no salary is published: GitGuardian’s Senior Software Engineer, AI (Paris, three office days a week, stock options; AI is one of several duties) and Remanence’s Member of Technical Staff for agent training environments and evaluations (clearly AI-central, but no pay or attendance rule is published). Three were rejected: n8n’s new Forward Deployed Engineer – EMEA and Vanta’s Staff Software Engineer, AI and Data Risk both exclude France, and Mistral AI’s crashworthiness AI Scientist is a simulation-domain-expert role. Earlier picks and near-misses that are unchanged are not repeated. These entries are research leads, not recommendations.

DecisionNo approval needed for this authorized daily website update. Zero new roles qualified today. GitGuardian and Remanence would need an employer-published salary (and, for Remanence, an attendance rule) before reconsideration. No applications or outreach were made.

Zero roles passed every recorded gate on 2026-10-31. The entries below are research leads, not recommendations.

Uncertainty & caveats

  • Sources checked October 31, 2026. Posting dates come from employer ATS metadata or structured data on the employer’s page.
  • Unpublished pay is recorded as unknown, not as below the threshold. Neither near-miss publishes a salary on the employer’s own page.
  • n8n’s Agentic Engineering Platform Engineer (October 30 rejection) is unchanged: same pay tiers, and France is still absent from its location list. It is not repeated.
  • Qonto’s Staff Software Engineer, AI Agents (Python) (October 28 near-miss) is still listed with no compensation data. Inato’s Senior AI Engineer (October 26 pick) and Pigment’s Senior GenAI Engineer (October 10 pick) are still listed with unchanged ranges. They stay in their original archives and are not counted today.
  • Shift Technology’s Lead AI Engineer and Staff AI Engineer remain listed on the official board and were not re-examined in depth. Dust’s on-site solutions-engineering leadership role (October 20 rejection) has been retitled Global Head of Solutions Engineering with the same requisition ID; it is not repeated.
  • Search-result leads not found on employer boards today (recruiter posts and third-party listings with salary figures) were not counted.
  • Deduplication covered the accessible October 10–30 reports and the supplied October 3/5 Escape history.
  • Company financial diligence was not advanced because no role was ranked; GitGuardian’s funding note is employer-stated only.
  • Independent recheck: every entry reflects checks made on 2026-10-31. Confirm the listing, pay and eligibility on the employer’s own pages before acting.
Search coverage

Automated official-ATS sweep on October 31: 132 of 276 attempted Ashby, Lever and Greenhouse board aliases returned data; many failed aliases are likely wrong board names, not evidence of no vacancies. The sweep screened AI-titled roles on reachable boards, Paris- or France-located engineering roles with published pay on reachable Ashby boards, and Greenhouse and Lever data for 111 France-located engineering roles (31 with pay text). It also screened Ashby engineering roles first published since October 28 with a France or Europe-remote location. A second pass reached 43 of 300 attempted aliases, and a Workable and Recruitee check reached 6 of 44. Eight web searches were used for discovery only; leads found there were checked against employer boards, which added the GitGuardian careers site and the Remanence Ashby board. Coverage is bounded, not exhaustive.

Criteria applied
  • Paris hybrid with explicit attendance, or fully remote explicitly allowing France-based applicants.
  • Senior/staff hands-on AI-central engineering; an AI employer, coding assistant use or AI product UI alone does not establish the required assignment.
  • Employer-published annual gross cash-base lower bound strictly above €100,000, or at least €80,000 with explicit equity. Use the lower bound; equity is not cash; packages, OTE, unlabelled pay ranges and estimates do not pass.
  • No unchanged prior selections. Requisition identity takes precedence over refreshed titles, URLs or timestamps; historical qualification is not current-live verification.

Filter entries

Showing 5 of 145 entries

JavaScript is off: all 145 entries from every report date are listed below.

Qualified matches

Entries whose stored gates all passed on their report date. Historical checks — not a live availability guarantee.

No role passed every recorded gate in the 2026-10-31 report. The research leads below are not recommendations.

Research leads

Rejected and near-miss entries kept for research. These are not recommendations.

GitGuardian

Senior Software Engineer, AI

Near-miss

Report date
Evidence checked
Posted
Work location
Hybrid — Official listing: “ENGINEERING · PARIS · HYBRID” and “Remote policy: hybrid (3 days/week at the office in Paris)”.[1]
Salary evidence
No published figures
Equity
Yes

Pay noteNo salary range is published. The listing states “Package that includes stock-options”. Pay is unknown, not below the threshold.[1]

Recorded gates (as checked on the report date)

  • Listing openpass
  • Locationpass
  • AI-centralunknown
  • Payunknown
  • Product researchunknown

Gate notes

  • Pay gate unverified: no employer-published annual cash-base lower bound, so the role cannot be ranked under the pay rule.[1]
  • Location passes on employer evidence: Paris, hybrid, three office days per week.[1]
  • AI centrality is mixed: the Incidents team runs “an LLM risk score that rates every new incident and an MCP server that lets AI agents work with GitGuardian”, and one listed mission is “Bring AI to production in our product”. Other listed missions centre on backend performance, Django/Celery delivery and on-call support, and production LLM experience is listed as a plus rather than a requirement.[1]
  • Seniority passes on the title (Senior; 5+ years of web software development). New to this site’s history. Posted October 27, 2026 per the structured data on the employer’s page. The application form rendered on the check date.[1][2]
For particulars: View listing

Research lead — opening a listing is not a recommendation.

Company & role evidence notes

Role/product noteEmployer-stated: GitGuardian sells secrets detection and non-human-identity security. The Incidents team handles prioritisation, routing and remediation after a leaked credential is detected, at millions of incidents per day.[1]

Company researchEmployer-stated on the listing: Series C raised in early 2026; offices in Paris, New York City and Boston. Amount, revenue and headcount were not publicly verified in this run.[1]

Source evidence notes (2)

Evidence notes are recorded research notes and may paraphrase the source; they are not guaranteed to be verbatim quotations.

Remanence

Member of Technical Staff — Environments / Evals

Near-miss

Report date
Evidence checked
Posted
Work location
Hybrid — Official listing: location “Paris; London”, location type “Hybrid”; “A flexible hybrid setup, with a preference for working together in person.” No office-day pattern is stated.[3]
Salary evidence
No published figures
Equity
Yes

Pay noteThe employer listing says only “Competitive compensation and equity”, and the official ATS data carries no compensation. A third-party job site shows €90,000–€130,000, but that figure is not on the employer’s board and was not counted.[3][4]

Recorded gates (as checked on the report date)

  • Listing openpass
  • Locationunknown
  • AI-centralpass
  • Payunknown
  • Product researchunknown

Gate notes

  • Pay gate unverified: no employer-published salary. The €90K–€130K figure seen on a third-party site cannot be matched to the employer’s board.[3][4]
  • Location is not established: Paris is listed and the role is hybrid, but no attendance rule is published (“a preference for working together in person”).[3]
  • AI centrality passes: the role builds task generators, curricula, learned simulators and evaluation harnesses for training AI agents, e.g. “Build reproducible evaluation harnesses and held-out tests that detect reward exploitation, simulator shortcuts, contamination, and failures to generalize.”[3]
  • Seniority is not stated: the title is Member of Technical Staff with no level or years requirement. New to this site’s history; first published September 22, 2026 per the ATS. The application form rendered on the check date.[3][4]
For particulars: View listing

Research lead — opening a listing is not a recommendation.

Company & role evidence notes

Role/product noteEmployer-stated: Remanence turns enterprise workflows into simulated, interactive environments where AI agents are trained and evaluated, aiming at specialised models for long-horizon tasks.[3]

Source evidence notes (2)

Evidence notes are recorded research notes and may paraphrase the source; they are not guaranteed to be verbatim quotations.

n8n

Forward Deployed Engineer - EMEA

Rejected

Report date
Evidence checked
Posted
Work location
Remote — Official location list: “Berlin Office; Albania; Austria; Belgium; Bosnia; Bulgaria; Croatia; Czech Republic; Denmark; Estonia; Finland; Greece; Hungary; Ireland; Latvia; Lithuania; London Office; Montenegro; Netherlands; Norway; Poland; Portugal; Serbia; Slovakia; Slovenia; Spain; United Kingdom”, location type Remote. France is not listed.[5][6]
Salary evidence
No published figures
Equity
Unknown

Pay noteNo salary range is published; the listing says “Competitive compensation 💸 – We offer fair and attractive pay.” The ATS data carries no compensation tier. Pay is unknown.[5][6]

Recorded gates (as checked on the report date)

  • Listing openpass
  • Locationfail
  • AI-centralfail
  • Payunknown
  • Product researchunknown

Gate notes

  • Location gate fails: France is absent from the 27-location list.[5][6]
  • AI-central gate fails: the main duty is enterprise workflow-automation delivery, “embedding on-site, solving real customer problems, and building reusable automation patterns”, including 5-day on-site deployment engagements. Building AI systems is not named as a primary duty.[5]
  • Pay is unpublished. New requisition, published October 30, 2026 per the ATS, with an application deadline of December 8, 2026. The application form rendered on the check date.[5][6]
For particulars: View listing

Research lead — opening a listing is not a recommendation.

Company & role evidence notes

No company research recorded for this entry.

Source evidence notes (2)

Evidence notes are recorded research notes and may paraphrase the source; they are not guaranteed to be verbatim quotations.

Vanta

Staff Software Engineer, AI and Data Risk

Rejected

Report date
Evidence checked
Posted
Work location
Remote — Official listing: location “Remote - Ireland; Dublin, Ireland”; “This role is remote-first. For engineers based in the London area, we ask for 2–3 days per week in the office. For engineers based elsewhere in the UK/Ireland, we expect occasional travel to London”.[7]
Salary evidence
No published figures
Equity
Yes

Pay noteNo range is published; the listing says “Industry-competitive salary and equity”. Pay is unknown.[7]

Recorded gates (as checked on the report date)

  • Listing openpass
  • Locationfail
  • AI-centralunknown
  • Payunknown
  • Product researchunknown

Gate notes

  • Location gate fails: eligibility is described for the UK and Ireland only; France is not mentioned.[7]
  • AI centrality is not established: the role drives “privacy, AI, and risk management features” for a compliance product, built with TypeScript, React and Node.js; building or evaluating AI systems is not stated as the primary duty.[7]
  • Pay is unpublished. The requisition first appeared in this site’s sweep with a September 18 date and was republished October 30, 2026 per the ATS; it was not reported before. The application form rendered on the check date.[7][8]
For particulars: View listing

Research lead — opening a listing is not a recommendation.

Company & role evidence notes

No company research recorded for this entry.

Source evidence notes (2)

Evidence notes are recorded research notes and may paraphrase the source; they are not guaranteed to be verbatim quotations.

  • [7] Official Vanta listing and same-page application (Ashby) checked

    Evidence noteThis role is remote-first. For engineers based in the London area, we ask for 2–3 days per week in the office. For engineers based elsewhere in the UK/Ireland, we expect occasional travel to London (roughly once per quarter, <20% of your time).

  • [8] Official Ashby job data for the Vanta board checked

    Evidence noteMetadata summary: location Remote - Ireland with Dublin secondary; workplace type Remote; published October 30, 2026; no compensation tier.

Mistral AI

AI Scientist - Domain Expert Crashworthiness

Rejected

Report date
Evidence checked
Posted
Work location
Remote — Official listing: location “Paris; Amsterdam; Berlin; Linz; London; Munich”, location type “Remote”.[9]
Salary evidence
No published figures
Equity
Unknown

Pay noteNo salary range or equity term is published on the listing or in the ATS data. Pay is unknown.[9][10]

Recorded gates (as checked on the report date)

  • Listing openpass
  • Locationpass
  • AI-centralfail
  • Payunknown
  • Product researchunknown

Gate notes

  • AI-engineering gate fails: this is a domain-expert role whose core requirement is industrial crash simulation, e.g. “Design and run high-fidelity simulation campaigns using structural mechanics solvers such as Abaqus, LS-DYNA, Ansys Mechanical, Radioss or equivalent tools.” Model training is done “with research teams”.[9]
  • Pay is unpublished.[9][10]
  • New requisition, published October 30, 2026 per the ATS. The application form rendered on the check date.[9][10]
For particulars: View listing

Research lead — opening a listing is not a recommendation.

Company & role evidence notes

No company research recorded for this entry.

Source evidence notes (2)

Evidence notes are recorded research notes and may paraphrase the source; they are not guaranteed to be verbatim quotations.