In the United States, you can legally call yourself a software engineer in almost every situation. State engineering laws generally protect the term “professional engineer,” not the standalone word “engineer,” so using “software engineer” on a résumé, business card, or LinkedIn profile does not claim a state-issued license. A few states enforce their title rules aggressively, and Canada’s provinces have historically been stricter, but for the typical developer working at a tech company, the title carries no legal risk.
What State Law Actually Protects
The protected terms in most U.S. states are “professional engineer,” “licensed engineer,” or “registered professional engineer.” Those phrases signal that someone has passed the Principles and Practice of Engineering exam, met state experience requirements, and can sign and seal design documents while taking personal legal responsibility for the work. “Software engineer” doesn’t do that, and most state boards recognize the difference. That’s the structural reason tech companies have used the title for decades without triggering mass enforcement.
A handful of state boards read their statutes more broadly, treating any commercial use of “engineer” as an implicit claim of licensure. Others look only at whether someone is offering engineering services directly to the public. So the risk isn’t uniform across the country, but in most places it’s low enough that no competent lawyer would tell a software developer to change their title.
The Industrial Exemption Covers Most Developers
Nearly every U.S. state except Oklahoma and Arkansas has what’s called an industrial exemption. It lets employees of private companies perform engineering work without a professional engineer license, as long as the work is internal to the company and not sold to the public as engineering services.
Oregon’s version, codified in ORS 672, covers engineering work “in connection with or incidental to the operations” of a company when “the engineering work is not offered directly to the public.” Florida’s exemption covers “regular full-time employees of a corporation not engaged in the practice of engineering as such, whose practice of engineering for such corporation is limited to the design or fabrication of manufactured products and servicing of such products.”1Florida Board of Professional Engineers. What Is the Industrial Exemption? A developer building internal tools, shipping features for a SaaS product, or writing code for a consumer app fits comfortably inside those definitions.
The exemption has edges. Even employees it covers generally cannot use the specific titles “professional engineer,” “licensed engineer,” or “registered professional engineer.”1Florida Board of Professional Engineers. What Is the Industrial Exemption? A freelance consultant marketing engineering services directly to individual clients falls outside it. So does work on public infrastructure like bridges, buildings, or utilities, which requires a licensed PE in responsible charge.
The States Where Enforcement Bites
Texas is the most aggressive. Under the Texas Engineering Practice Act, administrative penalties run up to $5,000 per violation, each day a violation continues counts as a separate offense, and the board can add the actual costs of investigating and prosecuting the case.2State of Texas. Texas Occupations Code Chapter 1001 – Section 1001.502 Those numbers can accumulate quickly if a board decides a commercial use crosses the line.
Oregon’s statutes define “engineer” as someone registered and holding a valid certificate to practice in the state. Civil penalties can reach $1,000 per offense.3Oregon State Legislature. Oregon Revised Statute Chapter 672 – Section 672.325 The Oregon board drew national attention when it fined Mats Järlström $500 for calling himself an engineer while communicating with the government about traffic light timing. Järlström held an electrical engineering degree and decades of engineering experience, and the board told him he could not publicly discuss traffic lights or use the word “engineer” without an Oregon license.
The First Amendment Limit on Title Rules
Järlström sued and won. In December 2018, Magistrate Judge Stacie Beckerman of the U.S. District Court for Oregon ruled Oregon’s title restrictions “substantially overbroad in violation of the First Amendment,” citing the board’s “history of overzealous enforcement actions” against people using the title in non-commercial contexts, including political speech.4Oregon State Board of Examiners for Engineering and Land Surveying. Opinion and Order – Jarlstrom v Aldridge The court entered a permanent injunction letting Järlström call himself an engineer and declared the relevant Oregon title statutes facially unconstitutional.
The ruling doesn’t automatically strike down title laws in other states, but it set a clear marker: a state cannot use its engineering title statute to suppress non-commercial speech. For software developers, that means using “engineer” on social media, in personal communications, or in political advocacy sits on protected ground. The actual legal risk concentrates in commercial contexts where someone might reasonably think you hold a PE license and rely on that belief when hiring you.
Freelancing and Consulting Change the Analysis
The industrial exemption protects employees, not independent contractors selling services to the public. If you work as a freelance developer and advertise yourself as an engineer to individual clients, you are closer to the kind of commercial representation that state boards police. The practical risk in most states remains low because “software engineer” is widely understood as a job description rather than a licensure claim, but the exemption that makes an employed developer clearly safe does less work here.
Work tied to public safety or public infrastructure is a separate category. Software that controls traffic systems, medical devices, aerospace controls, or structural monitoring may intersect with regulated engineering practice, and in those settings a licensed PE must take responsible charge even if the day-to-day code is written by developers who aren’t licensed.
Canada Is Different, and Alberta Is the Exception
Canada’s rules are stricter than the American ones. Provincial legislation across the country designates “engineer” itself as a protected title reserved for licensed members of provincial engineering regulators.5Ontario Laws. Professional Engineers Act RSO 1990 c P.28 Courts can impose fines and injunctions for unauthorized use.6Engineers Canada. Use of Professional Title and Designations Where U.S. states usually protect “professional engineer,” most Canadian provinces have historically protected the shorter word.
Alberta broke from that pattern in 2023, amending its Engineering and Geoscience Professions Act to let technology companies and workers use the title “software engineer” without holding a provincial license.6Engineers Canada. Use of Professional Title and Designations No other province has followed, so a developer in Toronto or Vancouver using the title faces more exposure than one in Calgary or in any American city.
When PE Licensure Still Matters for Software Work
There is no PE exam specific to software engineering. NCEES first offered one in 2013, but only 81 candidates total sat across five administrations, and the April 2018 session drew just 19 registrants. NCEES discontinued the exam after April 2019, citing the persistently low candidate population.7NCEES. NCEES Discontinuing PE Software Engineering Exam A software professional can still pursue licensure through a related discipline such as electrical or computer engineering, though the exam content won’t closely match most software work.
For developers in aerospace, medical devices, automotive safety, or other fields where software directly controls physical systems, licensure in a related discipline can carry real professional value, because the ability to sign off on safety-implicated designs has legal weight. For the much larger population building web applications, mobile apps, and enterprise systems, PE licensure offers no practical advantage, and the industry doesn’t require it. Calling yourself a software engineer, in that world, is both the normal usage and the legal one.