Google's guide for becoming a Software Engineer

In conclusion, I think a lot of my confusion as to where you're coming has been from the logical difference between the act of engineering a piece of software (without context such as being in a team or being a lone wolf), and the academic/legal requirements to hold the title of software engineer.

I have always regarded someone who declares themselves as capable of both designing and building software solutions, with heavily emphasis on designing with engineering principles, as a software engineer. I realize this may not be enough to fit the standard definition (which I didn't know even existed based on what I've seen with startup title abuse and programmers declaring themselves engineers or architects for the higher paycheck), but to me it has always been someone capable of designing and building software, and doing it well, and whatever tools they use to help them do it are important, but not necessary to fit the definition of the word "engineer."

I will concede that they have and probably will, going forward, make the definition for "software engineer" much more specific, which I am all for, even if I may disagree with some of the requirements (Not that I necessarily do, but I haven't looked into them deeply enough to know). As a license or standardized title, I agree that it should show competence in workflow, management, business, math, science, architecture, etc. Just, when a startup says they want an engineer, I have been programmed to assume they mean "someone capable of designing the software as well as building it" as opposed to lifecycle requirements, which are required of all programmers; not just the engineers.

/r/programming Thread Parent Link - google.com