[MarkMarine]

If you’re good at running your interview process you will have 3-4 at a time. That’s usually where I’m at, I’m interviewing with 12 and get it necked down to 3 or 4 getting to the offer point. I try to stretch out the fast movers and speed up the slow ones but just be honest with recruiters. You’re in the pipeline with other companies and you’re not ready to respond yet.

Edit: I saw other comments. I am both “old” and I have a mechanical engineering degree (not CS) and I do just fine interviewing with startups. I worked really hard at the practice of interviewing, this has more rewards and lower risk than basically any other skills you can learn so invest it.

[fdsf111]

> I worked really hard at the practice of interviewing

What did you do?

[shalmanese]

Not the OP but I tell everyone on the market that one of the highest ROI things you can do is just go through your own past career history with a fine toothed comb and simply remember all the different things you did and be able to tell the story of each concisely and informatively (if possible, recall actual numbers and quantifiable impacts etc.).

When in an interview, when you're asked a question about your past experiences, the larger the library you have to draw on, the more likely you are to find an example that's relevant and persuasive. Even questions of the form "How would you deal with [hypothetical scenario]", I encourage applicants, if possible, to answer it in the form of "Oh yeah, that's interesting, we had to deal with a very similar case at [one of my previous jobs], here was my approach towards it".

After each interview, do a "l'esprit de l'escalier" retro, write down all the questions asked, what your answer was at the time and what you would have ideally answered now given the fullness of time to think about it. If there's a significant delta, that's a sign to go back and prepare more until your "real time" performance approaches your retroactive performance.

[coredog64]

As terrible as the Amazon interview process is, they’re very up front in telling candidates exactly this: Here are the LPs, come up with stories for each one and make sure it’s STAR format.

[MarkMarine]

Everything. MIT has open sourced their coursework so I took all of it. I studied, I worked my way through TAOCP, cracking the coding interview (less helpful honestly) and tons of leetcode, I spent 4 years doing this and interviewing to get an idea of the system architecture problems and see how I was progressing.

It worked, after 4 years of studying I landed a SF job and 6 months later I was at Apple, year after that I was at Netflix. You get out of this life what you put into it, and in software it’s all out there for you to get. You don’t need a degree, you don’t have to pass the bar or boards, you just need to prove yourself and be willing to hustle