3 ms·
I once did a take-home project for a full stack role that proclaimed any language/framework could be used to build a browser-based application that satisfied a
by tmpz22 2y ago
I once did a take-home project for a full stack role that proclaimed any language/framework could be used to build a browser-based application that satisfied a particular task. I opted to use golang and its standard library to produce an application with no external dependencies and no javascript. In the rejection email they stated the use of outdated development methods was a point of disqualification. I'm sure other reasons for disqualification were present, I wasn't a great candidate in retrospect, but I'll never forget the naivety and hubris of their framing.
They were of course a NextJS shop.
Ultimately disregard role titles. It's a people problem that you have to pull teeth to find out what they really want, and what they really want they often won't say out loud. That's fine, it's their money (and usually a lot of it!) and they should be able to dictate the services that they want.
Really sucks for people new to the industry trying to learn the song and dance.
- kube-system 2y agoSounds like you dodged a bullet in terms of culture mismatch. I think a good number of these mismatches could be mitigated by having some in-depth conversations about the job, team, interactions with other teams, and problem scope, before getting into any technical interviewing.