Agree! I would like to add to all of the above, the following thoughts: In today's climate 3-4 year stints might be OK early career. Or maybe just one year as

Agree! I would like to add to all of the above, the following thoughts: In today's climate 3-4 year stints might be OK early career. Or maybe just one year as the first job out of school - it's understandable if that wasn't a good fit. But a history of 1-2 year stints without some good reason? You're a hopper and I'd burn your resume. Hard pass. - It takes time to become really productive at a new job. I'd estimate 6 months to a year. Why invest if you're just going to leave as soon as you're finally starting to be a net positive? - I don't think software engineering is an assembly-line job. It's a craft and I don't appreciate companies or employees trying to make it a fungible manpower vs. compensation game. You're a code-monkey-for-hire, not an engineer. It's toxic to the other engineering professionals that would be subjected to you. If I wanted that, I'd just hire consultants. - It shows a pattern of short-term vs. long-term thinking. That pattern will often represent itself in more than just job choices. For example, taking engineering short-cuts to meet a near-term goal at the expense of long-term quality. What do you care, you'll be gone before we realize the mess you made? Yes. Seriously bad look. But wait! Perhaps all those things I just assumed aren't true of you! What I'd say is that this is just what it looks like and what many people will assume. You should proceed with awareness of that and perhaps try to mitigate it.