[quote=svelte][quote=an]So glad I never had to deal with people like svelte and deadzone earlier in my career while interviewing.[/quote]
Sounds as if you’re a jumper. I wouldn’t want to train you up just to have you jump to another position a year later. That would be frustrating!
I get that there are exceptions, those who worked for companies that folded, etc. If there are good reasons for the jumps, I would certainly listen – and then I would verify those reasons were true. But the truth is, I would probably never even arrange the interview once I glanced at the resume…so the probability you would have had to deal with folks like me is low to begin with.[/quote]
I really don’t think it matters. Just like the real estate market, there’s a buyer for every house at various price points. And a competitive market where there’s a tight supply, those difference are even of less concern. So yes, while you and other companies might not be interested in hiring AN. That’s ok. There’s plenty of other companies that would hire AN and not hire candidates that might be a better fit for your company’s philosophy or style.
Also, quite honestly, in these day and age of mobile software. There’s very little that a company needs to do to “train” someone on the basic principles and architectures of doing a good app..All that information is already available out there on the internet in an open way, and it’s just a matter of spending the time to do a challenge project, whether it’s within the structures of a corporation or yourself… (with the exception of maybe apple, which you need to pay $99/year for a developer account, but still the financial bar is pretty low to join that program) So it’s quite common that a fresh college grad already has the basic tools he/she/they need to be a decent mobile engineer. Mobile phone for development + $99/year developer membership + computer to run IDE (for IOS/XCode, that means a Mac which you can do on a Mac Mini if you’re cheap).. OR…if you’re really cheap, do it on a Hacintosh, if you don’t plan on actually submitting the app to the app store (because your Hacintosh would violate all Apple EULA agreements..)
A lot of the “training” that a company needs to provide is about the specific business logic specific to the company’s business/IP… That knowledge doesn’t exactly carry over to the next job because depending on what that next job could be, the app he/she is working on might have nothing to do with the previous one and is only useful from within the boundaries of the previous company. My engineers ding candidates who know nothing about coroutines and other prominent async programming methodologies, for instance, because they don’t want to bother spending time teaching them about it. It’s all documented and all out there in the open and anyone worth their salt can learn about it themselves. They expect anyone coming in to already know that. And that usually also comes out in the take home assignment whether they get it or not. that’s what separates from the ones that really get it from, the fakers that take a 6 month crash course at a for-profit college like “Full Sail University” or “DeVry” or “University of Phoenix” to pad their resume, but have no idea what they are doing.
Case in point. The product I was in charge of at my last company has very little to do with the products I’m in charge of now. There was no carryover of knowledge I learned about search tech at my previous company to what my current company is working on.
