Teams hire a TinaCMS developer when they want editors to click on a page and type, while the content stays in Markdown, MDX or JSON files inside the Git repository. The work sits between a React front end and a content schema, and it goes wrong quickly when the person has only read the quickstart. We place engineers who have wired Tina to real components.
What does a TinaCMS developer build?
- The schema. Collections, fields and templates in code, designed so the files stay readable in a pull request.
- Visual editing. Click-to-edit connected to your actual React components, so the editor view matches production.
- The data layer. Queries through the GraphQL client Tina generates, with typed results in Next.js or Astro pages.
- Auth and hosting. TinaCloud for the backend, or a self-hosted backend with a database adapter and your own authentication.
- Draft and branch flow. Editors work on branches, and a change goes through review like any code change.
- Conversion. Existing posts and pages turned into Markdown or MDX with front matter intact.
What do we vet for?
Tina is a thin layer, so mistakes show up in the details. In a technical interview we look for:
- Schema discipline. A field renamed after launch breaks every file that used the old name. Candidates should plan how to migrate content when the schema changes.
- Rich text. Tina’s rich text can emit MDX. A good engineer maps each node to a component and decides which nodes editors may not use.
- Self-hosting limits. In a self-hosted setup the database is only an index and Git stays the source of truth. We check that the person understands which side owns what.
- Scale judgment. Git is a fine store for hundreds of pages and a poor one for huge record sets. We ask where they would stop.
What happens in weeks one to four?
The first week covers repository access, a read of the existing components and an agreed list of page types. The developer then ships one collection with working visual editing. Weeks two to four add the remaining templates, the branch and preview flow, and a walkthrough for editors. The first edit a marketer publishes without a developer is usually when the setup pays off.
How can we work together?
Most Tina work starts as a fixed-scope setup: schema, visual editing on the main templates and a handover. Once editors rely on it, schema changes and new components keep coming, which is when a dedicated developer or staff augmentation pays off. A site rebuild with design and content work can use a dedicated team. Hourly rates range from $50 to $150 across roles and seniority. If you self-host the backend, we also budget time for the database adapter and its upkeep.
When do you need more than one developer?
If you are choosing between editors, read our guide to the best Git-based headless CMS platforms. For a full project with audit, schema design and migration, see our TinaCMS development services. Tina sites usually run on Astro or Next.js, and other CMS skills are covered on the hire headless CMS developers page.
