A new job title showed up in my feed last week. Context engineer. I clicked. Twice. Three articles, all definitional. None of them showed code. Every definition was a paraphrase of "name things well." Then I opened my own repo and grepped for utils.py . Eleven hits. Six folders deep, in a project I have shipped to production. The same project where I had spent two hours that morning fighting an agent that kept loading the wrong helper file. The fix took thirty seconds. I renamed the file. The pitch checks out The current pitch goes like this. LLMs perform better with the right context. So we need a new role to design that context. Curate the files, structure the prompts, build the retrieval system, manage the embeddings. Each claim is accurate. None of them describes a new problem. You have been doing this since you wrote your first config file. Every time you renamed helpers.js to payment-validation.js , you were context engineering.…