News for hackers. Stuff that matters.
Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by cletus on Monday May 11, 2020 @12:29AM (#23138917)
So I'd say anyone looking for engineering work should aim to have at least one (and just one is fine) of the following:

1. A good (and well-known) school. MIT, Stanford, CMU, UW, Waterloo, you get the picture.

2. A good (and well-known) employer. FAANGs in particular. Ideally as an FTE but internships are good signals here too.

3. To be known for something you've done. Well-used open source project, well-known blog, that sort of thing.

(1) and (2) fall into the category of "social proof" [1] and whether you like it or not, social proof can take you pretty far in life. Like in my case, it didn't take that long from working at Google to getting cold-called almost constantly (and I guarantee you there's nothing special about my situation).

My own job seeking experience (pre-Google) tends to be pretty similar to the numbers in this post (applications to interviews to offers). For those of you sending out hundreds of applications let me offer you some advice because I see a lot of people making easy-to-fix mistakes.

Hiring is a popular topic on HN and you see the same comments. There are always people who call a hiring pipeline a failure because a good candidate got rejected. This is the wrong way to approach this. The process is asymmetric.

A candidate is trying to get through each stage of the pipeline and get hired by somebody. Ideally they want multiple offers to boost the offer they end up accepting. "Success" is accepting an offer.

Below a certain size, a company wants to fill a role. It'll have N applications and the pipeline is designed to have filters along the way to winnow down that number to fill the role. "Success" is filling that role with someone sufficiently good. They don't have to be the best. Technical skills matter but usually only to a point. You have to bear in mind that you are a cog that needs to fit into an existing machine. Each step of the process gets increasingly time-consuming so the more you can weed out at the earlier stages while still filling the role, the better.

Large companies are similar except you don't tend to be interviewing for a particular role. There is a constant hiring pipeline. Recruiting may well be a separate org. You can use this to your advantage.

So, let's make up some numbers for our waterfall:

- Recruiting receives 100 applications

- The 20 best get sent to a hiring manager

- They may well eliminate half for various reasons passing on 10 to one of their engineers

- That engineer may well filter out half too meaning 5 will get called

- 3 of those will get interviews

- 1 will get an offer, another will be the backup

Like I said, completely made up but still instructive. And I'd say it wouldn't be too far off the mark for a mid-sized company.

The first thing is you need to get through a company's recruiting/HR filter. Well they look at the requisition ("req") they have and try and see if the application seems to fit the criteria and I really do mean seems to. This is what I call the buzzword filter. Anecdote: I once had a conversation with a recruiter who said--and I'm not making this up--"I can see you have 6 years of Java experience but do you have any J2SE experience?"

Some of it isn't buzzword related. Like if the req calls for leading a team, they'll look to see if you've led a team in the past. Depending on the company, the seniority of the position and so forth, factors like your school and previous jobs may come into play. Length of employment is a factor here.

So how do we approach this to pass this filter? Well we need to cater our resume to the job posting and see how it fills the criteria. We need to have sufficient buzzwords but not too many and not any we can't back up. This may hurt us later. Then again, it's completely valid to try and pass through early stages and deal with that problem later.

One point to consider is that the half the applications the hiring manager may never see. To be fair, a lot of job applications are garbage. My numbers are actually pretty generous. I've had people tell me that 90% of applications can be immediately rejected.

The hiring manager will have their own criteria and biases. They're trying to judge if you're someone who will fit on the team. Here lots of short jobs can hurt. There are cultural factors too eg in the UK I found having contracting on your CV would really hurt you for full-time roles (this was years ago; I can't speak for the current conditions).

Basically the hiring manager is looking for red flags.

The engineer will typically be looking for technical suitability. It's from this point onwards that various (ideally cheap) negative filters are used to try and reduce the numbers further.

And this is what a whiteboard coding test should be: a relatively easy problem just to see if you're not an idiot. FizzBuzz is easy for a reason. Engineers fall into the trap of thinking the problem needs to be hard. This actually reduces the effectiveness of the signal as you've turned a useful negative filter into a crap shoot of whether or not you know the "trick". For example, I had whiteboard coding problem once to reverse bits. Turns out (I found out later) this can be done in O(log n). I had never had need for such a trick so didn't know it. So what did that test accomplish exactly? Bit-fiddling is applicable to certain classes of programming, just not any I had and (more importantly) not the one I was interviewing for.

An early stage startup may simply be the hiring manager responding to emailed applications and they'll hire the first suitably qualified candidate they find because they really don't want to be doing this. A larger company may filter everyone through and then pick the "best" to extend an offer to.

So when you apply for a position, I would encourage you to think about what process that company has for hiring and treating it as a waterfall that you need to get through. Find out what you can about their hiring process. If you can't find out, make up something that seems reasonable given the type of company they are and their size.

The most important step for your application is to make it through the first 1-2 filters as those tend to be pretty dumb. Your CV needs to stand out from a hundred others in some way. A known school or employer is a good one. Absent that, allowing them to see some evidence that you can communicate in written form and/or actually code is a big plus.

[1]: https://en.wikipedia.org/wiki/Social_proof

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by bradlys on Monday May 11, 2020 @12:40AM (#23138973)
Education isn’t enough on its own for social proof. I know because I thought it would be. I couldn’t get a job to save my life after college even with UW on my resume.

Also, education is wildly localized. Turns out SV doesn’t care about anyone except those from UCB and Stanford (big emphasis on Stanford). Same with UW. Outside of Seattle, no one even knows about it. (I should know - I went there)

Maybe prestigious colleges are more well regarded outside of the Bay Area - at least here, everyone and their mother went to an Ivy League or similar.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by strgcmc on Monday May 11, 2020 @12:14PM (#23143702)
Yeah, SV is really just the bubbliest-of-bubbles. It attracts so much talent, and is funneled so aggressively in so localized a market, that your anecdotal observation of "everyone and their mother went to an Ivy League or similar" is probably more true than most people might expect. Such is life, and it ain't fair.

UW is a great school. UW is what most people should realistically aspire to (as that caliber of school). It's upper-middle-class; it will most likely give you a great education and a great life.

UW is not Stanford/MIT/Harvard/etc. though. Those are not upper-middle-class schools; those are upper-upper-class schools. And it's not really the quality of education content either, at least if we're talking about average outcomes (but at the margins, ~2+ standard deviations away from the mean, it's no contest).

If anything, this should signal that SV has gone too far and the labor market is acting irrationally by competing so much for educational branding. However, just like the old adage says, the market can remain irrational longer than you can remain solvent.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by nscalf on Monday May 11, 2020 @01:22AM (#23139131)
I want to add another option:

4) Have a wide range of items on your resume.

I have found that having experience as an engineer in Fortune 500 companies, startups, working at the only dev, level 3 support, building dev ops, joining a big team, owning back end services, reworking a database, etc. has given me credibility for most positions. Everyone knows you won’t immediately fit in perfectly to any role, but if you have demonstrated an aptitude to learn and adapt, you’re likely good enough for their role.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by throwawayfaang on Monday May 11, 2020 @05:16AM (#23140285)
I think you should not do that. Whenever I see a CV from a candidate in his/her twenties listing like 30 different technologies that each take years to master (unless you're really a programming prodigy but even then it's unlikely) I immediately think the candidate is doing "keyword spamming", and that's a strong negative signal. As a candidate such a strategy can quickly backfire as well, because your interviewer might pick one of the technologies you boldly listed on your CV and ask you really detailed questions about it, which you might not be able to answer because you might only have used it in a short side project and don't know it in depth. That will almost always ruin your chances of getting an offer. I recommend to only list languages and technologies you really know well. You can still list others that you dabbled with but make it obvious that you e.g. only explored these in your spare time or are curious to learn more about them, this will be a positive signal and won't come over as keyword spamming.

Same thing if a candidate has too many short tenures on his/her CV. If I get a candidate that has five or more short (<12 months) stints at different companies I will not invite him/her (or at least ask for clarification in the phone screen) because it hints at a general problem. There are surprisingly many candidates that call themselves programmers but really can't program at all (or only at a very basic level), still they often manage to land positions as programmers, which they eventually get fired from (or leave) when it becomes clear they can't do the job (and some companies take a long time to come to this conclusion). A long string of short tenures is one indication of such a person, so be wary of putting too many short tenure work experiences on your resume, except if you're a freelancer of course.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by cantankerously on Monday May 11, 2020 @09:43AM (#23142033)
"Simply go to MIT and work at Google"

I say this in jest, but that isn't the most replicable path. For someone who didn't go to MIT and is mid-career, should one just throw in the towel and give up on the industry?

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by ativzzz on Monday May 11, 2020 @10:42AM (#23142634)
The OP should have prefaced his post with "If you want to make top 1-5% of engineering salaries". The vast majority of engineering jobs are done at boring non-tech companies by average programmers who have average educations and experiences. And of course, average salaries.

Generally programmers working at those companies don't know about or don't care about HN.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by cantankerously on Monday May 11, 2020 @11:41AM (#23143296)
I generally agree and I think I understand OP's intent. However, if true that paints a fairly bleak picture. I'd like to find challenging work and make upper echelon salary, why not? Didn't go to MIT or similar and no FAANG experience. So my only hope is to create an open source project or blog and pray it explodes in popularity?
Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by ativzzz on Monday May 11, 2020 @12:57PM (#23144278)
> I'd like to find challenging work and make upper echelon salary

This has always been the case for humanity, that typically people who do challenging, high salary work come from wealthier families with access to better resources, including better social signaling resources to enable them to stand out from the pack.

It's just part of the game; if you want to play at the top without being born into it, you have a long way to climb, and you are competing against everyone else in your position. You have to either meet the filtering criteria, or find a way to stand out from the crowd.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by cantankerously on Monday May 11, 2020 @03:41PM (#23146107)
I guess my error in thought is that tech would be more of a meritocracy than other disciplines. I'm totally aware I have shortcomings. But you're right, some are better at playing the game than others for various reasons. I don't mean to be argumentative, just frustrated. Just like at the casino, if the deck is indeed stacked against me the best move is to not play.
Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by int3 on Monday May 11, 2020 @05:23PM (#23147258)
It's still way more of a meritocracy than many other disciplines. In what other field can you get an upper-echelon salary via non-credentialed routes like open-source projects and blogs?

Btw, you don't need to create an OSS project from scratch. You could also get visibility by making important contributions to an existing one.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by jimbokun on Monday May 11, 2020 @04:56PM (#23146983)
> So my only hope is to create an open source project or blog and pray it explodes in popularity?

Pretty much, yes.

Re:My Mid-Career Job-Hunt: A Data Point for Job-Seeking Devs by charklet on Monday May 11, 2020 @07:16PM (#23148461)
A fourth: have a specialization either in a technology, part of the stack, or in an industry. That allows you to stand out for roles that really need someone with experience in that area, right now.

That said, I think your 3 recommendations lean more to a "how to play the interview game on easy mode" than every developer should to do this. I feel like I may be exaggerating your intent a little, but it did read a little like "Go to MIT, work at Google, write a famous blog" :)