Hacker News new | past | comments | ask | show | jobs | submit login

I'm really interested in your last sentence there -

Something that I learned before I converted fully to SWE is that most other domains of engineering have this class of job I'll call a "tech." In the hardware world they're electricians, or electronics lab techs, in mechanical they're mechanics, and in the other domains you'll call them lab techs or factory techs.

It's a highly technical role with a different entry point that has a harder path to a higher tier of compensation, but also contains a pathway to management and more integration at an organizational level (similar to technical vs management tracks for engineers).

What's different is that domains outside SWE have pretty well-defined ways for people to enter into the "tech" position. Vocational training, like through trade schools, community colleges, the military, etc. We do not have that in software, yet.

Bootcamps are like an experiment into the vocational training to develop a "tech" for software development. Our industry is still very young, so we haven't found a way to define the roles for people that go through that training, and people don't know how it fits in or what the job responsibilities/management should look like yet. I think the model of treating a bootcamp grad like a potential junior engineer is wrong - it's really a separate track for career development.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: