Does the software industry have standards on vetting their true requirements when it comes to hiring?

I'm just curious to see what it's like because it's coming extremely unguided based on some interviews I've been in. I mean everyone is studying data structures and algorithms but I feel like that has way too much and emphasis on the industry and if you miss out on creating an algorithm within an hour you get swooped away as a legitimate candidate. I might just be the only person who is having a terrible time getting an interview that does not emphasize leetcode heavily maybe...

Sometimes I feel that every company started adopting this because mega cooperations started to do this and I feel it's a bit rare to get a question that resonates with the company's product and would be related what you'd be actually working on.

For example, if you're going to be working ln the front end usually you should be asked to implented UI with "X" framework and consume api requests with "Y" framework

Instead companies looking for a new candidate seem to ask more about given possibilities of string or ints design an algorithm thats is optimal to solve it...

I mean if the company truly uses the algorithm at least connect it with what you'd do in the job...

Like I said it honestly might be just me but the industry seems to be horny for relying on algorithms to vet good candidates.

Posted Jan 26, 2020, 2:07 PM UTC

245
Getfitbro•

There is a flipside to this though, where companies barely have a "real" technical round, and most of time just ask some broad conceptual OOP questions and check for a cultural fit. Maybe they would have some sort of a small POC before onsite or very simple coding exercise during onsite. Then you end up with a crapshoot of knowledge and quality. There should be some happy middleground without whiteboarding for 5 hours and yet actually testing applicable skills.

11
Scarface74•

Why is this a bad thing? Aside what people think in the Reddit bubble, most software development is about boring yet another software as a service CRUD app or a bespoked internal app that will never see the light of day outside of the corporation

Most developers aren’t doing anything approaching “algorithms” or “leetCode”.

9
[deleted]•

[deleted]

2
Scarface74•

The gaming industry is not exactly known as a high paying industry or one with a great work life balance.

1
[deleted]•

[deleted]

2
Getfitbro•

Because then you end up with really shitty designed CRUD apps without utility/service classes, automated unit testing, an ability to effectively communicate to RESTful services through a standardized interface, etc. So you acquire years of shitty tech debt, and ship apps with deep dependencies that are held up by scotch tape and shoe strings.

Then it costs the company millions of dollars and several years to refactor that shit to scale. All of this due to poor hiring practices, poor development practices, and lack of mentoring.

1†
Scarface74•

I agree. But none of that has anything to do with your ability to reverse a binary tree on a whiteboard.

So an interview that focuses on architecture, clean coding concepts, real world trade offs, and delivering software that has business value should be emphasized.

11
Weak-Constant•

You're just rehashing the same old bullshit complaints that everyone periodically has a tantrum over here.

If you can come up with a concrete improvement to how people interview, that still fits into a 1 hour slot and gives me reasonable confidence that they can code, please let me know what that is. Having them memorize and regurgitate clean coding concepts doesn't sound like that to me.

-4
TheWrightStripes•

The best one I've ever seen was what we did at my last job. Have them do a design session for a familiar problem like how an elevator might be programmed. After going through the session and discussing their solution and prompting them if they get stuck, the next exercise is giving them a laptop with language/IDE of their choice that had a project built out with classes and tests. They had two or three methods to implement to make all the tests pass and we gave them about 2 hours but allowed them to work on it longer if they wanted more time. Google/StackOverflow/etc were all explicitly allowed.

4
ANormalSoftwareDevOP•

That's the thing that companies have to realize is that they really need to know what they need before advertising a position to the market. I get that algorithms is a important foundational block in computer science but in today's world of programming I've only made maybe a couple of algorithms in my entire 7 years of working the field. Organizations that heavily use algorithms would be real low level companies that basically manufacture the processors that software developers create software for.

There is a reason why libraries are around so that people don't keep re-rewriting the same dam software over and over again which how the evolution of higher level languages and frameworks came about. In your career progression, your job becomes more on code design and ensuring the code is performing well enough which deals with big O notation anylsis and scalibility (yes this deals with algorithms to an extent). I'm a little shocked with companies not even mentioning code design questions on patterns and approaches to solving problems.

I've yet seen a company I applied that glazes over a few OOP concepts and pushes in the culture fit which probably means the area that I am at has a different mentality of the industry. I don't like how in the technology industry copying another company's (FANG) idea is the only way to only move forward instead of fostering innovation within the company itself to prosper which I see happening quite rarely.

2
kiss-o-matic•

I'm a little shocked with companies not even mentioning code design questions on patterns and approaches to solving problems.

I have been saying this for years. My last place had a ton of really, really smart people... but they were all given a ton of freedom on overall design, and the repo showed it. 3 -ways to encode a UUID -- and not one of them conformed to a single standard. So eventually there was a project to real it all in and have an all encompassing framework and cut down on code re-use. Of course, that took a shit load of man hours that could have been saved with a bit of vision, constraints and agreed upon design patterns.

I had the easiest phone screen in a while the other day (Two sum basically). But he DID ask me -- "okay, what unit tests would you write to make sure this always works?" That raised their stock immediately.

2
almondcroissant96•

For one data point, my company has a relaxed technical round and our engineering quality (imo) is high. We don't hire entry level at all, only hire seniors and return interns as juniors. By the time someone is applying for a senior role, I think it's pretty easy to judge them based on their work history and phone screens. And the juniors are effectively interviewed for 3 months, so there is a strong quality filter there as well.

2
alecbenzer•

I think the ideal might look something like:

  • coderpad phone screen
  • 2-4 hour "take-home" style onsite project
  • For more senior candidates: a design whiteboard
  • 1-2 non-technical assessments
-1
Scarface74•

I would do a hard pass on any interview that required a “take-home” test unless there were paying way above market average.

I might be willing to do a “coderpad” interview, but by the time I jumped through all of those hoops, I probably would already have an offer in hand. I’m no special snowflake, but in my market, senior engineers come on the market so infrequently, that they are swooped up relatively fast. It’s never taken me more than two weeks to go from looking to an offer letter.

I suspect it will take longer next time because I would be very picky.

An architectural white board design session I would be more than willing to do.

Any company that emphasized “coding” over architecture would also be a hard pass. I turned down a job that focused the interview on whiteboard coding more than architectural and process questions.

4
alecbenzer•

I didn't mean that you'd actually do it at home, just a longer more practical coding exercise vs. several shorter whiteboards. It does a better job of checking the "can you code?" box and doesn't require brushing up on more esoteric algorithms.

I don't see any problem with jobs assessing my coding ability in some way before hiring me to write code.

2
Scarface74•

Sure, I’ve both done coding interviews and administered coding interviews.

My model is to have a skeletal project with failing unit tests where they have to write code to make the unit tests pass. But it really doesn’t take 2-4 hours to determine whether someone is not at the “don’t eat the chalk” level of ability.

1
IgnorantPlatypus•

I usually don't respond to these, because there's never anything conclusive happening in the comment threads. People come in with assumptions and leave with the same thinking.

So, consider that the industry is broad and vast. And so things that are common, and easy, and done all the time for some devs are never done by others.

And consider that this is almost the equivalent of finding someone to marry, after 1-2 dates, and you only have about 6 hours with each candidate because they have lots of other prospective partners and they're still in a relationship. So what do you do in 6 hours to figure out you want to be with them for years?

Do you ask task-specific questions? That has several issues: what if you want them to do more things in their tenure with you? What if they're moving from some field to yours? Why do they need to know how to do something that they could learn in a month or two, unless you need them productive on day 1?

Do you ask about past work? Will you have context to understand it? Will you run afoul of the problem that anything other than a pure technical test opens up bias where we choose people like us, not the best talent?

So the only safe-ish thing to do is fall back on asking questions about fundamentals; this is a technical assessment, and there's generally an assumption that people can learn anything else once they have the fundamentals.

And then you get people studying leetcode, because asking questions about the fundamentals is hard too.

EDIT: The best book I read about interviewing and recruiting is actually Inside Delta Force by Eric Haney. The first part of the book is about their selection process. While Special Forces and software have almost nothing in common, the point is that the folks founding Delta Force knew what the most important attribute was that a candidate could have. And then they built a test that they believed would show that attribute.

Where I work, we're explicit that the thing we want to hire for is "people who can solve problems". And designing a test for that is of course challenging. But we want to watch a candidate solve a problem with us in an interview. Of course these problems are narrower in scope, since they can be solved in under an hour. And it's quite possible that most companies don't know what qualities they're looking for in a candidate, and haven't even tried to design an interview to reveal whether a candidate has them.

2†
freework•

And consider that this is almost the equivalent of finding someone to marry, after 1-2 dates, and you only have about 6 hours with each candidate because they have lots of other prospective partners and they're still in a relationship. So what do you do in 6 hours to figure out you want to be with them for years?

What the fuck is wrong with you? A co-worker is nothing like "someone to marry". I absolutely hate this idea that finding a co-worker is exactly like finding a co-worker, and since it takes months and months to know you want to marry someone, it should also take months and months to find if someone can be your co-worker. A co-worker is just someone who sits next to you at the office. A significant other is someone you sleep with. There is a pretty big difference there.

Ask a person over the age of 60 who has been with their current company for 30 years what they went through to get hired. I guarantee you they didn't have to go through multiple rounds of 6 hour interviews before they were offered a job. They likely just walked in, asked for the manager, gave a firm handshake, and then was offered a job. This idea that candidates have to be put through a gauntlet has only started in the past 10 or 20 years. Fuck pieces of shit like you that encourage this behavior.

3
IgnorantPlatypus•

What the fuck is wrong with you?

I too enjoy engaging in calm, polite discussion!

Hiring and firing is substantial work. As is divorce.

While the relationship isn't one-to-one, there's still merit in the analogy that you're going to be near this person for years, you'll have to trust they're doing the right things, and a bunch of other things for which there's no other close analogy.

Also, not all marriages have sex in them, even if most do, but sure.

Fuck pieces of shit like you that encourage this behavior.

Where did I encourage multiple rounds of 6 hour interviews? I suggested that there was a total of 6 hours of determining if someone is an appropriate hire. You've read an awful lot into what I said, which says way more about you than about me.

4
freework•

Hiring and firing is substantial work.

No it's not. Look at how it was in the 1960s. All you had to do was walk into a company, ask for a hiring manager, give a firm handshake, and then you were told "welcome aboard, son". It's only "substantial" today because morons like you choose to make it substantial.

4
Getfitbro•

Go work at a factory in the 60s. You couldn't walk into NASA and become an Aerospace engineer then either. You can probably get a low skilled job with a handshake and enthusiasm today too. Nobody wants to spend time and energy to train someone on a complex job without apparent background knowledge and aptitude, as well as basic soft skills and being able to work in a team.

You are a classic example of this

2
ltran96•

Why are you so upset about his analogy? Are you taking out some personal resentment on the recruitment process or something? Software engineering is inherently a collaborative job and you want to make sure the person you're hiring is somebody you can work with. It's not the 60s anymore, and companies err on the side of not hiring a competent candidate over hiring an incompetent candidate precisely because of how difficult and long the process is to fire people.

Also, I don't appreciate how rude you're being to IgnorantPlatypus. All he's trying to do is have a calm discussion and you're not only accusing him of encouraging arduous hiring interviews, but you're also ignoring his rebuttal and strawmanning and cherry-picking his responses.

2
[deleted]•

[deleted]

1
[deleted]•

[deleted]

1
[deleted]•

[deleted]

1
[deleted]•

[deleted]

1
IgnorantPlatypus•

morons like you

Your continued efforts to be polite and reasoned are appreciated!

So you're assuming that the interview is the only thing that takes work when hiring or firing someone? Because your response surely implies it.

Also, getting a job in the 60s worked that simply if you were white and well-connected. Is that a world we want to go back to? Or would something closer to being hired on merits be better? Are women allowed to be eligible for this simplified hiring mechanism or does it only work for the menfolk? (The "son" in your example). And what if someone hires one of the many developers who can't even pass the FizzBuzz question?

You clearly have experiences different from mine, but so far you've made no efforts to be anything but rude and dismissive about them. I really hope you're like this only with strangers, but even with internet strangers it's a really terrible way to go about engaging with them.

EDIT The above was a bit snarky, I support, and I apologize. But still, you've offered almost nothing substantive but insults and some vague idea that "it was easier in the old days" and that it's somehow my fault.

0†
RootHoustonSoftware Engineer•

I have interviewed and hired many candidates for sysadmin roles, and if we were to put someone through 6 hours of interviews, they would've just walked away from the thing. It's a sign that the company expects too damn much. It's sad that the mentality of many on the dev side is so different.

2
IgnorantPlatypus•

What was the interview structure you used to determine if a candidate would work out? How well did your structure produce results that you were unhappy with?

1
ANormalSoftwareDevOP•

While I agree with some of your post part of the problem I see with most of the industry is that companies place too much weight of a specific subject to quantify one's potential.

With your example on the delta force vs software developement you try to pin down certain qualities you want in a candidate but is that truly what your organization needs or is that a trend you're following based on the industry?

Companies are all different and finding the candidate for them needs factual data to themselves and not comparing companies that seems relevant. I mean they can start with the trend then move forward on to evolving it but relying on the trend alone seems real foolish.

If your company is finding overall success with the trend fine I get it them keep going with that but if they have trouble finding a web developer but expect them to know low level machining aspects then I don't feel sorry for the company.

2
IgnorantPlatypus•

I've heard of both sides: an interview loop too focused on specific job skills that are learnable, and an interview loop completely focused on fundamentals which are not relevant to the skills needed for the job.

We've been trying to figure out how to customize our interview loop for some of the more niche work we have, so that a UI loop isn't the same as core s/w. And yet we want to be cautious, because we allow people to move between teams and groups without re-interviewing, so we don't want someone to pass an "easy" loop then move to one of the more intense areas of the product.

I would generally agree that it's very likely most companies aren't thinking a lot about it and are just mimicking what they see done elsewhere.

1
ccricers•

Knowledge can be divided into tacit and explicit knowledge. Explicit knowledge is stuff you can Google up and answer for interviews in a snap, or to win bar trivia. You definitely don't want to focus too much on that knowledge or it will encourage a fair bit of cheating. If their tech questions on the other hand seem easy and superficial I am going to bet on them putting a high importance on culture fit.

Companies that copy FAANG interviews "just cuz they did it" are fortunately companies I rarely encounter where I live. Questions are usually more grounded like, "how would you design this simple app in React" or "figure out how to filter SQL database results with joins, okay now do it without joins." There isn't a high level of specialization in most of the places I worked with, so in a sense they are also switched around but just with different responsibilities and not teams.

1
IgnorantPlatypus•

Both your example questions I have no answer for, because I've never used React, or SQL.

So ... are those kinds of questions also too much like a specific skill? Or does the team need someone who can do them on day one? Or is it still not "fundamental" enough? The answer depends on the company's needs, I'd think.

1
ratfaced_manchild•

Great answer, I'll have to take a look at Inside Delta Force.

1
kiss-o-matic•

As an experienced candidate I'm finding it a mixed bag. In my domain, I've only had LeetCode heavy hoops at the initial (automated) stage then maybe like one algo-ish question but with a more real life setting later. One place had a real-world challenge on hacker rank which wasn't too bad. Then a phone VERBALLY asking about algorithms with a very non-native English speaker with a very soft voice. Imagine Jian Yang from Silicon Valley mixed w/ The Puffy Shirt maker from Seinfeld. I did not pass that stage, despite giving, what I thought, were accurate answers. It raises the question if he really understood me.

Anywho, I've had some initials screens (in my domain and out) ask me about either CS fundamentals (hash map is a fan favorite), particulars about OOP and how it works in my language, or the most popular one: concurrency (and specifically how it works in my language). A challenging one was someone that wanted a high level view of a concurrent hash map -- I got it "to work" but had no answer when it resized itself. Another that I didn't pass went into a crazy deep dive about internals (sockets and of course, concurrency).

So yeah, I feel like maybe at this age there's a slight disadvantage on an average interview. We stray from the academic for the practical as time goes on, so need to refresh on DS&A. However, you may get in an interview and they don't ask you shit about DS&A (where you've been spending a substantial amount of your study time).

2
Reasonable_Policy•

There's a few reasons.

  1. Google does it. Other companies just copy what Google was doing even though it doesn't make a lot of sense for smaller companies to eliminate good candidates with CS puzzle questions.
  2. It puts the candidate in an inferior negotiation position. If you feel like you barely got an offer, you're less likely to ask for more money.
  3. It provides a legal cover to discriminatory hiring practices. Tech companies don't want to hire white or Asian males and they want to remove older employees who may ask for more money and time off.
0
[deleted]•

[deleted]

1
kiss-o-matic•

I get the age thing but I'm a bit lost on how white/Asian males are at a disadvantage w/ CS puzzle questions.

1