Couldn't agree more. A bootcamp dev with 3 years coding experience might have 7 years of professional experience they are building on. I know several bootcamp devs with very relevant backgrounds too. For example, 5-10 years as a Certified Public Accountant before working at a fintech company. Or working as a nurse then going to a healthtech company.

>For example, 5-10 years as a Certified Public Accountant before working at a fintech company. Or working as a nurse then going to a healthtech company"

Can you explain how being a CPA would help give you seniority in a software engineer role at a Fin Tech company or how nursing experience would help give you seniority as a software engineer at a health based tech company?

Isn't being "senior" in this context of software engineering specific to your role and not the industry as a whole? I guess I'm failing to see the transitive relationship. If I previously worked as taxi driver would that help me as an SWE at Uber? Or if I worked in retail would that best me as as an SWE at Amazon?

I get your point, but here's how I'm thinking of it. Software developer A is 22 and just graduated with a CS degree. Software developer B is 29, has a CPA, and three years of experience managing more junior accountants.

Both get hired at a FinTech company. Is software developer A or B more likely to rise to the level of "senior" in the next 5 years? I'd say B... Already has tons of domain specific knowledge that will help him focus solely on the technical issues at hand (instead of trying to understand how Balance Sheets work or something), has 7 years experience as a working professional and all the soft skills associated with this, and has experience as a manager.

IMO, too many SWEs think that the technical stuff is the only aspect to their job. Often (depending on company size, etc) there are many, many other skills required to be a successful employee.

Keep in mind that "senior" or other title doo-dads don't really have a fixed meaning.

Also, depending on the workplace you may be undervaluing domain experience. Yeah, of course, a taxi driver isn't going to ascend at Uber because of Taxi driver skills. But a high-skilled experienced CPA with a knack for software development could do really well against 20-something SWE's at a fintech company.

>"Keep in mind that "senior" or other title doo-dads don't really have a fixed meaning."

Now your shifting the discussion a bit with the concept of title inflation. I think the intention of "Senior" is very clear with respect to junior and mid-level career stages. It is not a "doo-dad" in the same way that something like "Customer Success Associate" is.

At my company, and every other large company I have worked for titles absolutely have a fixed meaning. There are standard pay bands that are largely predicated on your title.

_Within_ any one company, sure, "senior" may mean something.

But looking across companies... Nope. A "junior" could easily change jobs/employers and land on a "senior" title or vice-versa.

>"I expect that many people who enroll in bootcamps are coming from domains other than sw development. As such, they may have years of experience and skill-sets which complement the new skills they picked up at bootcamp."

I don't doubt the value complimentary skills at all but 3 years of actual software engineering experience and exposure and say 7+ years are very different things. I don't think there's any substitute for "rubber on the road."