This is missing the point of interviewing. The goal isn't to find any warm body to fill the chair, the goal is to find someone qualified to do the work who also has a history of doing good work at previous employers. You also don't have unlimited headcount and hiring budget, so it's worth making the investment to find the top 10% of your applicants rather than picking first-come first-serve.
One of the things you don't realize about the hiring market until you've been reviewing resumes for a while is that problem employees are over-represented in the candidate pool. The most qualified employees spend the least time job searching because they're given offers right away. The most problematic and underqualified employees are frequently searching for jobs after being fired or let go. If you sample applicants at random, they're far more likely to be in the underqualified and/or problematic group than in the great employee group, statistically.
The other thing that isn't obvious is just how damaging a single bad hire can be to a team. Hire someone who clashes with their peers and fails to deliver any good work and you'll find yourself losing the good team members very shortly. Nobody likes working with painful coworkers.
That said: The analogy of a "walk-on" job isn't dead in tech. If you pick a company you want to work for, find someone on LinkedIn, and send them your resume with a short pitch about why you want to work there, there's a good chance they'll at least strongly consider your resume. Nobody is guaranteed a job this way, but it's one route to getting your foot in the door even when you don't see the exact job posting you want on the website.
I never had a technical failure in my hires, but I did have a couple of "bad cultural fits." These usually weren't toxic people, but people that couldn't handle the responsibilities and pressures (we were a small, high-functioning team, and everyone's visibility was fairly high).
But this:
> who also has a history of doing good work at previous employers.
makes me wonder how LeetCode tests can tell you that, as they seem to be the single most important component of all software engineering hires, these days.
In my experience, they just drive out the qualified people that can see projects through, and leave you with ... the ones that are really well-practiced in short, academic exercises.
> In my experience, they just drive out the qualified people that can see projects through, and leave you with ... the ones that are really well-practiced in short, academic exercises.
Yeah beats me how anyone thinks LC is useful, other than for weeding out the most unqualified people, like people who genuinely have never coded. I suppose what it really does is finds you people who are willing to put in the time to study all the hundreds of questions.
Yes, this is it.
I won't study LC, because I'm waaaaaayyyy too busy, learning Swift, UIKit, AppKit, WatchKit, SwiftUI, DocC, MapKit, SiriKit, device SDKs, networking, USB, etc.
I literally work every single day (like seven days a week), and learn something new every single day, yet I am barely keeping up. I would be nuts to sacrifice any of this time, studying schoolboy questions that have little to no relevance in the software that I write.
These technologies result in actual applications that you can sell and market.
Just another way to look at it.
When a job doesn't focus on what LC asserts, and I think we'd agree about how huge that segment is, then naturally it should be a small or non-existent consideration.
Some stuff should definitely have a steady hand on the tiller, other jobs, not so much.
But the thought of licensing software engineers is daunting. The industry is so incredibly varied.
For example, almost none of the programming I do, involves higher math. I've pretty much forgotten all my calculus, while other jobs are almost nothing but math.
I could be writing crucial, lifesaving device control stuff, and the math person could be working on a game physics engine.
But overall I agree with you. While I don't have the results to back it up, I do believe that ultimately Leetcode isn't that useful outside of recruiting people straight out of college. Otherwise, I think there are more domain specific methods to assess candidate fitness to a role.
Also, my giving my unsolicited opinion, I do agree with one of the Reddit posters saying that you are currently on your way to burnout. While I can sympathize with you being super interested in learning programming all the time (because it is very interesting!) be sure to not ignore your other needs, and also to take a mandatory break at least one day a week. Speaking from experience, if you don't do this you will burn out and you will have to pick up the pieces.
But I also take breaks (and naps) whenever I want. No one wants to hire old folks, so I don’t work for anyone. I do this, because I want to.
What’s that saying? “It’s not work, if you love what you do?”
I’ll tell you when I was actually in danger of burning out; it was when I was a manager (which I did for 25 years). I spent a hell of a lot of time, sitting on my ass. I coded on the side, so I wouldn’t burn out. This is like Disneyland, compared to that horrible grind.
Wow. I keep forgetting what a sewer Reddit is. I guess that’s because I don’t spend much time, there.
It can be months (at a high salary) before you really know whether a hire is likely to work out. I think it makes sense to invest more effort in screening applicants in this case.
The trouble with programmers is that you can never tell what a programmer is doing until it's too late.
The trouble with programmers is that you can never tell what a program is doing until it's too late.
The trouble with programs is that you can never tell what a programmer is doing until it's too late.
The trouble with programs is that you can never tell what a program is doing until it's too late.
Which is hilarious in an industry that is pretty binary ("you can build it") || ("you can't build it"). Doubly so when the majority of dev jobs are in web which is easily explored in the candidate's language of choice with basic CRUD / RESTful concepts.
It may not be the majority, but if the research is all done in-house by various firms, there's no way for anyone to know that.
That started the contractor looking elsewhere...
> It can be months (at a high salary) before you really know whether a hire is likely to work out.
It's only that way if you make it take that long. You should know if you have a good programmer 2-3 weeks after the hire. Here a couple things that make making great hires hard:
* Making it difficult to learn and understand your system.
* Having slow and expensive employee onboarding. I've seen companies spend $3-4K (not including the actual laptop) just getting a laptop to a new employee after IT gets done with it. If it's super-expensive to make a hire, the incentive will be to keep people that aren't getting the job done.
* Not looking at work output for extended periods. In short give new people tickets that can be done in a few days at most so you are able to look at work output in six days instead of measuring at six months.
> I think it makes sense to invest more effort in screening applicants in this case
There's only so much you can really screen before error in your hiring process exceeds 50%. Every step you add to a screening process has an error rate, and some are very subjective and error prone. The more screening you do, the slower you go, and honestly, the worst candidates you have to pick from. Why? Because a good programmer will be on the job market for 1-14 days (I'm not saying you are bad if it takes you longer to get hired, it's just what we're seeing in our recruiting software right now).
Does your software systems scale to Millions?
What about counterfactuals?
Without that data, your 3-decade hiring process means nothing.
I'm sure someone working in IBM, TCS, AT&T, Booz can all claim that they have been hiring people for 3-decades and give an opinion
>I've hired hundreds of developers over three decades, and this is completely wrong
in order to argue from a position of authoritative experience, these questions are entirely fair game.
If folks are too green for that then they can be put thru an internship first. If an obscure language, have them do checkins on a tutorial.
I have a human conversation, make sure the expectations are clear and ask them if they think they can do it. Then I look at some of their work to verify and that's literally all.
No whiteboard, no takehome, no brainteaser, nothing like that.
Go google "how gates hires" or "how jobs hired" ... it's more or less the same. None of this I watch you implement a sliding window in a shared coding environment bullshit.
Let me put it this way. Say your candidates were all award winning scholars with phds and prestigious organizations to their name, then how would you go about it?
With respect but also, you'd still check to make sure it's the right fit, obviously.
Now here's the crazy go-nuts bananas idea - treat everyone with that level of respect. Totally wacky, I know. But hear me out - you can apparently build better teams with trust allocated to trustworthy people as your building block. That starts the day you interview and extends forever, well beyond your time working together.
Yes, three times.
> Does your software systems scale to Millions?
Is 8m active users per day enough?
> What about counterfactuals?
A broken clock is correct twice a day. Not sure what you are wanting here.
> I'm sure someone working in IBM, TCS, AT&T, Booz can all claim that they have been hiring people for 3-decades and give an opinion
I don't work for them.
the meta-halting problem
This make sense for highly productive labor, that foreman hiring people for just showing up generally got a positive expected return for this. In fact, this is still how a lot of (sometimes illegal) day labors go about getting work: truck comes by, picks up people ready for work, work get done and everyone makes money.
> Why again does boutique startup need to interview 500 overqualified people?
Because these startups lose money as a matter of principle. The people working there aren't actually performing productive labor. All of that hiring is about creating a large illusion in the market place.
Most of my labor has gone to waste. More projects than not never ultimately shipped, but even the most valuable projects I did, still made money for companies that ultimately lose more money than they take in. Many of my best projects are for SaaS companies that don't exist any more.
The guy picking up a bunch of people in the back of his truck is about to go build something real and is going to get paid in cash, and the more people he can get in the back of the truck the more jobs he can get done in that day, which means more cash for everyone (and if you're on the paying end, it means that project you wanted done is done faster).
> It's just business for crying out loud.
I don't think this has been true in tech for over a decade. I had a COO once excitedly proclaim that if the company made more money than it cost to run, we would have unlimited runway. The COO seriously thought he had stumbled upon some brilliant realization about a company making more than it costs to run.
The guy with the truck knows far more about business than most execs at tech companies today.
Same here and I've been in the biz for ~35 years. An architect can drive around a city and point to buildings he designed. It's a bit disillusioning to think that the vast majority of the work I've done has just sort of disappeared because either a startup didn't make it or got swallowed up into a larger organization that had other plans.
> The guy with the truck knows far more about business than most execs at tech companies today.
Yep. The guy with the truck can't lose much money for very long. A lot of tech execs have gone years without needing to worry about that because there was so much easy money around.
I don't think that the situation is really that much different for building architects.
In cities that are experiencing rapid densification, it's not unusual to see numerous buildings from the 1950s, if not much later, being demolished to make way for newer and larger structures.
Even when structures aren't totally demolished, it's not unusual for them to be so extensively modified that the original building is virtually unrecognizable, or even completely obscured by the work of other architects.
It's also quite common for building projects to be canceled before construction starts, but after designs have been prepared, and other architectural work performed.
Many projects that do eventually get built often go through numerous revisions, with the final product being almost nothing like the earlier designs.
I was under the impression that architects also did a lot of spec work, or designs for RFPs that don't ever get built. Or maybe only get built as a model.
I'm not disagreeing with your premise -- there is a lot of programming work that is hidden, lost, or wasted. However, it's not a trait that's exclusively a programming thing.
Washes most of the nonsense away.
B. Are you saying top banks are bad at banking?
literal fraud by banks and security rating agencies was directly responsible for the crisis. They defrauded their customers and each other.
Thats why they were called subprime loans.
What do you mean by "fully automated" ?
Literally every aspect of that job is fully automated.
Where I work today 20+ years later, we have 1/3 of the people doing like 100x the amount of work by several measures. Little teams of developers can just crank out work.
Yes, the productivity of modern day "stored-in-the-DB/presented-in-the-browser" project teams can be astounding. But that's only one type of software.
You're not hiring construction workers, you're hiring architects. It often takes more than 3 months to get used to a new codebase and understand how and why things are done the way they are.
A guy goes up to the shipyard gates and asks to see the foreman. When the foreman comes along he asks "Hey, any chance of a job in your yard?"
"Yes, of course", says the foreman, "if you're prepared to start at the bottom and work your way up. Are you any good at making tea?"
"Yes", says the man, "I can make the tea!"
"Great!", says the foreman, "do you know how to drive a forklift?"
The man squints at him quizzically, "How big is your f***** teapot, then?"
This used to happen in the 80s. I went to interview at a startup company in Mountain View in 1987. There was some chit-chat. Then the interviewer asked me to wire-wrap a circuit (diagram was provided) and power it on - he went away for about 1/2 an hour while I did that. He came back and complemented me on my neatness. He took me over across the room to talk to the VP of engineering who asked me when I would like to start. Those were the days.
I wonder what’s so hard with my interview. 5 years ago, even interns could do it, one of them could even tell the difference between UTF-8 and UTF-16.
Anyway, I guess it depends what compute layer you're interviewing for, but it doesn't necessarily sound like your interview process is broken, exactly. Like, it could be testing for the right thing, but in the absence of that thing, maybe you just need to find another thing that is substitutable.
It should be our real-life test, but it’s too long. It’s our most complicated algo, and honestly it’s very simple in the end. But given all the variables scattered around in a string.contains() (I don’t even look whether the result is correct, I look whether it’s structured for intelligibility and how they debug the off-by-1 errors), I can’t suppose a more complex algo will be done cleanly.
Maybe I’m mot giving them their chance - It might have taken time for me to output clean algorithms.
Umm...there's some administrative and legal overhead related to hiring, firing or otherwise replacing an employee you seem to be overlooking.
Things would function just fine, if not a lot better, without such unnecessary burdens being forced on employers and employees.
Long story short: I think we can lengthen the interview period to accommodate those legal time sinks without killing off the (now a bit of a novelty) meatspace first impression. Unless you're talking about blind selection, where the candidate's likeness (name, etc.) is redacted for DEI. In that case, I can see how witnessing the candidate's skin, gender, etc. could be problematic. TFA even explicitly included the types of things we try to leave unspoken these days: excellent health, 5'4"?!
Oh yes, ‘at-will’ states are absolute front-runners in employee happiness.
We were a small-ish startup and he had done his homework, showed interest, and could write code to our standards. He stayed for a year or two and then moved on.
Offbrand for this site but I’ve seen women audition and work and get paid the same day, this year
Is what it is
They sign all forms and its W-2 employment some places as well
I agree we should reduce friction to that level for more kinds of work, some people are working on that
the main point is how it is in direct contract to how other sectors will interview for weeks and months, before any resolution at all, then require negotiating an offer, just to get to a two-week notice at a minimum and then require another 2 weeks to a month to get paid, with deposits taking several more business days (up to 5 actual days) to be available
paid instantly when you realized you might need it, versus paid 4 months from now hoping you planned and forecasted correctly
I was referring to women dominated crazy corners and I don't have lived experience with man's equivalent job pursuit to say so I didn't speak about them
That's hard to do when there are so many strings attached to employing someone. It's a double edged sword which makes the decision to hire someone a lot bigger." Yeah, I have stuff I need help with right now" is not enough.
Whereas some tenants rights seems to have a pretty large positive impact - ie all the positive effects of secure housing.
Of course ymmv in your local housing market.
In that case, one benefit of public housing is that it slims the pool of “sob story”-havers that you can evict for sport!
But the contractor usually needs to be "employed by" some agency company, that guarantees his/her suitability, and that handles the (not insignificant) paperwork / legalities, and that takes a handsome cut.
In warehouse and construction work, if someone shows up at 7:30 AM on a Monday morning, odds are quite good that the foreman will have something for them to do. Maybe not that day, but maybe tomorrow, or maybe someone on the list above them won't show up that week and they'll get called. I made rent doing that in my early 20s and they even let me leave early sometimes to work on my internet business because I didn't have a family to support and maybe someone else had a bill they needed to pay and wanted my shift.
Why again does boutique startup need to interview 500 overqualified people? Hire someone right away and let them quit if they want to and hire someone else. It's just business for crying out loud.