Live data from Hacker News

2500 Job apps, 46 interviews, 1 offer

teamblind.com

71–80 of 126 posts

Re: 2500 Job apps, 46 interviews, 1 offer

#71

I'm a 30+ year experience SWE. I had my own successful startup exit and after that I skipped FAANG to join the founding teams at other startups founded by Ex-FAANG big names. Unfortunately none of them panned out. I recently went through a series of interviews with a company that were dragged out over two months. Each went very well. My last interview was with a "Senior Engineer" who graduated in 2020 and had a littl…

Was it actual pair programming (where you actually build something tangible) or was it a leetcode style interview?

In a leetcode style interview, I could see being thrown out for debugging. In a true pair programming exercise, I wouldn’t think this would be super common but guess it depends a lot on the exercise. Pair programming is extremely variable with the tasks.

Re: 2500 Job apps, 46 interviews, 1 offer

#72

With respect to OP, I think the real issue is the 46 interviews and only 1 offer, not the job applications. To sit through 45 interviews without an offer points to a serious weakness in the interview department. Instead of all the applications, they should have focused more of their time prepping for the interview. The ability to interview is the most important skill when it comes to getting a job, you can be the gre…

It's clear that you haven't had to get an interview from a non-connection in the last year. It's a literal fucking nightmare unless you have connections that can literally hand you a job. I have 8 years of experience.

TL;DR: Connections don't mean shit. Companies require multi-hour takehomes and then ghost you. Every reply is automated unless you are moving forward. Recruiters take a week to reply to even the most basic updates.

For reference, I've job hunted twice in the last 2 years. The startup I joined in Feb of 2022 folded in Feb of 2023. My style is to treat it like a full time job, usually completely filling my schedule with interviews.

2022 stats: In 1 month I interviewed with 31 companies, received 6 offers in under 5 weeks and had a job secured making ~30% more than my previous role. Of the 25 companies that I stopped interviewing with, 13 were me cutting off the process to save time and 12 were rejections. So ~50% success rate depending on how well you count the 13 that I cut off.

2023 stats: First month I interviewed with 14 companies, was ghosted by 6 of them. GHOSTED. 3 of these were from direct referrals from friends and previous coworkers! Not even my connections could get information on my process! I interviewed just as strongly as my previous year and they vanish, not even with a rejection. Of the remaining 8, 4 were not actually software jobs and 4 were rejections that refused to elaborate at all.

Second month I interviewed with 34 companies. 12 ghosted me, 4 of which required a multi-hour take home assignment. With a mortgage and kids, I was doing it all.

Of the 22, 11 didn't work out for non-performance reasons (found candidate before I was through the process, recruiter misunderstood the role, company moved so slow that I couldn't complete the process). Of these 11, 4 were from connections! They could not get their internal recruiters to reply to me in less than 2 weeks.

Of the 11, I was rejected by 6. Again, with no feedback or even a response when I asked for it.

Of the remaining 5, I got an offer and ended the madness before waiting to finish my remaining 4 interviews.

Re: 2500 Job apps, 46 interviews, 1 offer

#73
post #71

I'm a 30+ year experience SWE. I had my own successful startup exit and after that I skipped FAANG to join the founding teams at other startups founded by Ex-FAANG big names. Unfortunately none of them panned out. I recently went through a series of interviews with a company that were dragged out over two months. Each went very well. My last interview was with a "Senior Engineer" who graduated in 2020 and had a littl…

Was it actual pair programming (where you actually build something tangible) or was it a leetcode style interview? In a leetcode style interview, I could see being thrown out for debugging. In a true pair programming exercise, I wouldn’t think this would be super common but guess it depends a lot on the exercise. Pair programming is extremely variable with the tasks.

No it was implementing a feature. No palindromes or nonsense like that.

Re: 2500 Job apps, 46 interviews, 1 offer

#74

Earlier quoted context omitted.

Out of (morbid) curiosity - what was his objection to using a debugger?

Isn't it obvious? Using a debugger implies that you expect the code you write to have bugs. Not a mindset I'd like my coworkers to have.

Is this sarcasm or epic hubris? No-one writes bug-free code, and thinking otherwise sounds like an enormous red flag.

Re: 2500 Job apps, 46 interviews, 1 offer

#75

Earlier quoted context omitted.

Out of (morbid) curiosity - what was his objection to using a debugger?

Isn't it obvious? Using a debugger implies that you expect the code you write to have bugs. Not a mindset I'd like my coworkers to have.

Not sure if you're trolling or just missed the "/s" tag.

A much worse mindset is to be arrogant enough to assume the code has no bugs.

As a matter of principle every code has bugs. Some bugs are found, some not.

Re: 2500 Job apps, 46 interviews, 1 offer

#76

Earlier quoted context omitted.

Out of (morbid) curiosity - what was his objection to using a debugger?

Isn't it obvious? Using a debugger implies that you expect the code you write to have bugs. Not a mindset I'd like my coworkers to have.

It’s actually worse than that: using a debugger shows that you’ve written so much buggy code that you somehow learned that debuggers exist.

Steer well clear of these people!

Re: 2500 Job apps, 46 interviews, 1 offer

#77

With respect to OP, I think the real issue is the 46 interviews and only 1 offer, not the job applications. To sit through 45 interviews without an offer points to a serious weakness in the interview department. Instead of all the applications, they should have focused more of their time prepping for the interview. The ability to interview is the most important skill when it comes to getting a job, you can be the gre…

It's clear that you haven't had to get an interview from a non-connection in the last year. It's a literal fucking nightmare unless you have connections that can literally hand you a job. I have 8 years of experience. TL;DR: Connections don't mean shit. Companies require multi-hour takehomes and then ghost you. Every reply is automated unless you are moving forward. Recruiters take a week to reply to even the most ba…

Respectfully I have never gotten an interview let alone a job via a connection in my life. I maintain zero contact with previous coworkers.

Also I don't understand why you said I must have connections and then a sentence later say connections mean nothing.

You are right though, it has been 16 months since I interviewed so things may be different.

Re: 2500 Job apps, 46 interviews, 1 offer

#78

Earlier quoted context omitted.

Out of (morbid) curiosity - what was his objection to using a debugger?

Just that I used it at all. There's a contingent of engineers who feel using a debugger is a waste of time and or a sign of weakness. They're the ones who like to stare at code and "run it in their heads" and dump crazy amounts of "got here" into the logs. Evidently this guy is one of them.

There's two reasons I think. (I have ~25 years experience)

1. In your code should know what the edge cases, loop condition issues, etc.

I think this is fair. If you don't know the edge case failures when you write your code, you could end up with something like the Microsoft Xune that shutdown for an entire day over a leap year failure.

https://www.seattletimes.com/business/microsoft/original-mic...

Keep in mind that code review will probably not catch all bugs, it's up to the original coder to write it. This is particularly true if you're the best person on your team, say. Or you're working at a startup where no one can really review your code other than you.

On the other hand well coded unit tests should help you here.

2. It's toxic brogrammer culture there -- where leetcode scores are all that matter. In which case it's probably best you were passed over.

Re: 2500 Job apps, 46 interviews, 1 offer

#79
post #16

At those numbers, something is wrong with their process. Poor resume formatting/content, bad social skills during interview process. That's barely 2% call-back rate after an application.

Agreed. I get the "You aren't done till you give up" and "I have been knocked down 55 times, I got up 56 times" thing, but it can blind you to a tactics issue.

But there has to be at least two things wrong here, since he had a very low success rate on applications and on interviews.

Re: 2500 Job apps, 46 interviews, 1 offer

#80
We’re getting a lot of comments from people who are not familiar with different markets. This is HN - where the focus is on Silicon Valley and associated companies. User is posting from having just left Meta. $475k as a PM with 16 YOE isn’t even remotely high when you consider probably living in one of three major cities in the US (Seattle, SF, NYC) and is working for a company known to pay such rates. This is a common compensation - not outlandish at all.

The other aspect is the interviewing. People here are unfamiliar with other markets. If you’re interviewing with FAANG and crew - you probably send out hundreds of resumes. If you’re picking really desperate startups - you might get 25% reply rate if you’re in a good economy. In other scenarios, getting a 2-5% reply rate is common. Thus why people have to apply to so many places and so liberally. You’re just sending the same resume as you do everywhere else.

The other thing is the interview process for a lot of these companies is harder and more selective. You’re competing with people from all over the world and many whom are on visas and want to stay in the USA. Your small shop in a city of 250k that pays one fifth what this person is used to isn’t going to be competing for the same talent.

My point is - wow, yes, people get paid differently in different markets. They also have different interview processes because when you get paid a lot, it tends to bring a much stricter interviewing environment because there are often way more qualified people than they can hire. (Whether you get into FAANG is a mix of luck and preparation - most everyone is qualified enough to do the jobs even if they don’t get hired but the interview process is extremely noisy and highly selective by nature)

I’ve gone through these gauntlets. I had to interview with 100 companies to get one offer. (Including 15 onsites) In other stages of my life, I interviewed with about 60 and got 6 offers. It’s hugely variable and often has little to do with you and more to do with the hiring environment. I was overqualified for most every job I’ve ever had or been interviewed for. As every job I’ve ever had has been a joke in terms of the challenge, the skills needed, or the intellect required. I’m including jobs I’ve had paying $15/hr all the way to $1m/yr. Don’t misinterpret the interview process as really being a strong signal to your ability to do the job. Especially with all the leetcode stuff.

Post reply on HN