Anyone notice senior interviews are getting more focused on intangibles, personality, niche backgrounds?
Posted by SpicyFlygon@reddit | ExperiencedDevs | View on Reddit | 29 comments
Just wrapped up a hiring round. 8yoe mostly in backend/data in finance. One thing I noticed vs previous job hunt rounds is that my hit rate for recruiter screens was actually much HIGHER than usual. But I would consistently hit a brick wall at the technical resume review or system design round.
Companies were asking more open ended questions and less trivia or hard technical stuff than in years past. I get the feeling companies are now prioritizing for a very specific background or personality type, not just skill. I’m not sure exactly what background they want, just that I seem to not have it. I’m starting to worry the industry has just passed me by.
I ended up taking a public sector job and hoping to pivot to cleared contracting in the future. But this round has made me worried that I am becoming unemployable in the private sector. Has anyone else experienced this? Can any hiring managers comment from the other side?
try-catch-finally@reddit
I currently am at a small startup, interviewing for senior+ mobile dev to lighten my load.
Already had two people exited because of culture non-fit. Technically they were stellar on paper - but they just were not fitting into the flow or dynamics.
So yeah. You may be a genius but if you’re a dick (not saying OP is) it’s not worth it.
Aggressive-Exit8195@reddit
Can you tell me some of the more important cultural fit characteristics/things?
MysteriousMatter1256@reddit
Don't you think this is because of LLM era where technical stuff isn't that important anymore?
Inside-Froyo4378@reddit
This is a good thing. I'm making senior this year and still haven't done a leetcode. Thankfully my employer cares more about money than internet points.
DeterminedQuokka@reddit
How much experience do you have? I think that this has always been the case in the higher levels. I did interviews 6 months ago and they were basically the same as the ones I did 3 years ago.
Senior interviews in my experience have always been focused on “are you good at the thing I need you to be good at”. Which is usually like planning and leading. And are usually focused on actually asking people to tell you about their success in detail.
I will say that someone told me they expect staff engineers to be worse at technical interviews than seniors. But I also think that’s not new.
I have the most experience doing interviews and I’m for example doing the exact same system design today as a I was doing 10 years ago. And have done it at 4 different companies and I’ve never been the one who chose it.
The tech depth I do now is the same as the one I’ve been doing for 7 years.
The only change I’ve seen is that we added an ai interview.
brainrotbro@reddit
Good bc I personality the shit out of interviews.
subma-fuckin-rine@reddit
for the personality part, yes 100%, but its been that way for years. i've got 2 jobs in the past where the team admits there were other equally qualified people in the running and they chose me for personality and team fit as the "tie breaker" so to speak
DoctorWaters@reddit
Yes, for my current job my technical interview was more of a vibe check with some architecture questions. The previous step was an interview with HR and the HR girl and I are from the same town which turned out to be very positive for me.
Melodic_Crow_3409@reddit
Better than Leetcode. I’m 55 years old have worked in the seniors since like 20 I have never had to do Leetcode on my job. I have no time for that horse shit. I’m way too old to start drilling it just to get a job.
Pawesome101@reddit
agreed, these types of interviews are dead. even at the junior level seems irrelevant to test for.
Melodic_Crow_3409@reddit
My favorite types of interviews to give is just having the candidate go up to a whiteboard. I'll describe a business problem that is in some small way related to something that we've already solved. Nothing that requires Einstein, but something that requires knowledge of design.
Something like, create a system that will create new car objects. Design the car. Now, what about different models, how would you handle that? I'm looking for a basic Factory pattern, but if they come up with a solution that's good that I've not thought of, that's cool too.
beluga_ciabatta@reddit
This is a good thing imo. After a certain level of knowledge and experience, personality and fit matter more. You’ll want a new hire to fit into the org correctly and not be a lone wolf, otherwise you’ll be trying to fill that position again in a few months or years. I’d rather work with someone who is teachable and friendly than a cracked genius who is a jerk or anti-social. This is coming from 17 years of professional experience - call me a chopped unc programmer.
SpicyFlygon@reddit (OP)
I agree, lone wolves are not good for a team. But that's not what I've noticed companies hiring for.
I think it's more like the specific background they want are getting more narrow. For example, it used to be if you worked at a bank your skillset would be considered reasonably transferrable to like, a wealth management firm or fintech, etc. I think they are looking for ultra specific business and domain knowledge.
I also think companies are reverting to strong preference for tenure. Maybe they've been burned with over leveled engineers from the hiring boom and preferencing candidates at the top of the yoe range. Maybe 15 yoe is the new 8yoe for senior/lead
tankmode@reddit
I think that happens when the labor market is tight. the hiring companies shift their standards to people with the exact background they want (industry, domain expertise, tech stack, level) because theres so many applicants that meet a lower standard
as an aside I would sat 8 yoe is peak then it goes downhill. once your older and more experienced than the hiring manager you get x’ed out of a lot of resume screens. the middle management chain usually wants cheap, malleable, compliant employees below them. high yoe has certain strengths but it is usually not that.
Teh_Original@reddit
For the average company you will have to rehire in a few years anyway because the average company doesn't keep wages competitive for existing hires.
fmmmf@reddit
Honestly good. Software engineering is a highly collaborative endeavor, you want people with decent energy and EQ to have the discussions needed to map out architecture/run post mortems etc, the ai tools can do the actual grunt work.
throwaway_0x90@reddit
Absolutely, because that's the future of SWE. More softskills required.
Pawesome101@reddit
but honestly, isn't this just a better way to hire?
nrith@reddit
Sounds great to me. That’s what tech interviews used to be like. Who cares whether I can answer a LeetCode problem that any Codex can do easily?
snotreallyme@reddit
When there’s such a massive glut of candidates as there is now employers can be picky, very picky.
ilikeaffection@reddit
Most of the interviews I've done, even the technical ones, tend to be conversational and focus on background, like, "When you worked for [company], you say in your resume you [accomplished thing]. Tell me [details] and what things stood out to you as surprising when it came to implementation."
I did, however, have an interviewer have me open up VSCode and solve FizzBuzz while sharing my screen just recently. I guess they get a lot of ppl who either lie on their resumes or they're looking for super clean, optimized answers. It's such a cliche puzzle, I can't imagine there's many who haven't seen it.
SpicyFlygon@reddit (OP)
Yep the background review format is still the most common for those rounds from what I've seen, but it feels very different and more specific these days. Previously, companies were looking for ability to deliver, deal with roadblocks, optimize, make tradeoffs, etc. It felt like they were assessing general engineering ability.
Now they want someone who matches their situation exactly: your roadblocks are their roadblocks, your tradeoff decision needs to match their tradeoff decision, etc. The criteria have just become more niche
slimracing77@reddit
I think it’s just a reflection of the market. Any position gets hundreds of resumes within a day or two and if you’re going to have to sort through that might as well hold out for exactly what you want.
Also agree with your earlier comment regarding tenure. The days of 3yoe “senior” people are gone.
originalchronoguy@reddit
I haven't interviewed candidates much in the last 6 months (due to budget). Prior, I was always interviewing potential candidates. I've always had a particular profile in mind so this isn't something new.
What I looked for his how compatible they were and how quickly they could onboard. If I was hiring for a project with a 6 month timeline, I can't afford the luxury of a new hire learning the ropes for 3-4 months. For me hiring were often to fill slots for incoming work or incoming projects. So yes, I had to be picky on that profile. An example is, you needed to know how to do REST APIs, you worked in the past writing swagger yaml, you know what an API gateway is. You know how to write a helm chart to deploy a POC or service immediately so someone else can validate. You know how to write performance tuning and how to create observability for disaster recovery. So modern microservices and containerized workflows. There are plenty of people who fit that profile. So why go elsewhere?
smutje187@reddit
I’ve been recruiting for the consultancy I work at for the past few years and we’ve always approached interviews open ended and hired for a mix of experience, behavior and gut feeling - in my opinion, outside of very niche areas where a very specific skill is needed someone with the right mindset and approaches can learn most technologies on the fly - thanks to supply chain attacks and cloud providers enabling the possibilities to deploy multiple languages (and LLM) we aren’t as hard wired to specific languages anymore as we were 7, 8 years ago.
SpicyFlygon@reddit (OP)
Has the way you interpret gut feeling changed over time? And how are you weighing years of experience? Are you specifically looking for like, seasoned old timers for senior and lead engineer level?
NonProphet8theist@reddit
Where? That's all I have most of the time lol
diablo1128@reddit
I haven't noticed anything to what you are describing.
I actually find my 15 YOE on medical devices to get lower hit rates with applications this year compared to past years. When I interviewed with Apple earlier this year it seemed like the normal interview questions, coding, system design, etc... I didn't get an offer, but nothing seem different than past years.
Frankly I think I get less hits with applications because me experience is just not transferrable to other companies. Sure I used c, c++, and python in an embedded environment, but not many companies need that. Those that do need these skills expect domain experience as well, which I don't have.
For example, why hire me in an autonomous vehicle company when Bob has the same c, c++, python skills AND has done path planning at a previous job. Bob is just the better candidate because I would need to be trained up in path planning. Hell Bob may even be better a c, c++ and python than myself.
hypnofedX@reddit
I've taken two interview sets in the last year that would have led to C-suite or Director-level positions within a few years with non-tech companies valued in the hundreds of millions. Both times I made it to the final round of consideration and lost out due to experience. All of the technical evaluation has been conversation-based.