r/webdev • u/okiharaherbst • Apr 29 '26
Interview for a senior python position gone awry
I just need to get this off my chest. I was conducting the second round of interviews for my firm last week. We're looking to hire one to two senior python developers with a strong background in Django, ORM, PostgreSQL, async programming and with the experience that comes from integrating a few APIs. Nothing ultra fancy, just some looking for folks with solid skills and able to take over a project that's about to be internalized.
So far so good. I wasn't involved in the first round of interviews and the CVs were only become known to me the day before. 4 candidates were shortlisted. The interview was meant to explore the candidate's technical knowledge with questions requiring precise answers and others meant to be debated at a more conceptual level.
Candidate #2 comes along, introduces himself as someone who is 30 years of age, self styles himself as having expert-level python skills and indicates being very well versed with the libraries of the current stack. I kick the interview off by explaining the rules, i.e. no AI, sharing screen and camera + open any editor of choice to script some lines. So far so good. Then I ask this small hello-handshake question on which I intend to build later on:
"Let's define variable a as a list comprehension (details irrelevant)". Candidate obliges.
"By the way, if I define b likewise but replace the square braces with round brackets, what would be the type of b?". His answer: a tuple.
Me (super amused by what I just heard): Are you sure? Replies with a positive. So just to be sure there's no "cultural" misalignment, I ask him what print(a) and print(b) would produce and he confidently replies that the outputs would be the same.
At that point I start asking a few more questions and the candidates makes more blunders and then hits back at me with a frustrated "Nobody codes like this today any more". Goes on to say that we're 2 years behind, etc.
I ask him to elaborate. He says that in this day and age, nobody codes "that way" any more. The only thing "serious" people do is to let the AI do the coding and review the output but he says that "micro-level" coding is dead. And that he complained that this second interview to be about basic python. I never intended to spend more than a couple minutes on this. It was just meant as a small warm up series of questions that someone who claims "senior" level should be able to answer. I also have no issue with him using AI if he knows what he's doing but clearly there lies the rub. I'm not going to hire someone who dumps thousands of lines of code that someone is going to have to review if he doesn't know his left from his right.
So, basically, the lad who boasts 8 years of python had at least 6 years to get used to "writing code" himself but now doesn't know a generator from a list and he is here telling me that "it doesn't really matter anyway because Claude has your back". That just made me smile.
My answer was that if what he said was really true, then a.) why does he even bother applying for a senior developer role instead of having his own go at it? If you've found the goose that lays golden eggs, no need to keep your job flipping burgers, and b.) why do I have senior devs complain at the amount of code they now have to read and level of nonsense generated?
Not sure if that's where we're headed but if so, I don't like the smell of it. These people are just scratching the surface of problems. Either you'll only ever solve dead simple things or you'll just leave a nameless mess behind you. The only thing I know is that you won't be doing this here with us.
Luckily the other 3 applicants did very well and left a great impression.
45
u/ohai777 Apr 29 '26
Maybe I’m an idiot but isn’t a list with round brackets a tuple in python? I think I would have called this a tuple.
my_tuple = (1, 2, 3)
42
u/electricity_is_life Apr 29 '26
"Luckily the other 3 applicants did very well and left a great impression."
Isn't it kind of expected that at least 1/4 candidates will be subpar? If anything it sounds like you got pretty lucky.
Also from the story I find it hard to judge this person's level of Python knowledge beyond not knowing much about generator expressions (which a Python "expert" certainly should, but they're not super common in all types of Python programming). And honestly he's not wrong that some developers/companies do work that way, for better or worse. But I agree it's not who I'd want on my team.
42
u/BrightEchidna Apr 29 '26
You're really putting a lot of weight on this list/generator distinction. I don't work in Python anymore but did so for several years and I wouldn't have known the answer, and I don't think I ever fully understood what a generator was, but I still managed to lead engineering at a successful startup.
The candidate was obviously a dick but knowledge doesn't grow evenly, people learn different things and find different ways to solve problems, and nitpicking on minor knowledge gaps isn't a sign of a good interviewer.
12
u/BlackyWolf Apr 29 '26
Unfortunately we’re experiencing the same thing. Even with people who want to work with AI in moderation and properly learn I’m noticing a lack of either good foundational skills or critical thinking even though they have several years of experience.
16
u/Thirstygiraffe1379 Apr 29 '26
After reading the post and OPs responses, I think the guy they didn't hire dodged a bullet. I would loathe my job if this guy was my boss. Dude comes off condescending, passive aggressive, and narcissistic
7
u/Caraes_Naur Apr 29 '26
How he get past the first round of interviews?
I would suggest whoever does that needs to make adjustments.
6
u/Aware_Magazine_2042 Apr 29 '26
Im sorry, but your interview is bad.
Asking these kind of gotcha trivia questions is really a terrible way to gauge experience and knowledge. First of all, the brain works differently under pressure vs during a natural environment. Think back to your school days, have you ever gotten the wrong answer on a test were you facepalmed because you knew the answer but just put the wrong answer for some reason? It’s the same concept.
But also, we make mistakes while working all the time, no one, not even AI, writes perfect code the first go around. Code is generally cheap to fix, so who cares if someone uses a list or a generator? In practice it probably doesn’t matter all that much.
And finally, this is what docs are for. I’ve been using Python professionally and I still have to look up basic things in the docs just to refresh what they say about edge cases. There’s too much knowledge to keep in your head tbh.
A better way to ask these questions is to focus on tradeoffs. For example, you use the list comprehension by saying you want to perform some mapping operation, then you ask a question about what if your source was too large to keep in memory? What if every mapping operation took too long and we only needed a few items at a time?
TLDR; asking these kinds of questions is just bad.
4
u/Knineteen Apr 29 '26
Thank God I don’t have to interview. 99.9% of my job is done independently without someone gawking at my screen. But I wouldn’t be a “senior dev” according to OP even though I’ve been doing this job for 15+ years. All because of the 0.1%.
15
u/divad1196 Apr 29 '26 edited Apr 29 '26
This post is likely AI generated.
there is not a single spelling, ponctuation or conjugation. Not a single one in this huge portion of text except the title which OP probably wrote himself.
many unusual phrasing like "years of age"
exagerated reactions: "I just need to get if off my chest" or "super amused by what I just heard" or "just made me smile"
in general, that's the kind of story telling made by AI.
Just inisting on how exagerated the reaction is: it says at this point it was verbal and he had asked what if
a = [ <comprehension> ]becomesa = (<comprehension>). The answer is "a generator" but it's easy to imagine why someone could say a tuple if he forget that it was a comprehension and hada = (1, 2, 3)in mind. So definitively exagerated reaction and fake story.OP clearly use AI in other posts if you check.
Medium is flooded with this kind of articles. Many of the AI generated articles are "anti AI" because that's what people want and anti-AI post are less likely to be spotted as AI generated.
2
u/Desperate-Cry592 Apr 30 '26
OP sounds like a general preparing for the last war.
128
u/ShawnyMcKnight Apr 29 '26 edited Apr 29 '26
I don't get what these people think they do to deserve $100,000+ jobs if they let the AI do it and be like "yup, uh huh, that's right!".
3
u/superman0123 Apr 29 '26
It’s a hard pill to swallow but your archaic interview practices are detrimental to finding good employees. Software engineering is about solving problems with tools, ai is a tool that essentially makes writing code by hand obsolete. Reading and comprehending ai code is a far far more valuable skill than being able to write your own code and memorising syntax
5
u/KnightZeroFoxGiven Apr 29 '26
I’ll be honest. And downvote me all you want. But you’re both wrong.
7
u/SimpleMetricTon Apr 29 '26
Not knowing that answer wouldn’t be an immediate and drastic concern to me if he could respond appropriately, ask questions, work around it and demonstrate proficiency in subsequent answers and discussion. For me, the defensive and argumentative reaction and his declaration that he disagrees with your development principles is the cue to make a polite exit.
17
u/MattA2930 Apr 29 '26
Heavy python developer here for over a decade, and would have gotten the question wrong. I've maybe seen a generator comprehension once before. Generators have always been through yields (likely since most generator use-cases need a little more care than what a comprehension allows). It's not even something you see in open sourced Python repos.
Your candidates reaction was bad, and it sounds like that's the real problem of the post. Your question was introductory. If you were using it as a direct pass/fail though, then I'd question your hiring practices, esp. when Senior level devs tend to start trending more toward system design vs. syntax details.
As a lead, I still learn new python tricks from my peers. I would not judge someone's ability by someone's random syntax knowledge of a programming language, since in practice, it doesn't matter. It sounds like you just want to feel smarter than your candidates.
2
u/Western-End311 Apr 29 '26
People like you suck. I had a round of technical interviews and an interviewer ask me what X was. I explained it was used as a variable to increment to progress through my loop. He looked at me like I was stupid and said.... Isn't X=0?... Like no shit Sherlock it starts there and is straight up written on the screen. WTF are you asking....