Ask HN: How are you interviewing engineers in this agentic era?
Curious to know how are you interviewing engineers?
Do you have a no-LLM policy? Are take-home tests worth it? How do you make sure engineer is a "good" engineer?
Do you have a no-LLM policy? Are take-home tests worth it? How do you make sure engineer is a "good" engineer?
stuff like the pros and cons of JWT, when orchestration is necessary, APIs vs message queues, their opinion on statically vs dynamically typed languages, etc
these questions don't tell you directly how efficient they will be on a project or language stack, but they DO tell you whether or not the person actually understands programming at a deeper and wider level, and not just experts at regurgitating generic PRs for your average 10LOC ticket
Those seem practical to me.