From freelance consulting to indie SaaS — leveraging your technical edge
Engineers earn the highest side income of any profession — technical skills + analytical mindset + high day-job pay = unfair advantage.
Freelance consulting ($150–$400/hr via Toptal, A.Team), indie SaaS ($1K–$50K MRR), technical writing for dev tool companies ($300–$800 per article), Udemy/Teachable courses, expert witness ($300–$500/hr).
Engineers have the highest earning ceiling of any profession in side work, and the most common failure mode to go with it: building rather than selling. The instinct to make the thing well is exactly the instinct that produces a polished product nobody was waiting for.
Freelance and fractional technical work converts existing skills directly into income with no build phase, and it pays multiples of the gig-economy rate. It is also the option engineers most often skip, because it feels less interesting than building something.
Most employment contracts in engineering include assignment-of-invention and moonlighting clauses, and they are far broader than people assume. Read yours before you start, not after something works — the clauses that matter usually cover anything built in the same field, whatever hardware you used.
The sequence that works is to find someone who will pay before writing the code, rather than after. That inverts the natural instinct and is the single highest-return habit change available in this category.
See also: Side Hustles for Veterans.
Freelance and fractional consulting, by a wide margin, because it converts existing skills into income immediately with no build phase. It is also the option most often skipped, because it feels less appealing than building a product.
Check your contract first. Assignment-of-invention and moonlighting clauses are standard in engineering employment and are usually broader than people expect, often covering anything built in the same field regardless of whose equipment you used.
Because they are built before they are sold. The instinct to make the thing properly produces a polished product with no buyer. Finding someone who will pay before writing the code inverts that, and it is the highest-return habit change in this category.
Tax rules, limits and pay data change. Check the current figures with the primary source before acting on them.