4 ms·
Make damned sure the "test automation position" is really a software development position, realize that the field in general doesn't get any respect, and be pre
by hga 17y ago
Make damned sure the "test automation position" is really a software development position, realize that the field in general doesn't get any respect, and be prepared to explain on your resume etc. how this wasn't really a testing per se position. Especially if you discover you don't like it and want to get back to software development.
(OK, yeah, I've been burned badly here, Lucent in 2001.)
As for deciding in general, can you convince them it's not a bad idea? Best is the enemy of good enough ... except for the longer term a true software development position where you'll be doing cutting edge stuff should leave you in a better position for the future. And you have already gone through the startup failure experience, just without the minor baggage of a family and a house....
Good luck.
- lief79 17y agoGood feedback, thanks. I got placed firmly into test from a split test/development position a few jobs ago. I'd call it a slight burn on my part. The job title of Software Engineer and the reputation of that company make up for it, I just didn't get to continue developing software there as long as I would have liked. In this case, they are talking about needing a developer to test middle ware using a custom groovy testing application, and the testers they've had with out the software experience haven't worked as well.