CriticCode Blog
Writing on interviewing
in the age of AI.
-
· 5 min read
The interview invitation email is doing more work than you think
When you invite a candidate for an interview, the email is the first real read they get on your team. Most invitation emails handle logistics and stop there. Here's what a good one does instead.
hiring candidate-experience interviewing -
· 5 min read
The questions a candidate asks you are a signal too
The last ten minutes of an interview are usually the most rushed. They're also where candidates reveal more about themselves than in the first fifty. Here's how to read them.
interviewing hiring candidate-experience -
· 5 min read
When the AI transcript looks suspiciously clean
A perfectly polished AI conversation looks great in the submission. It's also one of the clearer signs that the candidate wasn't really thinking. Here's what to watch for.
ai interviewing candidate-experience -
· 5 min read
What a realistic job interview actually feels like
'Realistic' is the most overused word in interview design. Most 'real-world' exercises don't feel like real work to the person doing them. Here's what the shape of a realistic job interview actually looks like.
interviewing hiring candidate-experience -
· 4 min read
Interview calibration is mostly a vocabulary problem
If two interviewers in your interview process mean different things by 'strong hire', they haven't calibrated. A rubric won't fix that. A shared vocabulary might.
engineering-management hiring interviewing -
· 5 min read
The interview transcript is a better artefact than your notes
Most teams leave a technical interview with a page of notes and call it a record. A transcript catches the things notes can't: pacing, framing, what was actually asked.
interviewing hiring engineering-management -
· 5 min read
The follow-up interview is where the take-home earns its keep
A take-home is an artefact. The follow-up conversation is where it turns into signal. Most teams leave that conversation entirely unstructured. Here's a shape that works.
interviewing take-home hiring -
· 5 min read
What a GitHub profile actually tells you about a candidate
Scanning a candidate's GitHub feels like getting a private peek. It's mostly not. Here's what you can actually learn from it and what you can't.
hiring interviewing candidate-experience -
· 4 min read
Your interview process needs a position on AI, not a policy
Most teams haven't really decided what to do about AI in interviews. Candidates can tell. The muddle costs you more signal than either extreme would. Pick a side.
ai interviewing hiring -
· 5 min read
Your first technical screen is probably doing three jobs at once
The first technical round after the recruiter call tries to filter for technical fit, team fit, and interest at once. It's not great at any of them.
interviewing hiring engineering-management -
· 4 min read
What a coding test for an interview actually measures
Coding tests were built to prove a candidate could write code. The format still looks the same; the signal doesn't. Here's what interview coding challenges actually measure in 2026, and what's worth measuring instead.
interviewing hiring engineering-management -
· 4 min read
The debrief is where most interview processes quietly break
Five interviewers can run five good sessions and still produce a bad hire if the debrief meeting is run like a popularity contest. Here's a different way to run it.
engineering-management hiring interviewing -
· 4 min read
Live coding rewards composure, not engineering
Live-coding interviews test whether a candidate can stay calm under surveillance while regurgitating a pattern they happened to remember. That's not a signal about engineering. Here's what we think is.
interviewing hiring engineering-management -
· 4 min read
How to ask a question a candidate can't rehearse
Every question in your interview process sits on a spectrum between 'the candidate has answered this thirty times' and 'the candidate has never thought about this before'. The second end is where the signal lives.
interviewing hiring engineering-management -
· 5 min read
What a good challenge statement looks like
The challenge statement is the hardest part of CriticCode to get right. Here's the shape of one that works, with worked examples for three common roles.
hiring interviewing challenge-design -
· 4 min read
How to read a candidate's AI transcript
The final written answer is the tidied version of the thinking. The AI chat transcript is where the actual thinking shows up. Here's how to scan one in under ten minutes.
ai interviewing hiring -
· 4 min read
Take-home interviews that respect everyone's time
If your take-home is longer than two hours of real work, you're filtering for candidates with free weekends, not candidates with judgement. Here's what a good one looks like.
take-home hiring interviewing -
· 4 min read
The paste event isn't cheating
Every time a candidate pastes a chunk of text into a take-home, some hiring manager reads it as a confession. It isn't. Here's how to read a paste event like a grown-up.
hiring ai interviewing -
· 4 min read
Candidates already use AI. Most interviews haven't caught up.
The 'no AI' clause on a take-home started as a quality filter. In 2026, it mostly ends up measuring whether the candidate is willing to pretend. Here's what we think it's worth measuring instead.
hiring ai interviewing