Side hustles for software engineers: 10 ways to earn without burning out

Software engineers have one of the most sellable skills on the internet. You can build things people pay for, fix problems businesses can't, and teach skills others desperately want. The challenge isn't finding a side hustle; it's picking one that pays properly without eating every evening, and without getting you into trouble with your employer.

Here are ten side hustles for software engineers, what each involves, how quickly it pays, and the rules to check before you write a single line of side-project code.

Side hustles for software engineers at a glance

Side hustle	Pays how soon	Upside
Freelance development	Weeks	High hourly rate
AI code evaluation	After acceptance	Flexible, well paid
Technical writing	Weeks	Steady, builds reputation
Mock interviews and tutoring	Weeks	Well paid per session
Selling templates, themes and plugins	Months	Sells repeatedly
Micro-SaaS	Months to years	Highest long-term upside
Bug bounties	Unpredictable	Occasional large payouts
Open source sponsorship	Slow	Grows with users
Consulting	Weeks	Highest per hour
Courses and content	Months	Scales

1. Freelance development

Small businesses, startups and agencies need websites fixed, integrations built and features shipped. It's the most direct way to turn your skills into money. Pick a clear specialty, like "Shopify apps" or "API integrations for small businesses," rather than "full stack anything." Our guide to freelancing for beginners covers proposals and pricing.

2. AI code evaluation

AI companies pay experienced developers to review AI-generated code, write better solutions and judge answers. Coding work pays more than general AI tasks; DataAnnotation, for example, lists coding roles at $40 to $150 or more an hour. See how to get paid to train AI for how to pass the assessments.

3. Technical writing

Developer tools companies pay for tutorials, documentation and blog posts written by real engineers. It builds your reputation too.

4. Mock interviews and tutoring

Job seekers pay for practice interviews with working engineers, and bootcamp students pay for tutoring. Sessions fit neatly into an evening.

5. Templates, themes and plugins

Starter kits, UI templates, WordPress plugins, Notion templates and spreadsheet tools can be built once and sold many times.

Your side project is only yours if you build it on your own time, with your own tools. Photo by Arnold Francisca on Unsplash.

6. Micro-SaaS

A small software product solving a narrow problem for a specific group. The potential is highest here, but most micro-SaaS products take many months to earn meaningful money, and marketing is harder than building. Validate demand before you build: talk to potential customers first.

7. Bug bounties

Security-minded developers can earn rewards for responsibly reporting vulnerabilities through programs on platforms like HackerOne. Payouts are unpredictable, and you must stay strictly within each program's rules and scope.

8. Open source sponsorship

If you maintain a useful open source project, users and companies can sponsor you. GitHub says it doesn't charge fees on sponsorships from personal accounts, as explained in its sponsorship fees documentation. Income usually grows slowly with the project's popularity.

9. Consulting

Senior engineers can charge high hourly rates for architecture reviews, performance audits and technical due diligence. Consulting is the most likely to conflict with your employer, so check your contract carefully.

10. Courses and content

Video courses, newsletters and YouTube channels teaching specific skills can grow into real income. See how to make money on YouTube.

How to choose between them

Ask what you want most. If it's money soon, freelancing or AI code evaluation. If it's long-term upside, a small product or a course. If it's career growth, technical writing, open source or consulting build your reputation while paying. And if it's variety after a day of coding, teaching or mock interviews use different muscles.

Check these before you start

• Invention assignment clauses. Many employment agreements claim rights to things you create. In California, Labor Code section 2870 limits those claims for inventions made on your own time, without employer resources, and unrelated to the employer's business. Other places have different rules.
• Outside work and conflict of interest policies. Some employers require approval or forbid work for competitors.
• Separation. Use your own laptop, accounts and time. Never use company code, data or credentials.
• Taxes. Side income is usually self-employment income; set aside part of every payment.

Avoid burnout

Coding all day and then coding all evening is a fast route to burnout. Many engineers do better with side work that uses different muscles, like writing, teaching or interviews, or by capping side work at a few focused hours a week. Our guide to making money on the side with a full time job has more on keeping it sustainable.