3 ms·
I'm in the same position. Plus with too many short term positions on your resume it makes finding a job at all (let alone a decent one) harder. I have been at
by flukus 10y ago
I'm in the same position. Plus with too many short term positions on your resume it makes finding a job at all (let alone a decent one) harder.
I have been at one place that was good though, unfortunately I left it to relocate. I haven't found anyway remotely close to the same quality in they ~6 years since.
I've developed a few proxy questions to estimate exactly how shit they are though.
- lotyrin 10y agoDefinitely have a refined set of interview questions developed, if nothing else to show for it. Never really get past: "Walk me through the steps of the your design process, what steps does software go through to get from conception to production on your team, who is responsible for each step, and how do they test the assumptions inherent in their designs?" "Uh... well... <handwaving about how roles aren't defined so nobody's responsible, why wouldn't you be confident about your 'decisions', maybe 'design' is too strong a word?>"
- flukus 10y agoMy best is "when I fix a bug, what are the steps to get it in production". It gives an insight into the corporate culture as well as their automation level. Also, anywhere that uses TFS is an instant no, and I think SVN will be on that list now too.