Prompt engineering did not disappear when models got better, it changed shape. Here is what the skill actually looks like in 2026, why a resume line or a quiz cannot measure it, and the tasks and rubric that do.
Engineering managers should not take coding tests, and most EM loops overcorrect into pure behavioural questions that everyone has rehearsed. Here is a middle path that tests the judgment calls the job actually consists of.
A live system design interview lives or dies on structure, not on which question you pick. Here is a minute-by-minute run sheet for keeping it a conversation, plus when a take-home design doc is actually the better call.
When the candidate pairs with an AI instead of with you, the assessment moves from writing code to judging it. Here is what to watch, how to design a task the model cannot finish alone, and what a strong session actually looks like.
Hiring managers are now expected to judge how well candidates work with AI, mostly without having done it themselves on real work. Here is the minimum literacy you need to run that round honestly, and the four questions that expose whether you have it.
Time to hire is mostly waiting, not interviewing. Here is where the days actually go, which ones you can remove without lowering the bar, and the two changes that cut the most.
For a recruitment agency, submission-to-interview ratio is the whole business model. Here is why CV screening cannot move it, what a technical assessment platform has to do differently for agency work, and how to introduce one without adding a step candidates walk away from.
Most technical interview feedback is either legally sanitised nothing or a list of everything the candidate did wrong. Here is what to send instead, what your lawyer actually objects to, and how a real-environment interview makes the useful version cheap to write.
Teams assess whether engineers can use AI well and never assess what they feed it. Here is what AI security literacy actually covers, why a code review will not catch a leak, and four interview exercises that surface it before it becomes an incident.
How to conduct a system design interview as the interviewer: questions grouped by what they test, a weak-versus-strong answer transcript, and a rubric that scores the conversation instead of the final diagram.