I interviewed for an “AI software architect” job this week with a well-known multi-national, and they did not want to hear about how I’m using Claude Code to be 5x more productive than before, or about how I would approach their AI software strategy, or hear about what I’ve created in the past 12 months, but they did want me to solve live LeetCode problems during the interview. The twist was that they wouldn’t tell me the actual problems; they expected me to have memorized the problems by name along with the solutions. The larger question is how software job interviewing will change in light of the significant workflow changes over the past 12 months. I can imagine being given a software problem that can be solved using agentic coding in about 30 minutes, but only if approached systematically. By that I mean, something so complicated that “build me X” is not going to cut it. In my 15 years as a software engineering manager, I hired too many people who could solve any software program I gave them, but couldn’t actually be productive in real life. The point of hiring people is for THEM to solve problems that I can’t. Giving people a bunch of tricks to memorize just tells you if they can learn solutions and regurgitate them in a highly stressful environment; it tells you nothing about how they would approach real-life complicated problems that require thought, planning, and experience. I have had to fire people who could solve any trick programming in the book, but couldn’t handle “research this problem and give me a solution” when they couldn’t look it up on the internet. Given that everyone is busy and companies will naturally do whatever is easiest, someone will recreate online programming tests for the agentic programming era. submitted by /u/czei
Originally posted by u/czei on r/ClaudeCode
You must log in or # to comment.