Labs prefer 'Context Engineers'
Top AI labs have moved away from traditional 'prompt engineer' roles and are hiring 'Context Engineers' — jobs advertised with salaries above $220K as teams focus on deeper system integration rather than surface prompting (x.com).
Andrej Karpathy and other high-profile practitioners popularized "context engineering" as a discipline distinct from ad‑hoc prompting, calling it the systematic work of filling a model's context window with the right information for each step. (ludaxis.io) Philipp (Phil) Schmid at Google DeepMind has publicly framed context engineering as an operational discipline — organizing instructions, retrieval, tools, and memory into a production-ready context pipeline. (contentstack.com) Anthropic’s current hiring listings explicitly recruit "prompt and context engineers" and list responsibilities that span evaluations, prompt frameworks, and product integration rather than one-off prompt crafting. (job-boards.greenhouse.io) OpenAI’s public roles emphasize system-level work such as AI deployment and research translation — job pages describe collaborating to translate research into scalable systems and list deployment/engineering responsibilities alongside research scientist openings. (builtin.com) Market evidence shows advertised compensation for context/prompt-adjacent roles and research positions frequently exceeds $220K: Anthropic job boards show a "Prompt Engineer and Librarian" listing at $175K–$335K, a Teal posting lists a "Technical Documentation & Content Engineer, Model Context Protocol" at $280K–$405K, and OpenAI research scientist listings report ranges around $250K–$445K. (jobdai.com) Hiring criteria diverge by track: Anthropic prompt/context roles require 5+ years of software engineering experience with Python and practical LLM work, DeepMind research listings repeatedly ask for a PhD or equivalent, strong publication records and JAX familiarity, and OpenAI research positions list PhD-level research experience and a record of top-tier publications as common expectations. (job-boards.greenhouse.io) Company practices imply two clear entry routes: the shortest path to a research‑scientist role at labs like DeepMind or OpenAI remains a PhD-level research record with publications in NeurIPS/ICML/ICLR, whereas production‑focused "context engineer" and deployment roles favor seasoned ML software engineers with systems, evaluation, and productization experience. (job-boards.greenhouse.io)
