3. Context Engineer
Evidence label: Specialization. Current postings use Context Engineer and adjacent titles, but employers also assign the same work to AI, applied AI, platform, and developer-productivity engineers.
What they do
Context engineers design systems that give models the right information, tools, and constraints at the right time. That scope includes retrieval, memory, tool descriptions, repository instructions, and context-budget management. The discipline is broader than prompt wording, but current evidence does not establish one standard organizational boundary for the title.
See the Context Engineering reference for the full discipline, including the ACE pipeline (Section 6), the L0→L5 maturity model (Section 9), and the operational mechanisms that separate a Level 4 from a Level 5 system: signal taxonomy and causal attribution (Section 10), PR-based loop closure (Section 11), ejection of dormant rules (Section 12), constitutional audits (Section 13), and multi-dev profile reconciliation (Section 14).
"Context Engineering is providing the right information and tools, in the right format, at the right time." (Philipp Schmid, Google)
The article Context engineering became a job title documents early title adoption. Treat it as evidence of emergence, not proof of market volume.
Responsibilities
- Design RAG (Retrieval-Augmented Generation) systems and knowledge bases
- Manage context windows across multi-turn interactions and long-horizon tasks
- Define what agents remember, retrieve, or forget during task execution
- Structure information hierarchies (system prompts, conversation history, retrieved docs, tool definitions, safety constraints)
- Optimize context for accuracy and cost simultaneously
- Measure context quality through systematic evals
Required skills
| Technical | Soft |
|---|---|
| Python (context pipeline automation) | Systems thinking |
| Vector databases (Pinecone, Chroma, Weaviate) | Information architecture instinct |
| SQL and NoSQL (context retrieval) | Cross-functional collaboration |
| Cloud platforms (AWS/Azure/GCP) | Curiosity and continuous learning |
| RAG architectures, embedding models | Precision in documentation |
Relationship to other roles
Context engineers work upstream of AI engineers (they define what context is available) and downstream of domain experts (they encode domain knowledge into retrievable structures). Closely related to platform engineers in large organizations.
Entry paths
Data engineer, backend engineer, ML engineer, information architect.