Ask HN: What do coding interviews look like in the age of AI?
I'm a senior Rails/React dev with 13+ years of experience. Recent AI-driven layoffs have me (soon) looking for work again. But I've barely hand-written a line of code in the past year. All that has been necessary is good prompt writing and tedious, patient code review with tweaks for style / formatting and obviously re-prompting for bad architectural decisions.
Should I go back and hit the books / write a bunch of components by hand to get the muscle memory back? Or have programming interviews changed to catch up with the technology and do things now look broader and more architectural?
7 comments
[ 2.1 ms ] story [ 8.0 ms ] threadBefore: you invert the tree during the interview but not at work.
Now: you use AI at work but not during the interview.
I sometimes consider applying even when I am not looking for a job, just to get to technical interviews where I don't care about passing and start questioning the interviewer. Like "So it's been 30min of leetcoding and the interview is 1h. Now it's your turn, I give you a leetcoding exercise that I prepared and you have 30min to solve it. If you don't convince me I don't go to the next interview".