Job description About the work O3 World is a Philadelphia-based digital consultancy.

We build and support content platforms for clients across enterprise B2B, nonprofit, and commercial sectors. A growing share of that work is headless: Sanity for content, Next.js for the front end.

We are adding contract capacity for a heavy period of Sanity work.

That includes a large Umbraco-to-Sanity CMS migration, ongoing feature development on an existing Sanity and Next.js platform, and post-launch support across several retainer clients.

You would work alongside our staff engineers rather than in isolation.

This is hands-on delivery work with real deadlines and real clients.

It is not a greenfield architecture role.

We build with AI agents as a normal part of the workflow, not as an experiment.

We expect the developers we bring on to move faster because of it.

If your process is entirely manual, this is not the right fit.

Please note: This is a near-term project need.

Candidates should be readily available to interview and onboard quickly if selected.

The anticipated commitment is 30–40 hours/week for an initial 3-month contract, with potential to extend.

What you would actually do Design and implement Sanity schemas: document types, objects, references, and Studio configuration Build Next.js front ends against those schemas, including GROQ queries, caching, and on-demand revalidation Write and run content migration pipelines that pull from legacy CMS platforms and load into Sanity, including HTML to Portable Text conversion Work against content models you did not design, including schemas produced by other agencies, and identify gaps between what exists and what a given page template needs Build and maintain redirect maps for large-scale migrations Implement components from Figma designs to a production standard, including responsive behavior and accessibility Use coding agents to accelerate the repetitive parts of this work: component scaffolding, schema and type generation,



transform scripts, test coverage Set up the context that makes agents useful on a given codebase, including project instruction files, conventions, and reusable prompts other developers on the team can pick up Participate in code review, sprint ceremonies, and client-facing technical conversations when useful Required Production experience with Sanity, specifically schema design and Studio work, not just querying an existing dataset Strong Next.js, including the App Router, server components, and data fetching patterns Solid Type

Script and React Experience with content migrations from a legacy CMS.

Word

Press, Drupal, Umbraco, Craft, Contentful, or similar.

We care that you have moved real content at volume, not which platform it came from.

Comfort writing throwaway scripts to extract, transform, and load data, and the discipline to make those scripts re-runnable Ability to read a Figma file and implement it faithfully without needing every state specified Clear written communication.

Most of our coordination is asynchronous.

Agentic development, as a working practice We are specific about this because it is a real requirement, not a nice-to-have: Daily working use of a coding agent such as Claude Code, Cursor, Codex, or similar, on production codebases Ability to break a task down so an agent can actually complete it, and judgment about which tasks are worth handing over at all Comfort setting up project context so agents produce work that matches our conventions instead of generic output A verification habit.

On a migration touching a thousand pages,



the question is not whether the agent wrote a transform, it is how you know the transform was correct across every page.

If you cannot describe how you check agent output at volume, this role will be frustrating for both of us.

Honest sense of where agents fail.

Content modeling, ambiguous requirements, and anything requiring taste still need a person.

Strongly preferred Portable Text conversion experience, especially handling embedded media, inline links, and tables from legacy rich text fields Accessibility fluency at a WCAG 2.1 AA level, applied in practice rather than as a checklist at the end Playwright or similar end-to-end testing, particularly regression suites that validate content and routing after a migration Experience on agency or consultancy teams, working across more than one client at a time Familiarity with .NET or Umbraco specifically, on the extraction side Experience building agent-assisted pipelines for content classification and mapping, not just code generation Not required Deep design skills.

We have designers.

Backend or infrastructure specialization.

Familiarity with deployment platforms is useful, but we are not hiring for Dev

Ops.

Domain knowledge in any particular client vertical.

How we work Weekly sprint cadence with a standup and a demo Code review on everything We prefer systemic fixes over one-off patches, and we would rather you flag a structural problem early than route around it Agent-generated code goes through the same review bar as anything else.

You own what you ship regardless of what wrote the first draft.

Direct, honest communication.

If an estimate is wrong, say so while it still matters.

Company Braintrust is a global talent network that connects top independent professionals with leading companies for high-quality, adaptable work.

We help organizations hire skilled talent faster while giving professionals access to vetted opportunities with innovative teams.

📌 Senior Sanity Next.js Developer (Remote - LATAM) (México)
🏢 Braintrust
📍 México