3 ms·
To be honest, if I were looking at a resume that reads like I expect yours would, I would probably pass on it unless I was looking for an architect/principal so
by CuriouslyC 11y ago
To be honest, if I were looking at a resume that reads like I expect yours would, I would probably pass on it unless I was looking for an architect/principal software engineer, and in that case I would need to see interesting technical accomplishments and leadership experience as well. Less experienced developers are cheaper, probably have a more current education, and are less set in their ways (e.i. more trainable).
I recognize you will probably make fewer dumb mistakes than a younger developer, and your experience probably enables you to learn new technologies faster (though I'd wonder if you didn't list any trendy technologies on your resume). On the flip side, if your resume showed a long period without any significant career advancement I might question your competence.
- slindsey 11y agoIt's difficult to codify "career advancement". What does it mean? To whom? I've been a "programmer", "analyst", "database administrator", "developer", "consultant", and "manager". What order shows advancement?
- CuriouslyC 11y agoWell, it is a bit of a red flag if you list them in non-chronological order (unless you wrote a functional resume that was tailored specifically to the requirements for my position, in which case you get bonus points). You should be able to show career advancement via the achievements you list for each position. There should generally be a trend towards increasing responsibility and successively more impressive feats at each stage. Some lateral movement is fine, but if that's all you've got it suggests that you lack focus/get bored easily.
- slindsey 11y agoTrue. The description/achievements are key. I guess my point was that the distinction in my titles was largely a result of HR practices at the organizations and not an indicator of advancement. For example, at most companies an "Analyst" position is higher than a "Programmer", yet I had that first. And if I didn't choose to become a manager, showing growth at my current position would be difficult.
- gutnor 11y ago> Less experienced developers are cheaper What are we talking about here ? Comparing a developer with 10 year experience vs with 20 years ? Or one fresh out of school, with a senior developer ? Because around here, your salary will be determined by your actual responsibilities and the only way for a guy with 20+ years of experience to make more than one with 5-10 years is to have been in that company for during those 20 years, accruing benefits. Similarly, contract price are about the same. They haven't even raised much in the last 10 years. Unless you become consultant on a specific topic, you are getting paid the same regardless how much more experience you have over 3 years. The inflexibility has a flip side too: a developer that has been developing for 20 years is most likely doing exactly what he wants to do. Can probably count on him to be there to see the project through production, and not having "move up" or strategically move to other office, technology stack, companies.