Ask HN: What do your job interviews look like? (August 2026)
For those who have recently (Summer 2026) gone through software engineering job interviews, have you noticed any changes in the interview process?
Is it still the usual Leetcode, system design, behavioral and leadership questions, and maybe technology specific questions (e.g., Spring for Java devs, borrow checker details for Rust devs, etc.)?
Or have you noticed something completely different because of the AI agentic era, with companies taking a fundamentally different approach to interviewing engineers? If so, could you share some of the more unique or unusual things you've seen?
17 comments
[ 0.24 ms ] story [ 12.1 ms ] threadThinking about which profession to choose next, cause I'm not passing so many gates so far.
But one thing is very common. It's that the cultural fit interviews are longer and carry more value than ever (possibly more than technical interview). Out of 5 stages, 2 or 3 are meeting non tech people, coming to the office, having an informal chat, etc. Companies really want to know you as a person and are very careful who they pick. It's the same for remote, hybrid or office based work.
Technical gaps will always be there, and people will have to work with those and learn.
Maybe I am just talking from the perspective of a SWE that is not exceptional, but this is my feeling.
The only difference is that in the Live coding session they now allow AI to be used. I didn’t use it and went old way (because I had already rehearsed it the old way, and found no feedback on the internet about how the company assess AI usage, so I didn’t want to be the Guinea pig)
Interview took place this summer. Major tech company in EU (not faang tho). Also Live coding is not leetcode.
So this company wanted to replace MuleSoft with a home grown solution using TypeScript and Node.js. The primary reasons were the high costs of MuleSoft and the inability to pivot from MuleSofts most basic approach to REST. A home grown solution would quickly pay for itself in operating costs and could be relicensed as a future product that solves problems MuleSoft can’t. This new initiative has 0 lines written and the position called for a Node.js expert to start this off.
There were three rounds of interviews each for 30 minutes with different leaders. One of these interviewers was aware of TypeScript and how Node works but none knew what to ask from a technical perspective.
The final interview was with the person assigned as the architect of this effort who was greatly opposed to training people and opposed this initiative generally.
After leaving the interview it was clear that the person hired would be on their own and scapegoated by insecure personalities with conflicting agendas not related to product or the underlying financial motive.
In a way this experience felt like a game of a pending marriage divorce with ambitious personalities versus highly neurotic people focused on their own things. The more I thought on it the more it reminded me so much of several past employment experiences.
I didn't find a place which I liked an stopped the process most of the times after the initial interview.
A waste of time in other words..