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
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.
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”.
[deleted]
The gaming industry is not exactly known as a high paying industry or one with a great work life balance.
[deleted]
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.
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.
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.
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.
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.
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.
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.
I think the ideal might look something like:
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.
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.
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.