See how much of this job your resume covers, and what’s missing.
Want a recruiter to go through it line by line?
Get professional reviewQuestions interviewers often ask for this role, with sample answers.
Upload your resume and we draft a letter for this exact role, tailored to what it asks for.
The role involves authoring repository-level context for AI coding agents, including instruction files, skills, and prompt libraries. You will also be responsible for automated documentation and code-comprehension generation across legacy codebases.
Authoring repository-level context for AI coding agents: instruction files, skills, prompt libraries, and the conventions that make them consistent across many repositories.
• Reading and reasoning about unfamiliar production code in at least two languages well enough to describe what it does and why.
• Automated documentation and code-comprehension generation across legacy codebases.
• Context and retrieval design: what to include, what to exclude, chunking and indexing, grounding agent output in real repository facts.
• Strong technical writing for a developer audience, and the discipline to templatize rather than hand-craft each product.
• Evidence of measurably improving agent output quality by improving context, not by changing the model.
Nice To Have
Exposure to legacy stacks — COBOL in particular — where added application and domain context is what makes agentic work viable.
• AST, code-graph or static-analysis tooling used to generate context automatically.
• Information architecture or taxonomy background.
Authoring repository-level context for AI coding agents: instruction files, skills, prompt libraries, and the conventions that make them consistent across many repositories.
• Reading and reasoning about unfamiliar production code in at least two languages well enough to describe what it does and why.
• Automated documentation and code-comprehension generation across legacy codebases.
• Context and retrieval design: what to include, what to exclude, chunking and indexing, grounding agent output in real repository facts.
• Strong technical writing for a developer audience, and the discipline to templatize rather than hand-craft each product.
• Evidence of measurably improving agent output quality by improving context, not by changing the model.
Nice To Have
Exposure to legacy stacks — COBOL in particular — where added application and domain context is what makes agentic work viable.
• AST, code-graph or static-analysis tooling used to generate context automatically.
• Information architecture or taxonomy background.
Stop the endless job search. Our AI finds and applies to the best jobs for you.
Featuring 219,422+ Jobs in AI Engineer
Answer easy questions
219,422+ jobs across 15+ categories
Get your best job matches
Only hand-screened, legit jobs
Find a remote job faster
No ads, scams, or junk
“I was the first applicant for a remote marketing position that got listed on the company website the same day I applied. Had an interview within 48 hours!”