> "2) I didn't take any interest in the full stack when the company needed a full stack developer." I would consider this a good, ethical thing to do, and not

> "2) I didn't take any interest in the full stack when the company needed a full stack developer." I would consider this a good, ethical thing to do, and not at all unethical. The company's needs don't always come before your needs to protect your specialization and your work experience, not even in early-stage start-ups. It's on the management to get the right people, not to trumpet around some disingenuous "everyone wears many hats" philosophy to squeeze inappropriate work out of you. It can really be damaging to your career if you get hired into a start-up to do X, but then because "wear many hats" or "we're a lean shop" or whatever nonsense, you only spend your time doing Y. After that, if your real passion was to work on X, it can be really hard to get employers to look at you seriously for hiring for X. You'll be pigeonholed into Y. Since employers ought to care about career goals and growth of their staff, it definitely makes this sort of thing more the employer's fault than the employee's. So, I would say item 2) is not unethical at all -- and in fact it's deeply important for people around the industry to take a hard line with this sort of thing when they need to protect a career-goal specialty.