Webiny is a CMS you deploy into your own AWS account, so a Webiny developer needs to be a TypeScript engineer and a cloud engineer at once. Companies hire one to model content, write extensions, set up infrastructure as code, or run a multi-tenant SaaS product on the platform. As of October 2026, webiny.com describes it as open source and AWS native, available self-hosted or managed, with an MCP server for AI-assisted extension.
Work you can hand to a Webiny developer
- Content models in the Headless CMS app, with field level permissions and localization.
- Extensions for the admin app and the API, written in TypeScript against Webiny’s extension points.
- Deployment: infrastructure as code with Pulumi, separate dev, staging and production environments, and a CI pipeline.
- A Next.js or Astro frontend that reads the GraphQL API, with preview and cache invalidation.
- Tenant isolation and per-tenant content for SaaS products.
- Loading content from an old CMS by script, with redirects.
Vetting: serverless skills first, CMS skills second
Most Webiny trouble is AWS trouble, so the interview starts there.
- IAM and accounts. How would they structure accounts and roles so a deploy cannot touch production by accident?
- Cold starts and timeouts. What do they measure on Lambda, and what do they change when a query is slow?
- Cost visibility. Do they set spend alerts and read the bill, or discover it later?
- GraphQL discipline. Query depth, caching and what the frontend asks for.
- Extension upgrades. How do custom plugins survive a Webiny version upgrade?
A candidate with CMS experience but no AWS time does not pass, and neither does the reverse. We also ask for one deployment they broke and how they found the cause.
The first weeks
Before writing code, the developer agrees with your cloud team on the account layout, regions and who holds deploy access. A sandbox environment goes up in the first week, so everyone sees the real deploy time and cost of the stack instead of an estimate. That number often changes how the team plans environments. Week two delivers a content model change or small extension through the pipeline. The remaining weeks go to the larger task, with monitoring for Lambda errors and latency in place before launch.
Engagement models
One dedicated developer works when your own cloud engineer reviews the infrastructure. If you have no one in that seat, ask for a dedicated team that includes it, together with frontend and QA. IT staff augmentation covers short capacity gaps. Rates range from $50 to $150 per hour across roles and seniority.
When you need the whole build
Our Webiny development services page explains who the platform suits, what it costs to own and when we pick another CMS. For other platforms see headless CMS developers.
