31–40 of 322 posts
The norm, in the last few years, has generally been in most cases a new hire makes more than a long tenured individual in the team.
Do that.
Your CV or resume is sales collateral. Focus on warm and hot leads over cold calling. Vet your leads with conversation, make sure you really can solve their problems, then give them your sales material. Preferably optimized for the lead in question.
If possible make the sale before interviews even begin. That way they’re just a rubber stamp and smoke test for red flags.
>For a typical job there were four or five interviews: an initial interview with a recruiter, an interview with a hiring manager, one or two technical interviews (either live coding, or going through a take-home assignment). There could also be an interview with a product manager, and/or one with a CTO or founder. All in all, quite a time commitment. This is not news at this point, but it is pretty crazy.
That's not crazy. Some of these are probably what 30 minutes? Tech interviews 60 mins? So what, five hours? Remember when on-site interviews meant an hour total commute plus say six hours of total interview plus lunch event. Some high demand companies put candidates through more than one round of that. Not to mention if you were flying from out of town... I remember a friend who interviewed with Google and got stuck…
Add in the 6-hour take home (which companies delusionally believe will take 2 hours, despite being often inadequately scoped or otherwise poorly presented; while quite often expecting a nitpick-proof solution); and all the random delays, and other hoops - and the none-too-occasional ghosting (even at the very end of the process) -
Yup, it adds up.
I don't question that is takes hard work, even for more senior devs like the author, but 30 apps leading to 3 offers is a dream. Most early-career people are probably at >100 app with maybe a few interviews and hopefully one offer.
Earlier quoted context omitted.
That's not crazy. Some of these are probably what 30 minutes? Tech interviews 60 mins? So what, five hours? Remember when on-site interviews meant an hour total commute plus say six hours of total interview plus lunch event. Some high demand companies put candidates through more than one round of that. Not to mention if you were flying from out of town... I remember a friend who interviewed with Google and got stuck…
> I remember a friend who interviewed with Google and got stuck in SF for three weeks due to snow storms on the east coast This is literally unbelievable. I cannot remember a time when the east coast was inaccessible for three weeks…
https://en.m.wikipedia.org/wiki/February_5%E2%80%936,_2010_N...
https://en.m.wikipedia.org/wiki/February_25%E2%80%9327,_2010...
https://en.m.wikipedia.org/wiki/February_25%E2%80%9327,_2010...
Two back to back storms, there was about 12 hour window where you could get in or out. This poor guy was supposed to fly back during the first, got pushed to a flight during the second, and then the pile-on of rebookings pushed him further. I don't remember if he got trapped due to the third storm too.
It wasn't completely cut off. During the first storm, I got head notice of the next one and rebooked my flight out of the east coast to be one day earlier, and threaded the needle by politely asking customer service. I was in and out of the east coast for a week.
Anyways, Some cities on the east coast are less prepared than others for this sort of thing.
Bit of a rant but I also have been job hunting after a layoff and their experience sounds like a dream. I have only gotten email rejections thus far and only 1 phone screen. It feels like most of my rejections are just automatic emails. Some of them come same day. The most demoralizing thing happens when you get rejected for a job and then see a new listing for that same job go up just moments later. You were rejecte…
Earlier quoted context omitted.
I remember when on-site interviews were an hour and that was it. All this stuff companies do now is insane. If a person isn't performant, you'll know within 30 days, but you'll never know by interviewing them. I haven't had to cold interview in 20+ years. I hope I never have to based on how it works now. I get all my jobs from previous colleagues. Companies are closing the door to a lot of great talent based on this…
I interviewed at Google nearly 15 years ago and it was already phone screen + a marathon of on-site interviews. Maybe 4 in a row.
what's the database timeout answer? i would say something along the lines of 5 seconds max.
I have no idea what the correct answer to an interview question that asks this is, though. Like, I never connect to my database inside the request flow, I have a connection pool and wait for a connection to become free in the pool. So "connection time" is really a function of how utilized the pool is, and has only a passing resemblance to the health of the database. Maybe 10 connections are running "begin; lock table foo; select * from foo where expensive_condition". All 10 connections in the pool are blocked on a lock, and that doesn't mean the database is unhealthy and you want to shed load. So do you want to show the 11th person "sorry, our site is down, come back later", or do you want to wait for the random expensive queries to complete? I'd wait. (I suppose I wouldn't take an exclusive lock on a table to serve a web page either, but who knows what the interviewer is doing.)