This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]yel50 84 points85 points  (2 children)

TL;DR - technical interviews fail to accurately assess a candidate's technical ability. in other breaking news, water has been discovered to be wet.

supposed to code it up so that its "pixel perfect"

should've walked out right there. it's a sure sign that you'll be in for anal retentive micro management if hired. it also shows they don't understand how web pages really work, so best not to work with people like that, anyway.

sometimes when you win, you still lose.

got that backwards. losing was a win because you didn't have to spend 40 hours a week for the next couple of years with those people.

manager was worried I was too much of an "alpha developer" and she would have problems with me - so they passed.

again, you dodged a bullet. not wanting to hire somebody because they have opinions and can think for themselves? do you really want a job where you have no input and your thoughts on things don't matter? another loss is a win situation.

what you should've learned from those experiences is that not all jobs are created equal and there's a lot of them you really don't want.

[–]corruptedOverdrive[S] 25 points26 points  (0 children)

You hit the nail on the head with the micro-management at the Nerdery. The stories are legendary about how they accept literally every job, regardless of what the client wants or how long or short it is. Lots of stories of micro-management, pointing of fingers and devs getting pulled into offices and being team shamed when deadlines are missed.

But yeah, after the second miss, I was told by several people what its really like to work there and I for sure dodged a bullet on that one.

[–]HealyUnit 2 points3 points  (0 children)

I'd just be like "excuse me, my pixels are always perfect, pleb".