> I don't work with people who can't do the whole thing. So having a "generalist" team doesn't sound like anything special, even though I'm aware this is an odd

> I don't work with people who can't do the whole thing. So having a "generalist" team doesn't sound like anything special, even though I'm aware this is an odd thing in the corporate world. Where do you work? and are you hiring? I haven't met a company (even a startup company) that would prefer to hire a generalist over a specialist. At every startup I've worked at, being a "generalist" means you fill whatever position hasn't been hired for yet. I typically spend a few months in a specific job role and shift to a different one whenever a specialist is hired. My preferred method of working is the same as the OP's: I like implementing whole features from start to finish. In my 10 years of experience, I've been able to do that in exactly one job and it only lasted 6 months before the product was finally sunset.