What interview process helps discover if a candidate is a good fit for senior software position?

We've all seen posts about how the hiring process has changed and might be even broken but do we know what atrributes make a candidate a real honest good fit to the company?

I've interviewed with a few companies as an applicant and it's becoming a strange phenomenon to structure every job position in the software industry with at least a grueling 3-4 hour per interview session which might be a couple of rounds. Beginning with the projects you've worked on and then the leetcode grind which makes no sense as most people don't use that at such high levels. So I just want to know if there has been any forms of stats recording and sources out there that this type of interview format generates real hard results on quality candidates.

I also feel interviewing has greatly changed over time with the world job market and not just software industry but it's just more apparent with our industry.

I might be applying to the wrong companies here too so that might explain the whole at crazy interview process of knowing leetcode hard as a minimum.

Posted Jun 24, 2021, 10:54 PM UTC

911
mniejiki•

The companies who have enough hard data will never release it because it is a competitive advantage to them. However if you look at the interview process of these companies (FAANG, etc.) you do see similar approaches so likely those have been found to provide the most value to them. Keep in mind that these companies must account for preventing fiefdoms, bad interviewers, discrimination lawsuits and a whole lot more as part of their interview process. So it's not a one size fits all answer and their approaches are not optimal for other companies.

However a smaller company has the option of guessing without data or following the tech giants despite not having the same goals. No real winning strategy. If nothing else since most everyone is doing leetcode you at least don't annoy candidates more than most other companies.

11
Dramatic-File-6196•

There's irony here. They released reports years ago that it correlates poorly with job performance.

2
metaconcept•

That's the billion dollar question. I'm not convinced that anybody knows the answer.

The interview process isn't only to find the best candidate, it's to weed out the bad candidates. If that fails and you hire a bad candidate, it's hugely expensive for your business to get rid of them. The top candidates aren't really even in the job market because they've been snapped up already or started their own businesses, and the bad candidates are plentiful in the job market because they don't get hired.

I suspect that leetcode is effective at weeding out bad candidates. We absolutely hate it, but the big companies continue doing it, so my theory is that they have evidence that proves it's effective.

Personally, I'd like to work with someone for a while first before deciding to employ them, but I don't know how to do that. Maybe start with a 6-month contract?

10
Groove-Theory•

I suspect that leetcode is effective at weeding out bad candidates. We absolutely hate it, but the big companies continue doing it, so my theory is that they have evidence that proves it's effective.

This has been the case for other strategies such as puzzle question or man-hole cover questions. Big companies like Microsoft et al were using these for many years until they realized it wasn't working. But in 2006 the notion could be "well the big companies talk about manhole covers so maybe there's evidence", when in reality, like most people, we're just making shit up on the fly because no one knows what they're doing and just copying whoever they think is successful.

In all honestly, people should just simulate what's going to be on the job and ask people experiences or questions based on what's going to be on the job. What evidence does something like a dynamic programming question about stock market prices (true story) going to provide if you're not going into fintech? Or a questions about seating arrangements for an airport on the maximum number of 4-person families can sit next to each other (true story, again) when the company product was a CRUD organic food app.

In my experience, if a candidate can show me they can do the job (based on a real-world simulated environment or high level discussions), I've never seen a difference in whether or not they can think of a near solution to a riddle (be it leetcode or some arbitrary system design i.e "How would you design Google Maps" when you're applying to some shit startup in the midwest)

If you like puzzles pick up a Sudoku book. If you like engineering, join my company because we're hiring.

2
[deleted]•

[removed]

1
mobjack•

Interviews are structured like that because they work reasonably well for finding qualified candidates.

Companies have a lot of feedback in their hiring process as they get to see how the candidates performed afterwards. If they were getting bad hires then they would adjust their process until they find something that works.

If someone has data that another hiring method is better, then I would love to hear it. Until then, I am going to do what works.

3
[deleted]•

[deleted]

1
StevePilot•

Senior dev isn't such a high position that you wouldn't need to be a good developer. I can't even think of anything a senior dev wouldn't be expected to be able do that a normal dev would be expected to be able to do. So your assertion that seniors shouldn't have to leetcode due to their high level sounds like complete bs to me.

0
[deleted]•

My focus is about asking really intensive leetcode questions... Yeah sure you're paid to problem solve but leetcode doesn't really form a bridge to what is expected on the job. Most of the time these leetcode questions are so low level that 95% of the front end jobs out there don't need to focus on them squarely. We already have patterns, concepts and frameworks to use that have already been researched by PHD's to use... We shouldn't try to reinvent the wheel unless it's absolutely needed but a ton of companies think their candidates need that.

I keep mentioning if your company squarely focuses on making algorithms for their business then fine ask the hardest leetcode question in history but if the resposbility is creating a front end website then to me it's GTFO. I'm not going to whiteboard and peform big O analysis on some front end UI everytime I code. But I would indeed think of the design and resuability of it which is totally different from leetcode.

1
StevePilot•

You still need basic programming skills, despite there being frameworks for most things.

I'm not going to whiteboard and peform big O analysis on some front end UI everytime I code

That's fine - that's more job security for me. That attitude is why the outsource teams we hire write so much front end code that needs to be re-written due to performance problems.

1
[deleted]•

Re-writing code isn't a result of poor performance only... There are many things to take into account maybe there was a bug, expanded feature, a new technology to adapt to or it's just flat out unreadable and unmaintainable.

Only caring about performance actually leads to more bugs believe or not because so much effort is put towards that aspect instead of the overall design.

1
StevePilot•

Re-writing code isn't a result of poor performance only...

I didn't say it was. It's like you hit your head and became confused... But I also ask them to re-write for clarity / maintainability.

1