4 ms·
Interviewing Engineers in the AI Era: Lessons from a Year of Rebuilding
- WorkflowResearc 4mo ago[dead]
- shdh 3mo agoWe gave away the most fun part of being a SWE to the clankers
- SadErn 3mo ago[dead]
- Muromec 3mo agoThe most fun part being seeping through stderr of tsc and restarting the unit test runner after realigning some assumptions.
- dan_q 3mo agoIf you want it back, ruthlessly mock the low-performing "engineers" who are addicted to LLMs. In every company, we need to make these weaklings our scapegoats.
- keybored 3mo agoWriting for investors in the AI Era - We have embraced everything about the AI Era at our company - Arbitrary topic about how that changes something
- mchinen 3mo agoI've been considering different ways to measure code understanding and fluency. I'm still using traditional 'easy' problems on a coding pad to probe this, but I'm finding a new generation candidates that don't prepare for this, and may be able to have a full career with just a higher level of code understanding. But they might not ever develop the ride-a-bike with one hand level of fluency unless they grind pointless leetcodes. So I'm increasingly uncertain about what and how to test. My default for now is still to rely on ability to write basic code fluently, but I'm open to changing this perspective. I really want to know how this existing repo AI-assisted live coding test works, with example problems. It seems the standard data structure puzzle type thing won't be feasible if you are using an LLM. Also the latency for these agentic coding/prompts seems like it would make the interview a bit awkward. Anyone been conducting or taking interviews with this kind of thing with thoughts to share?
- mbil 3mo agoI’ve been conducting AI Coding interviews at my job. Candidate will screen share and use AI-assisted coding environment and tools of their choice. I ask them to implement xyz thing. What I’m looking for is how they interact with the AI agent. Do they ask the agent to plan first? Do they review the plan? Etc. It’s pretty typical stuff that you might expect an experienced engineer to do if they effectively use such tools daily. There are a series of follow-up questions about how to productionize the toy system, which gives some additional signal about how well they understand what they’re making. I sprinkle these in when there’s dead air waiting for the bot to think. I think we’ll need to evolve and refine this problem and process as the models continue to improve.
- Muromec 3mo ago>It’s pretty typical stuff that you might expect an experienced engineer to do if they effectively use such tools daily. It's also the kind of stuff that somebody can learn in a week, so not hiring the right person who just didn't spend this week of time yet for whatever reason is a loss.
- pmg101 3mo agoYeah it tells you nothing of value. It's the Recency Bias taken to its ultimate conclusion isn't it. Anything I learned about AI I learned in the last few months but somehow that's as important as all the experience of my decades long software career? Come on.
- Muromec 3mo agoIt signals you don't have enough time or will to chase the latest stuff, otherwise you would have learned it with other cool kids half a year earlier. It carries some signal, but I would not choose based on this alone. I would even consider selecting against this to a certain point, but I also work in a place that COBOL on a mainframe. YMMV.
- 3mo ago
- dgellow 3mo agoSomething I appreciated when going through Anthropic interview process was that I only dealt with humans. They could have been showcasing how even their interviews are done with Claude or something, but no, the whole loop was interacting with real humans, and nothing was on the topic “how do you work with LLMs”. It was about how me, the human, think and approach situations, and how I handle working with others (humans), etc. Which made a lot of sense to me, and I overall appreciated their process (other than it’s very time consuming, requires lots of prep). But it’s interesting to see that AI labs customers feel the need to showcase how much of their processes are now around agentic stuff
- bravetraveler 3mo agoFourth crack commandment: never get high on your own supply
- dan_q 3mo ago[flagged]
- deleted 3mo ago[deleted]
- bonoboTP 3mo agoThey extensively use Claude to develop Claude. It's absurd to suggest they don't use what they push on their users. It's one of the most common criticisms of Claude Code that it's too vibe coded and buggy due to that.
- normie3000 3mo agoIt's why you never meet a dog that works in a dogfood factory.
- lukewarm707 3mo agothey will use their own product. but they will rule like the plutocracy that they are. they will tell me that they are not privileged to have my custom, rather, i am privileged to be their customer. we will tell ourselves that we should wait eagerly to see if we will be graced by "tibo's" largesse, like peasants clamouring to see a royal throwing bread among the masses. or that it is right and good that claude should refuse to answer on account of safety, but hack other companies on behalf of anthropic. surely we are too simple, and sometimes naive, truly we know not what is best for ourselves. no more. Vive la révolution!!
- o0ower0o 3mo agoI am really looking forward to the day where AI is normalized during interviews. Right now the duality of interviews is basically: - You get a leetcode question and if you're lucky is an easy medium that you can solve, if you're really lucky you already solved it and can pretend you are approaching the problem the first time. Good luck if you get a hard question and you never saw it before. - You get a home assignment, in a framework you might not know but you're expected to be fluent with it, then waste 1 hour setting up the project structure, and one more hour to find out how the framework expects you to define the CORS allow list. You are expected to deliver the project in 3 hours. The good I see in AI is that it completely removes the need to study just for interviews, and you can also delegate all the project setup to the AI. Then you can focus on what you would test (e2e? integration? what are the boundaries? what do we mock?), how to keep the documentation, how to structure your code. You have an expensive endpoint, do I make it sync or add an async jobs framework? Imagine you're an expert in C++ interviewing for a Django position and the interview consists of fixing a big in a repo. The bug is that a function without type hinting is modifying what is expected to be a list, but the caller is passing a tuple. Trivial after a week you work in python and you have your environment set up for type warnings, also trivial with AI and definitely not an interesting problem that shows expertise with software engineering in general. We also did this in our last interview at work, and it was a really good indicator to see if someone just copy pasted code, or understood it after it was generated. Some candidates had a unit test fail and couldn't debug it for his life, even if he "wrote" all the code himself. Others simply did not understand the architecture they wrote, and assumed that a function defined with "async" and awaited would run in parallel from the code that called it (as if you spawned a thread)
- Muromec 3mo agoI was on the interviewer side last month. We stopped giving take-home assignments because they don't produce a signal anymore. We explicitly said -- feel free to use whatever framework and AI assistant, just show us how you do it. The practical part had no leetcode too. Just build something really basic, then explain a snippet of code (3 lines) and generalize it. A trick question (with a disclosure it's a trick question) if the candidate did it fast enough that we didn't have to go into the overtime. A bit of theory about protocols, all in all an hour and we leave another 30 minutes on top to answer questions. At the end of the day we just filter out with confidently bad takes, people who can't do 2+2 and ones that can't understand the question without rephrasing it three times. The most bizzarre candidate didn't know anything at all, but was so relaxed and confident, that he spent all of the 30 minutes asking about the company and how his day would like and all that, while he clearly bombed it. The difficult part is how to not filter out a competent person who doesn't necessarily agree with all of your takes, uses all the same tools and had all of the same experiences as both of the interviewers.
- rvz 3mo agoI would do the opposite and would likely use the same framework that some AI companies are doing to evaluate candidates. By either not allowing them to use AI assistants in any part of the interview process (Anthropic and OpenAI does this.) or give candidates a strict token limit (100k tokens) until the candidate runs out of tokens. They have to earn it, as the tokens are not free. Given that deskilling and over-reliance in AI assistance will continue to happen, putting a hard token limit <100k tokens in the interview process serves as a great filter to prevent the vibe-coders and "tokenmaxxers" out and forces a higher bar for quality, with clean code and reasoning across well maintained software with less tokens rather than increasing the slop. Do you want a candidate that knows when to use AI and carefully uses tokens with in their limits, or do you want a candidate generating incomprehensible AI slop to be tokenmaxxing out your company limits and then draining your company bank account?
- dan_q 3mo agoI would start looking for a new job if I heard that my company hired someone who wasn't able to prove that they could write code without LLM assistance. A lot of people like that are legitimately illiterate.
- hansmayer 3mo ago[dead]
- sarmadgulzar 3mo agoThis all sounds good on paper but I have an honest question: How do you develop judgement as a junior or mid level engineer to critique AI if you yourself never learned that skill by making mistakes in the first place? I’m not saying that all code should be typed by hand in 2026 but there are certain subtle things you learn only when you get into nitty gritty details especially related to security. Also today’s AI is notoriously bad at ownership. When you ask it to give you a concrete answer, it will still give you options with pros & cons of each so that ultimately you own the decision and not it. So how do you decide between the two (or more) when you never learned to do it yourself?
- throwatdem12311 3mo agoYou hire juniors but don’t let them use AI tools for a year :)
- sarmadgulzar 3mo agoStakeholders are not technical enough to understand that so CEOs won’t do it. We are already seeing it play out. Entry-level hiring has been consistently down ever since AI got mainstream.
- throwatdem12311 3mo agoThe competence crisis in a few years is going to be apocalyptic.
- xmcqdpt2 3mo agoI wish but at $work the push has been the opposite. I'm still allowed to write code, but interns and juniors are being told that they need to prompt all the time. I think upper management are hoping they can replace a possibly reticent or AI skeptical "old guard" with AI native Gen Zs. In practice, the young out of school kids are much less excited about AI than the 50 year olds, so I don't know how well it will work.
- 3mo ago
- jacamera 3mo agoI'm very skeptical of that graph. What does it mean for code to be AI-generated vs human-generated? If I merge a PR that was opened by Claude do all the changes in it automatically count as AI-generated? How about the individual commits? If I'm reviewing locally and make manual changes but then have Claude create the commit it appears to be AI-generated but might not have been. The point is that these metrics are easy to game and I've definitely wasted time and tokens refining code with Claude that would have been easier to just edit by hand. It can be kind of fun and when the goal is just "use AI" I don't find it surprising that graphs showing 100% switch to AI-generated code could be defensibly generated without really saying anything about how much manual intervention is happening or how efficient the process is.
- xmcqdpt2 3mo agoOne of my least favourite feature of our AI era is that I can't even trust people to do basic math anymore. It used to be that a graph like that would mean someone had a (probably broken) metric that they put in an excel sheet and got a lineplot out of it. The metric might be broken but at least additions and subtractions etc were correct. Now I don't even know! Colleagues send me graphs they made with Copilot and then we discover that the LLM did mental arithmetic or whatever to produce the results and they are wrong. Computers used to be able to do math !
- pards 3mo ago> When the cost of building goes to zero Where are they getting all those free tokens from?!? I don't like this rhetoric. It still costs money to write code, only now that wealth gets transferred to Anthropic instead of to individual contributors.
- serial_dev 3mo agoAnd even ignoring the token costs, that is just not true. Sure, for some cases, the cost is going down. I and others on my team "one-shotted" impressive features in an hour of agent work that would have taken humans probably a month if done completely manually. I've also seen agents going in circles for an hour on a fix that would have taken even a junior 3 minutes to get right (after it was struggling for 10 minutes, I wanted to see if it can ever get it right as an experiment). And when taking a look at the whole organization, orgs still just aren't really shipping that much more quality features to their users as the impressive one-shot demos would make you think.
- pards 3mo ago> orgs still just aren't really shipping that much more quality features Writing code was never the bottleneck at large enterprises.
- bonoboTP 3mo agoNor was product quality the goal. Principal agent problems abound. The large org's behavior follows the thousandfold incentive gradients of the individual employees in their own career, CV building, promotion paths, budget allocation, etc.
- wiksorr 3mo ago[dead]
- zitterbewegung 3mo agoI'm not sure if it is a good idea when you are referencing your "rebuilding" after you reduce headcount by 14% . If this isn't some kind of entendre then it's actually extremely effective. https://xcancel.com/brian_armstrong/status/2051616759145185723 https://xcancel.com/brian_armstrong/status/20516167591451857...
- cheeaun 3mo agoCurious to know: - does the company provide the harness and specific model for this? Or the interviewee use whatever they have access to? If they don't do a good job, is it the fault of the harness or the model or the interviewee not knowing how to fully utilise the harness and model or alternative harnesses and models? - if every interviewee uses different harnesses and models, how does the company ensure that it's a fair comparison between interviewees for the same role? - will the interviewer go through all lines in the code generated or let AI do it?
- Ac1285asFa 3mo agoRegulatory compliance as attempted by Coinbase does not pay, and of course they had many fines for non-compliance already. The whole point of Bitcoin is sanctions evasion. Tether moved from Deltec Bank (CIA) in the Caribbean to Lutnick's Cantor & Fitzgerald and El Salvador. That is where the action is. So promoting the AI bullshit is for investors because that is what they want to hear. They are not going to vibe code financial transactions and get another $500M EU fine. As an aside, it is interesting that the new "taste" talking point was already on Coinbase in mid-July.
- nitwit005 3mo agoMy company has tried to produce an AI oriented process, and I just don't see it making sense. The basic problem is, no one on our side has actually doubted the ability of candidates to us the AI tools in conventional ways. Consider the design section here. I think we are all confident the candidates can query some AI tool for a design. It's basically copy-pasting the description in. The real goal is to have a discussion, to see if they understand the relevant issues. But then, we could just hand them a design. It just seems like you waste time having them fiddle with prompts and everyone trying to read the output. Just skip to the discussion.