Who gets in, and who does not
The network is small on purpose. A roster nobody has spoken to is a directory, and directories do not get anyone hired.
- Experience
- Around four years of production work, minimum
- Certification
- Cloud certification expected, verified at source
- References
- Two, from managers or paying clients
- Structure
- Individuals and small specialist teams
- Regions
- North America, UK and EU, Middle East, India, Singapore, Australia
- Cost
- None
CloudOps Network accepts independent engineers and small specialist teams with around four years or more of production experience, verified cloud certification, and two references from managers or paying clients. Members must be able to contract independently, represent scope and customer situations accurately, and work only after a purchase order is issued.
What we look for
Production experience
Systems you built that ran, broke, and got fixed. Notebook and prototype work does not carry the same weight.
Verified credentials
Cloud certification confirmed with the issuer. Kubernetes, security and data credentials where the specialisation calls for them.
References that check out
Two, from people who managed or paid for the work. We ask what went wrong as well as what went right.
Ability to contract
You can sign a subcontractor agreement in your own name or through your own entity, without a conflicting obligation elsewhere.
Communication
Clients read your written updates. Engineers who cannot explain a decision in plain language do not get rematched.
Straight dealing
The compliance structure rests on accurate representation. This is the standard we enforce hardest.
What ends membership
Short list, applied consistently. Two of these carry an immediate exit rather than a conversation, because the network's access to funded work depends on them.
This is not about being strict for its own sake. One inaccurate submission can jeopardise the accredited standing that every member's benefits depend on.
Inaccurate claims
Overstated scope, inflated figures or misrepresented customer facts. Immediate exit.
Starting work before a purchase order
It cannot be covered and it compromises the submission. Immediate exit on repetition.
Going around the agreement
Taking a funded opportunity direct after it has been through intake.
Repeated delivery failures
Feedback is recorded per engagement. A pattern ends membership.
Eligibility questions
I am certified but I work through an agency. Can I join?
Usually yes, provided you can contract independently for the work and nothing in your existing agreement prevents it. Check your own contract before applying.
I run a small agency rather than working solo. Can we join?
Yes. Small specialist teams are a meaningful part of the network, and the same standards apply to the individuals who would deliver.
I am strong but not certified. Any route in?
Tell us anyway. Certification is a strong signal and not the only one. Substantial production experience with verifiable references is sometimes enough, and we will tell you which certification would settle it.
Do I need to bring a customer to join?
No. Plenty of members join for matched work and never bring an opportunity of their own.
Is there a minimum experience level?
In practice, around four years of production experience. Below that the matching pipeline rarely has work that fits.
Request an invite
Tell us what you build, where you work and what you are certified in. If there is a fit you will hear from a person, not an autoresponder.
Joining is free. It always will be. Engineers are never charged to be matched or to receive benefits.