// writing

One question,
answered properly.

Notes on interviewing engineers in a world where every one of them has an assistant. No predictions, no maturity curves — the arguments we have had in public with hiring managers, written out in full.

  1. Is a take-home coding challenge safe to run? What to check first

    Fake recruiters have hidden malware in coding tests. Five checks before you run a take-home project on your own computer, and what to do if you already did.

  2. What replaces the coding interview? Four options and what each shows

    Many managers dropped the coding interview and have no replacement yet. Four options people try, what each can and cannot show, and three questions to ask.

  3. Should you use an AI interviewer to screen engineers?

    An AI interviewer saves interviewer hours, but many only hear the candidate talk. What it can and cannot see, and five questions to ask before you buy one.

  4. Should you go back to AI-free coding interviews?

    Your AI-allowed round gave scattered results and many candidates pasted the whole task in. That spread is the signal. What to change before you drop it.

  5. How to write an interview rubric for an AI-assisted round

    Write the task and the rubric together, describe each band as something an observer can see, write low first and mid last, then test it on your own team.

  6. AI-enabled coding interview: how to prepare

    What an AI-enabled coding interview looks like, what to ask the recruiter, how to practise in the week before, and what to do in the first ten minutes.

  7. Interview scorecard template for technical interviews

    A free interview scorecard template for engineering roles: five criteria, what high, mid and low look like for each, and where the evidence goes.

  8. Can you detect AI use in a coding interview?

    Not reliably. And a detector that worked perfectly would still answer the wrong question — here is what the false-positive maths does to honest candidates.

  9. When is an AI-free assessment the right call?

    We sell the opposite, and we still think some rounds should exclude AI. The three cases where it works, the one condition it needs, and when it is a trap.

  10. Who checks the evidence behind an AI score?

    A score that cites its evidence beats a feeling. But a citation can be invented, so something has to re-check it — and withdraw the score when it fails.

  11. How do you assess an engineer who uses AI?

    Four things to grade once the finished code stops being the signal, what each one looks like in a real session, and why a score has to point at something.

  12. Should candidates use AI in a technical interview?

    Yes — and the company that builds the model reached the same answer for its own hiring. The argument, and what changes about the interview once you allow it.

// rss