Research Engineer, Codex
This is an analysis of the public job description. It is not a confirmed description of this company's interview process, and no company has reviewed or endorsed it.
What the posting clearly emphasises
- Agentic coding models, tool use and the surrounding evaluation work.
- Training infrastructure and running training jobs.
- Ambiguity spanning research, engineering, data and product.
What that likely means for preparation
- Expect strong hands-on coding, not a conventional puzzle round: reading unfamiliar code and changing behaviour under test is the closer analogue.
- Prepare how you measure a coding agent: task sets, pass criteria, flaky graders, and why unit-test pass rate alone misleads.
- Have an infrastructure story: a training or evaluation run you made faster, cheaper or reproducible.
What stays unknown about the loop
- How much of the loop is research discussion versus production engineering, and whether a take-home is used.
- The round order, count and length. Postings describe the job, not the loop.
- Whether AI assistants are allowed, required or banned in any coding exercise.
The company and role link are carried over. Paste the full job description on the next page for the highest-fidelity map — we save the link but do not read it for you.
Build my map for this role