Can I legally call myself a software engineer without a professional engineering license? I recognize that certain types of engineering disciplines are very heavily regulated. As I understand, these types of engineering have a legal definition that requires licensure, without which one cannot claim to be an engineer in that discipline. For example, someone with training in civil engineering can't call themselves a mechanical engineer without obtaining a license to practice civil engineering. This licensure requirement is intended to promote the health, safety, and well-being of the general public. Do software engineers need a license, or can I call myself a software engineer right after graduation?
There is no general answer: it's a state-by-state question. Texas Occupations Code 1001.301(b) says that a person may not, unless the person holds a license issued under this chapter, directly or indirectly use or cause to be used as a professional, business, or commercial identification, title, name, representation, claim, asset, or means of advantage or benefit any of, or a variation or abbreviation of, the following terms: (1) “engineer” etc. You cannot call yourself that, in Texas. Subsection (f) provides for an exemption: Notwithstanding the other provisions of this chapter, a regular employee of a business entity who is engaged in engineering activities but is exempt from the licensing requirements of this chapter under Sections 1001.057 (Employee of Private Corporation or Business Entity) or 1001.058 (Employee of Certain Utilities or Affiliates) is not prohibited from using the term “engineer” on a business card, cover letter, or other form of correspondence that is made available to the public if the person does not: (1) offer to the public to perform engineering services; or (2) use the title in any context outside the scope of the exemption in a manner that represents an ability or willingness to perform engineering services or make an engineering judgment requiring a licensed professional engineer. 1001.057 does allow an exception for &quot;products manufactured by the entity&quot;, which under the law includes computer software. Whether or not (1) and (2) apply to a given employee / business depends on what they do: you can't open up a code-writing shop for the public and use the term &quot;engineer&quot;, but you can be a software engineer for Shell Oil. In Washington, RCW 18.43.010 says that it shall be unlawful for any person to practice or to offer to practice in this state, engineering or land surveying, as defined in the provisions of this chapter, or to use in connection with his or her name or otherwise assume, use, or advertise any title or description tending to convey the impression that he or she is a professional engineer or a land surveyor, unless such a person has been duly registered under the provisions of this chapter. which is not as clear as Texas law (I would not have thought that a &quot;software engineer&quot; is a &quot;professional engineer&quot;. The term &quot;professional engineer&quot; is defined in RCW 18.43.020 as a person who, by reason of his or her special knowledge of the mathematical and physical sciences and the principles and methods of engineering analysis and design, acquired by professional education and practical experience, is qualified to practice engineering as defined in this section, as attested by his or her legal registration as a professional engineer. Having kicked the can down the road a bit, &quot;professional engineering&quot; is defined as any professional service or creative work requiring engineering education, training, and experience and the application of special knowledge of the mathematical, physical, and engineering sciences to such professional services or creative work as consultation, investigation, evaluation, planning, design, and supervision of construction for the purpose of assuring compliance with specifications and design, in connection with any public or private utilities, structures, buildings, machines, equipment, processes, works, or projects. If &quot;software engineering&quot; is a kind of &quot;professional engineering&quot;, you must register, and here are the requirements, which ultimately refers you to the PE Electrical and Computer exam, which includes EE-type stuff that probably few software engineers know, and some software-related stuff including general computer architecture that is also not general knowledge among computer programmers. Judging from advertisements for &quot;software engineer&quot; position in Washington, jobs state qualifications as as having a degree and knowledge of software, but not possession of a license or being registered as a &quot;professional engineer&quot; (and the exams only happen twice a year so it's not a trivially satisfiable formality). Either there is a massive conspiracy to mislead applicant or scoff at the law or, more likely, software engineers in Washington are not considered to be &quot;professional engineers&quot;. This includes huge numbers of jobs with Microsoft, which are open to students who are years from being able to satisfy the 8-year experience requirement.
You won't be able to get around self-doxxing yourself. § 5 Abs 1 TMG requires tele-media service providers like you to list den Namen und die Anschrift, unter der sie niedergelassen sind the name and the address where they reside or are established Similarly, Art 13(1) GDPR requires you to provide the identity and the contact details of the controller In a German context, it is generally accepted that both of these involve a ladungsfähige Anschrift, i.e. a street address where you could be served with a lawsuit (not a post box). These requirements exist for both natural persons and legal entities, and for both businesses and non-commercial activities. The TMG Impressumspflicht talks about “geschäftsmäßige, in der Regel gegen Entgelt angebotene Telemedien” but in practice this only requires that the service could be paid (not that you're actually making any money), and that the service is offered routinely/business-like (not necessarily commercially). It does not matter where your service is hosted as long as you live in Germany. The TMG and GDPR might not apply if the forum is run purely privately, e.g. if it is only made available to a few close friends or family members.
Raise the question with your employer If you believe that you are an employee and not a contractor then there is presumably something you want from your employer. This may be additional wages and entitlements that you would have or will become entitled to for past or future work respectively. Or you may have been injured and want workers' compensation. Or terminated and you want redundancy pay. Whatever it is, work it out and raise the issue with your employer. You might want to consult an accountant or union to help you. They may acknowledge that you were incorrectly classified and give you what you want. Winner, winner, chicken dinner! Or they may dispute it. If so, you need to follow the dispute resolution processes at your workplace. These typically involve informal discussions, escalating to mediation and then to a workplace tribunal run by the government. You will almost certainly want to consult a lawyer or union to help you - given that you don't know where to start the learning curve is likely to be too steep. In virtually every jurisdiction if people are employees at law they can't choose not to be. in british-columbia the relevant law appears to be the Employment Standards Act although it's not unheard of in edge cases for a person to be an employee under one law (e.g. workers' compensation) and a contractor under another (e.g. income tax). From the linked site: The overriding question is “whose business is it?” Is the person who is doing the work doing it as a person in business for themselves? If you are working "for" your own business you are probably a contractor. If you are working "for" your employer's business you are probably an employee. For example, if you are an accountant with several dozen clients, maintain your own business premises and charge for your advice based on the amount quoted rather than by the hour, you're a contractor. If instead, you have 2 clients, work from their premises at set hours and get paid by the day or week, you're an employee with 2 jobs. In edge cases these are not cut and dried - Google are Uber driver's employees. In Australia: no. In California: yes. In the UK: yes.
It is possible if and only if you can say exactly what you mean, and what you mean isn't prohibited by law. Software licenses can have all sorts of conditions attached to them, such as use (commercial or not; educational) or a quasi-demographic (are a student at UX, are employed by Z; reside in Y). &quot;Mega-corporation&quot; is not at all defined, so you would need to specify what it means to be a &quot;mega-corporation&quot; (is it defined in terms of assets, or income, and what is the magic number that is not to be crossed). What do you mean by &quot;corporation&quot;? Your license might not achieve what you intended it to achieve, if you don't think about ways to legally get around the restriction (can a mega-corporation have an employee incorporate your code into a product, as an individual, and then sell the rights to the product to the mega-corporation for $1, or for $1,000,000? If not, what part of the license says you can't). Also bear in mind that a license might be for a fixed period (a nuisance), or perpetual (the usual case), but status as a &quot;mega-corporation&quot; is ever-changing (Microsoft was a garage operation a few years ago; Blockbuster was a mega-corporation a few years ago). Do you want people or companies to lose their license right once they make a certain salary / income? The license would be discriminatory, but not all forms of discrimination are illegal – I don't think this would actually run afoul of any anti-discrimination laws.
If it is open source code, then usually the requirement is that you produce the source code for the software that you release. Exactly for the software that you release. For example if you took open source software X, and added feature Y, and distributed the combined software outside your company, anyone can request the source code for X including Y. Handing them the source code for X only wouldn't meet the open source requirements. Now all this is not illegal, but it means the copyright holder of X could sue you for copyright infringement. They will do that if they have enough reasons to do so. So let's say you are continuously developing your software and occasional hand out your compiled software. Say you built versions 100, 101, 102, 103, 104 of the software, you gave versions 100 and 103 to customers, and anyone asking for the source code is given the source code for the latest, slightly improved version 104. The copyright holder of X might sue you but: 1. They wouldn't know you are doing this. 2. A judge might side with you and decide that newer, improved source code is good enough (I don't know this, but it seems not unreasonable). 3. The copyright holder might decide that they don't want to sue you for this because you are close enough to meeting the requirements.
No The intent of the proposed bill is to codify existing case law. You are an employee now and you will be an employee then. You are an employee now because a) you are not free from the company's control and direction or b) the work you are doing is the company's main business. If you read the bill you will find out that c) involves "an independently established trade, occupation, or business" so your business qualifies for this but you need to qualify for all three factors to be an independent contractor.
Do you have permission of the person? In general, product names fall under trademark law, not copyright. And while it's possible to use the name of a non-employee as a trademark, doing so without the permission of that person is rather dangerous. That person may sue you for a number of different reasons, with different demands - chiefly financial compensation or a rename of your product.
You will need a license for any library that you are including in your product. Including libraries that you didn't really want to include, but which are needed by another library that you intentially include. And you will have to agree to all the licenses simultaneously, which may be difficult. If several libraries have conflicting licenses (that is you cannot possibly respect A's and B's license at the same time), then you must remove one of the libraries until no conflicts are left.