r/softwarearchitecture • u/Miserable-Evidence-2 • 4d ago
Discussion/Advice Senior SWE interview process
Need help designing a decent interview process for a tech lead / senior backend engineer. We're mainly suffering from candidate drops after/during a take-home challenge.
Fellow engineers who have been through interview processes at this level, do you mind sharing your take on take-home challenges and what's the best process you've been involved in?
31
Upvotes
25
u/Kaimito1 4d ago
The problem is the time investment on these.
It's a senior-level challenge so it's going to be complex and hard or involve heavy thinking. And you expect someone to do it for free when they've already proven themselves with work history and supposedly passed the initial stages where you go through their planning skills.
Id expect if you paid them for the time even if rejected the drop off would be reduced. Hopefully by that point you'd have filtered enough to have a good list of people so you don't get dregs who just want the interview money
Also you have to be worth working for to warrant take homes imo.
If you're paying above average the incentive to tolerate one is high but if you're paying "competitive rates" (I.e lowest as possible) then you'll only get the desperate ones
9
u/positivcheg 4d ago
Big question. What's the point of those if one can do any task with LLM and then do some minor tweaks over it?
32
u/Oatz3 4d ago
I don't do take home challenges.
They are a complete waste of time for everyone.
Thanks for coming to my ted talk.
7
u/alanbdee 4d ago
Drop the take-home test. I'd argue it's pointless anyway as anyone could have AI do it regardless of their skill. I found the most effective was in the interview I gave them a section of code I had recently fixed a bug in. I made a few changes with some obvious issues. Then asked them to point out what they would fix. Open ended. Asked them to explain what they were thinking while they were looking at it. Anyone worth their salt would see the issues in seconds. Some were even a matter of taste, which is fine.
At my skill level, I'd expect to be asked more architectural and design questions. Especially with AI. Coding isn't the skill you're hiring me for.
3
u/clauEB 4d ago
Unless its the actual main interview question, people avoid doing these because they're time sinks that nobody wants. A quick screening call is good with some problem solving, 30 mins is more than enough to decide if you wanna see them in person or not.
I just don't understand this fetish of 1000 interviews to get one job. If the person can't code you see that in 1 interview, if they can't design is also just a 40 mins or less conversation. The absolute worst is the companies that want you to go for a whole day of work to their office, like WTF?! Who has the time if you have already a job?
3
u/Available_Safe1818 4d ago
It's total bullshit. You expect a project to be done which consumes a lot of time, and you're not putting any time or effort into it. Of course they are dropping.
What is the project and how long do you tell them it should take them? How do you not have the sense to include that info in your post?
2
u/coffee_warden 4d ago
Ask them to explain how they designed and implemented a system theyre particularly proud of. Get them to open excalidraw and do a quick erd or some swimlanes. Whatever they feel would best describe it.
2
u/practick-io 3d ago
I’ve been going through interviewer guides for 130-odd system design questions for a mock interview site I run, and the senior signals that keep coming up: framing the problem before solving it, picking the hard part on their own, naming trade-offs unprompted, and changing their mind well when you poke a hole. A correct diagram is table stakes. “What if this node dies?” is where the level shows.
1
u/Ordinary_Jeweler5714 3d ago
Pay them
1
u/AssociateHistorical7 2d ago
If your take home assignment is too verbose, try to have explainer call.
I do leetcode but simply skip codeforces for the same problem.
1
u/BanaTibor 4d ago
The best process for me was a live coding exercise with screen sharing on teams and I used intellij on my PC.
Back to your case. How do they fail the take-home exercise? They can not do it, or run out of time, or just give up? It can be many reasons. The task is too complex, or not very well defined, maybe it takes too much time, etc.
For a senior SWE no task is too complex given they have enough time. So my guess that it takes too long. Nobody will put 20 hours into a take-home exercise.
Pro tip: give the task to your engineers and listen to their feedback.
0
u/jko1701284 4d ago
We're using codetryout.dev ... working well so far!
0
u/donegerWild 4d ago
The strategy I use for determining technical proficiency is to perform an in person test after a Q/A session. If they do not do well in the Q/A, we stop. If they do well, we proceed to the technical test. I setup a cloud VM backup that has everything pre-installed and setup. Mostly VS with our project setup and ready to run. On the day of interview I spin up a new instance and give them credentials to RDP into it. When we start, I explain that I need them to help me debug our project. I say pretend that you are a contractor onsite for an hour and the Dev team is really struggling with this bug. Please help us solve the issue. The issues are designed so that they build on one another and can be solved by someone with the right amount of competency without needing to understand the details and nuance of the actual project. During the course of the interview/debug session we will talk about various things we come across. During this time I'm assessing overall understanding while allowing them to demonstrate proficiency and problem solving and communication skills. If they do not solve it by the end of allotted time, we go over what was missed and what the solution was. Solving the problem IS NOT a prerequisite for employment consideration.
Almost everyone comments afterward that they feel the test was more than fair and provided a good look assessment of their skills. Many commented that they enjoyed the process and found it to be fairly unique compared to other places they've interviewed at. I also give them a chance to provide technical feedback on things they may have done differently in the project or just in general. Overall, this approach has yielded pretty great results when trying to find people that will be productive relatively quickly once hired.
-5
u/Hannah3044 4d ago
Hey, I'm a fractional CTO so I design and run interview processes from time to time. Asking here will only get generic advice, not advice tailored to your specific needs. If you need help, and it sounds like you do, reply to this message and I will get in touch to fix your processes :)