Related Posts
3/29 Thread (General):
I hate going to the Apple Store nowadays.
Additional Posts in Ask A Recruiter - Tech
What do you like about working in tech ?
Any recruiter in search of a Scrum Master 🙂
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.




Bowl Leader
It really depends on the role. I know this may sound negative, but if it's for a maintenance or support role, the list of technical skills is priority over the other questions or feedback.
However, if it is for a career track either in engineering or management, these are always problem solving questions. These are just different sets of expectations because the type of work each track presents.
That’s an interesting distinction. The expectations likely shift depending on whether the role is focused on execution or broader problem solving and ownership.
Mentor
Both get evaluated, just at different stages. Early screening often looks for tech stack alignment because it’s a quick filter. Once that baseline fit is there, the conversation usually shifts toward how you approach problems, make tradeoffs, and deliver impact.
That’s a great breakdown. Tech stack gets the door open, and the problem solving approach seems to matter more as the process moves forward.
I go based on the questions. I’ll get a feel for where they are most interested. If I’m really unsure, bring up the specific tech I used and how I used it to solve problems. Best of both worlds.
That’s a smart approach. Connecting the technology directly to how it solved a problem usually tells a much stronger story.
It tends to depend both on the role, and how technical the recruiter is. I find it's usually pretty clear early on that they aren't liking the logical side of my answer and would rather be checking off boxes of tech I've worked with.
Good point. The recruiter’s technical background probably shapes how deep the conversation goes beyond the tech checklist.