OpenAI Codex on Your Resume: How to List It in 2026
How to put OpenAI Codex on your resume in 2026: CLI, IDE extension and cloud tasks, where to list it, bullet examples by level, AGENTS.md, and what interviewers ask.
Updated November 15, 20267 min readWritten by the MatchResume.ai team
Try MatchResume FreeQuick answer
How to put OpenAI Codex on your resume in 2026: CLI, IDE extension and cloud tasks, where to list it, bullet examples by level, AGENTS.md, and what interviewers ask.
- Yes, list OpenAI Codex if you use it on real work: in an AI Dev Tools line and in one bullet with a result.
- Say which part you used. Delegating tasks to Codex in the cloud and reviewing its pull requests is a different skill from using it in the terminal or the editor.
- Write 'OpenAI Codex', not just 'Codex', so recruiters and ATS keyword matching know which tool you mean.
Should You Put OpenAI Codex on Your Resume?
Yes, if you use it on real work. OpenAI Codex is a coding agent: you give it a task, it writes and runs code, and you review the result. Hiring managers who list AI coding tools in a job ad want to see that you can delegate to an agent and still own the code. A bullet with a result and a review step shows exactly that.
Which Part of Codex Did You Use?
Codex runs in several places under one ChatGPT account. Name the one you used; each tells a reviewer something different.
| Where you used it | What it signals |
|---|---|
| Codex CLI in the terminal | You work with an agent inside your local repo and toolchain |
| IDE extension | You pair with an agent while you write and refactor code |
| Cloud tasks that open pull requests | You delegate whole tasks in parallel and review them like a teammate's PRs |
| Code review on GitHub | You use an agent as an extra quality gate on pull requests |
Where to Put It: Skills Line and One Bullet
- Skills section: 'AI Dev Tools: OpenAI Codex, ...' so ATS keyword matching finds it
- Experience bullet: the task you delegated, how you checked it, and the result
- Projects: link the repo, ideally with the AGENTS.md you wrote
Skills section
Before
Tools: Codex, Git, Docker
After
AI Dev Tools: OpenAI Codex, Claude Code, Cursor Languages: Python, TypeScript, Go
Showing AGENTS.md and Delegation Skills
The skill employers look for is not typing prompts. It is setting an agent up to succeed and catching its mistakes. Two kinds of bullet show it well.
Agent setup
Before
Set up Codex for the repo
After
Wrote an AGENTS.md for our Python services (test commands, lint rules, migration conventions); agent-made pull requests passed CI on the first run 80% of the time, up from about half
Delegation and review
Before
Used Codex to do tasks
After
Delegated dependency upgrades and flaky-test fixes to Codex cloud tasks; reviewed and merged 45 agent pull requests in a quarter, freeing about a day a week for feature work
Bullet Examples by Experience Level
Swap in your own numbers and keep only what you did.
Junior or student
Before
Made an app with Codex
After
Built a budget-tracking CLI in Python with the Codex CLI; designed the data model myself, added 40 pytest tests and published it on PyPI
Mid-level engineer
Before
Used OpenAI Codex at work
After
Used OpenAI Codex to add type hints and tests to a 20,000-line legacy Django app; reviewed every change, raised coverage from 38% to 71% in six weeks
Senior engineer or tech lead
Before
Brought AI agents to the team
After
Introduced Codex code review and cloud tasks for a team of 9 with a written review policy; escaped defects stayed flat while merged PRs per engineer rose 30%
What Interviewers Ask When They See Codex
- 'Which tasks do you give the agent, and which do you keep?' — shows judgement
- 'How do you review an agent's pull request?' — your chance to talk about tests and diffs
- 'Tell me about a time the agent was confidently wrong.' — shows ownership
- 'What did you put in AGENTS.md and why?' — shows you can set up a team
Red Flags: When Listing Codex Hurts
- ✓'Codex' alone, so a reader can't tell which tool you mean
- ✓No result, review step or repo next to the claim
- ✓Merging agent work you cannot explain line by line
- ✓AI tools listed above your core languages and frameworks
FAQ
Should I put OpenAI Codex on my resume?
Yes, if you use it on real projects and can explain how you review its work. List it with your other AI coding tools and back it with one bullet that shows the outcome.
Is this the same Codex that powered early GitHub Copilot?
No. The original Codex model from 2021 was retired. Today OpenAI Codex is a coding agent you use from the terminal, your editor, the cloud or GitHub. On a resume it means the agent.
Codex, Claude Code or Cursor: which should I list?
Every tool you can speak to in an interview, on one AI Dev Tools line. If you used one much more than the others, make that one the subject of your bullet.
What is AGENTS.md and should I mention it?
AGENTS.md is a file in a repository with instructions for coding agents, such as how to run tests and which conventions to follow. Codex reads it. If you wrote one for a team, it is a strong, concrete bullet.
Related articles
How to List Claude Code on Your Resume
How to list Claude Code experience on your resume — what to write, how to show real output, and how to make agentic coding experience readable to recruiters.
Cursor on Your Resume: How to List It in 2026
How to put Cursor on your resume in 2026: where it goes, how to write the bullet, how to show agent, Cursor rules and MCP experience, and what interviewers ask about it.
GitHub Copilot on Your Resume: How to List It in 2026
How to add GitHub Copilot to your resume in 2026 — where it belongs, how to write the bullet, and what to say in an interview when they ask about your AI coding workflow.
AI Skills to Put on Your Resume in 2026
Which AI skills belong on your resume in 2026 — prompting, Copilot, Claude Code, AI-assisted coding, and more. With formatting tips and real before/after examples.