5 ms·
The "hire for" part is pretty straightforward - when you interview, you'll have candidates with zero idea what your company is building. They won't care either.
by avip 7y ago
The "hire for" part is pretty straightforward - when you interview, you'll have candidates with zero idea what your company is building. They won't care either.
Come Q time they'll ask about tech stack, code review, 4k screen, could they use their esoteric linux distro (yes).
OTOH you'll have candidates who already know your competitors, and know the tech stack because they registered for invite-only beta the day before the interview.
- therealdrag0 7y agoEh. I lean towards the former; in an interview I ask tech/process related questions and don't care about product (unless the interviewer mentions something that piques my interest). But when I start the job I give above-average energy to product-engineering. I'm looking for a tech fit, and I can apply my product-engineering energy anywhere.