How to Do Freelancing As an Embedded Engineer
Rosmianto A. Saputro
Freelance is a wonderful world:
- You get to choose who you work with.
- You get to choose what project you work on.
- You get to choose how much you are getting paid.
It offers lots of freedom and flexibility.
But, given those pluses, freelance is also hard. Because instead of just doing the tasks from your boss, now you have to find clients. Sometimes it's easy, but often it's challenging to get clients.
But again, the pluses far outweigh the minuses. No wonder freelancing is so seductive for many talented engineers. It's too sexy to ignore. You should not quit your main job if you have zero knowledge of the freelance world.
That's too risky. Instead, do freelance on the side, and slowly transition from full-time employee to full-time freelancer (if you want to. I have friends who prefer part-time freelance indefinitely).
Now, to be a freelance embedded engineer, you need to assess your profile first.
I will be using my 3-check criteria to check your readiness:
- 2 years of experience minimum
- 10+ hours a week to spare
- Self-disciplined and autonomous
Let's dissect them one by one.
1. Two Years of Experience Minimum
2 years minimum is a subjective criterion, actually. But it helps me to see if someone has enough exposure to the corporate world.
Less than 2 years usually an engineer still doesn't know the full cycle of embedded project development. They never shipped a product, never tested device on the field, never knew how to handle business pressure to technical development.
If you have less than 2, you still can be a freelancer, but I'm afraid you will not survive and leave negative views of freelance world.
Remember, embedded freelancing is different with other types of freelance like video editing, translation, voice over. There are specific knowledge and skills required to survive it.
2. 10+ Hours/week To Spare
Now, accepting freelance projects means you work outside your main job. And the great part of freelance is, you have the freedom to set your schedule. You just need to make sure your clients are kept updated every week.
In my experience, 10 hours a week at minimum is a sweet spot to make a significant project progress. Less than that usually you can only do minor work. And most clients also have time constraints.
Because I say 10 hours a week, that means you can work 2 hours on Monday, 2 hours on Tuesday, and 6 hours on Saturday. Or..
5 hours on Saturday, 5 hours on Sunday. You get the idea. You pick yourself.
Make sure you send the progress update to your clients every week.
3. Self-Discipline and Autonomous
Lastly, you have to have those 2 traits: self-disciplined and autonomous.
If you need to constantly be told what to do, what next, how to do it. Ahh, forget freelancing. It won't suit your style.
Because in reality, freelancing requires lots of discipline, because your clients don't know what you should do. That's why they hired you as a freelancer.
They don't have the bandwidth to check your work every hour.
They only have the money to pay for your work.
In my experience, someone who has these traits is usually a senior engineer.
How to Land Freelance Clients
Now, if you pass those 3-check criteria, you are ready to get clients. My method below is for long-term
Follow my 3-step framework to get clients:
👉 Set your expertise. What projects do you want to do? Robotics? IoT? Firmware Development?
👉 “Attract” not “hunt” clients. Do that by showing your expertise through posts on LinkedIn.
👉 This is the hardest step, it might test how serious you are. Publish daily for the next 30 days.
Do that and you will have someone DM you end of the month.
Whenever you're ready, there are 2 ways I can help you:
1. FREE Firmware Development Email Course. A free 7-Day Email Course to teach you the foundational concepts you should know to start firmware development. Full of practical tips and industrial insights.
2. FREE Embedded Freelancing Email Course. Another free Email Course to help you grasp the basics of embedded freelancing and make more money as an embedded engineer.
