4 ms·
Ahh, so they're not actually looking for seniors then? Sounds like they want people who are "passionate" enough to spend months prepping for an interview so the
by openfinch 6y ago
Ahh, so they're not actually looking for seniors then? Sounds like they want people who are "passionate" enough to spend months prepping for an interview so they can milk them dry without the risk of pesky things like "free time" and "family" getting in the way.
Tongue in cheek analysis aside:
- A phone interview to weed out timewasters.
- A RELEVANT technical take-home task that could be done feasibly in a few hours.
- A long, informal, in-person chat to determine "culture fit" and personality.
- Actually checking references.
That's all you need, anything more is just self-importance - or worse - time wasting.
- bra-ket 6y agotechnical take-home task is mostly time wasted for the candidate, working for hours just to be ghosted again and again, you will be selecting for people who have nothing better to do. I'd skip that (and leetcode) entirely and during in-person chat put emphasis on discussing prior projects in detail. As for "system design" ask a question on your current architecture, how would they approach solving a particular problem you actually have/solved, and see what questions they ask. That's how good people who built the tech industry used to get hired in the old days (i.e. when they were not friends of friends)
- blamestross 6y ago"Prior projects in detail" is a great idea until most of your desired candidates can't do that because of NDAs. Most of my NDAs do not permit me to discuss anything except the broadest strokes of my past projects.
- dilyevsky 6y agoI interviewed a bunch of fb E4s at previous gig and yeah imo not a lot of them would have senior title if you rewind industry say 10 years back. Once you deviate from their canned prep it all falls apart. They’re almost all very good with basic algo stuff tho