Senior Sanity + Next.js Developer (LATAM)

What You'll Do9

• Design Sanity schemas, covering document types, objects, references, and Studio configuration.
• Build Next.js front ends against those schemas with GROQ queries, caching, and on-demand revalidation.
• Write migration pipelines that extract content from legacy CMS platforms and load it into Sanity, converting HTML into Portable Text.
• Read content models built by other agencies, spot gaps between the schema and what a page template needs, then close them.
• Maintain redirect maps for migrations that span large sites.
• Turn Figma designs into production components with responsive behavior and accessibility in place.
• Use coding agents for scaffolding, schema and type generation, transform scripts, and test coverage.
• Set up project instruction files, conventions, and reusable prompts so agents produce work that matches team standards.
• Take part in code review, sprint ceremonies, and client technical calls when they help.

Requirements10

• Production Sanity work that includes schema design and Studio configuration, not only querying someone else's dataset.
• Strong Next.js skills with the App Router, server components, and data fetching patterns.
• Solid TypeScript and React.
• Content migration experience from a legacy CMS such as WordPress, Drupal, Umbraco, Craft, or Contentful, with real content moved at volume.
• Comfort writing throwaway extract, transform, load scripts, plus the discipline to make them re-runnable.
• Ability to implement a Figma file to spec without every state spelled out.
• Clear written communication, since most coordination runs through written channels.
• Daily use of a coding agent such as Claude Code, Cursor, or Codex on production codebases.
• Skill at breaking a task down so an agent can finish it, plus judgment on which tasks are worth handing over.
• A verification habit. On a thousand-page migration, you can explain how you confirm the transform is correct on every page.

Preferred Qualifications6

• Portable Text conversion, including embedded media, inline links, and tables from legacy rich text fields
• WCAG 2.1 AA accessibility applied in practice
• Playwright or similar end-to-end testing, especially regression suites that check content and routing after a migration
• Agency or consultancy background with several clients at once
• .NET or Umbraco familiarity on the extraction side
• Agent-assisted pipelines for content classification and mapping

Who Should Apply

Senior developers who have shipped Sanity schemas and Next.js front ends in production and moved large content sets off a legacy CMS fit this contract well. You already run coding agents in your daily work and can describe how you check their output across thousands of pages. A near-term start matters, since this need is close at hand.

Salary Insight