Teams hire a Ghost developer for three jobs: a custom theme that keeps Ghost’s membership and newsletter features, a decoupled Next.js or Astro site that reads Ghost as a content store, or a move off WordPress that must not lose rankings. We supply engineers who have shipped each of those, one at a time or as a small team.
What does a Ghost developer actually do?
- Builds and maintains Handlebars themes, including custom collections and URL patterns set in
routes.yaml. - Builds a decoupled frontend on the Content API, with webhooks that trigger rebuilds or revalidation and a preview route for drafts.
- Sets up tiers, Stripe, gated content and the signup flow, then tests the paywall on real devices.
- Configures newsletters: sending domain authentication, segments and the sign-up form.
- Connects analytics, CRM and automation tools through the Admin API and webhooks.
- Imports posts, authors, tags and images from the old platform and ships a redirect map.
What we check before we put someone forward
Ghost looks simple, and the mistakes show up late. We ask candidates how they would handle each of these:
- Which parts of membership survive when the frontend is decoupled. Login, paywall behaviour and preview have to be rebuilt, and a candidate should say so without prompting.
- Why a Content API key in browser code is acceptable for public posts but never for anything admin-level.
- How a theme upgrade is tested against Ghost’s own theme validator before it reaches production.
- What breaks in a content import: slugs that collide, image paths that point at the old host, cards that do not map.
- How a self-hosted instance is backed up, updated and monitored, including mail delivery.
We also read code. A candidate who has only restyled a stock theme does not pass for a decoupled project.
The first weeks on a Ghost engagement
In the first week the developer gets repository and staging access, reads the theme or frontend, and lists what runs on Ghost’s built-in features versus custom code. By the end of week two the first small change is in review: a template fix, a route, a webhook handler. Weeks three and four usually take on the larger item that justified hiring, such as the tier redesign or the move to a decoupled frontend, with a staging copy of real posts and a test Stripe account for editors to try.
How can you engage the developer?
Most Ghost jobs start with one dedicated developer inside your sprint. If the publication also needs frontend and design hands for a quarter, IT staff augmentation adds them. A larger relaunch with delivery management is a job for a dedicated team. Rates across roles and seniority run from $50 to $150 per hour, and we quote after an intro call about the work.
When a project fits better than a hire
If you need the architecture decision made for you (theme or decoupled, Ghost or another platform), see our Ghost development services. For other platforms, browse all headless CMS developers.
