3 ms·
It was not an entry level. There was no designation to the role actually. But what does that question mean anyway? Say I've been working in java stack for 10 y
by zerogvt 7y ago
It was not an entry level. There was no designation to the role actually.
But what does that question mean anyway? Say I've been working in java stack for 10 years but for whatever reason I want to move to js/frontend. What else is there than entry level to begin with? Tech careers (at least honest ones) are rarely linear and there are hundreds of reasons for that.
- dlphn___xyz 7y agoyou're being subjected to these entry level assessments because you haven't proved that you can apply your software design skills across different paradigms - build a portfolio or maintain a github
- notacoward 7y agoNo, that's not why. Some companies just do this for every engineering hire, even those being hired for senior or specialized roles. I came in to my current job with two and a half decades of experience across multiple specialties, nearly a decade on a project they relied on and for which I was an upstream maintainer ... and I still got the whiteboard. Maybe there are some exceptions, but I have yet to meet one. Even characterizing it as an "entry level assessment" already misses the mark. It's more about avoiding bias (or the appearance of it) by trying to apply a uniform process and standard across the board. Some might say you shouldn't want to work at those companies if you don't like their hiring process, as though there's nothing to any company but the hiring process. It's like saying you shouldn't join the military if you don't like basic training. Nobody likes basic training. People join organizations despite those things, and I for one am not going to judge them or assume their reasons are silly just because I might decide differently.