How did you land your first freelance DevOps client?
Asked by
MellowPine47
I work full-time as a DevOps engineer and have experience with AWS, Kubernetes, Terraform, Docker, Linux, CI/CD, monitoring, and cloud infrastructure. I'm considering freelance or part-time consulting, but I'm not looking for job offers—I'd like to learn from people who have successfully made that transition.
How did you find your first client? Did you use a freelancing marketplace, professional networking, LinkedIn, referrals, or another route? Which services were easiest to sell at the beginning? Did you create a portfolio, blog, GitHub projects, or open-source contributions first? How did you set your initial hourly rate, and what mistakes should newcomers avoid?
Answers
A polished portfolio isn’t mandatory, but a few well-documented examples help establish trust. A GitHub repository, home lab, technical write-up, or open-source contribution can show how you approach infrastructure, security, automation, and documentation. Focus on explaining the problem, your decisions, and the result rather than just listing AWS or Kubernetes on a résumé.
Reply to this answer
Be careful with pricing. Don’t calculate your freelance rate by dividing your salary by the number of working hours. You’ll also be covering taxes, insurance, benefits, equipment, software, sales time, administration, and gaps between contracts. Your billable hours will be lower than your total working hours, so the rate generally needs to be substantially higher—often at least around twice the equivalent salaried hourly rate, depending on your location and expenses.
Reply to this answer
Freelancing is running a small business, not just doing the same technical work with more freedom. You’ll need a simple contract, clear scope, payment terms, references, and a process for handling support and changes. Marketplaces can provide leads, but infrastructure work there is often heavily price-driven. Networking, local business groups, conferences, and a simple professional website may produce better-quality opportunities over time.
Reply to this answer
Don’t market yourself as simply doing “DevOps.” Pick one painful, specific problem and make that the offer—for example, migrating CI/CD to GitHub Actions, automating AWS infrastructure with Terraform, Dockerizing an application, reducing cloud costs, or fixing deployment reliability. A narrow service is easier for a client to recognize and buy than a long list of technologies.
QuietMarble6: That was my experience too. Saying “I do DevOps” got almost no response, while leading with cost optimization gave people a concrete problem to discuss. Warm introductions help, but they still work better when the offer is specific.
Reply to this answer
For most people, the first client comes through someone they already know: a former coworker, previous customer, friend, or professional contact. Someone who has already seen you solve a real production problem is much more likely to trust you than a stranger viewing a profile on a marketplace. Word of mouth and a good reputation tend to make the next few projects easier to find.
Reply to this answer
Add your answer
Answers are reviewed before publication.
BriskLemon14: It’s also worth separating business and personal finances from the beginning and tracking expenses carefully. Business registration and tax structures vary by country, so getting advice from a qualified accountant or attorney is safer than relying on generic online guidance.