Strapi Backend Developer

About the role

We are looking for a Strapi Backend Developer to help us design, extend, migrate, and stabilize modern CMS platforms. You will work on Strapi applications used by marketing teams, product teams, and enterprise clients that need clean content architecture, reliable APIs, permissions, integrations, and deployment workflows.

This role is backend-focused, but not isolated. You will collaborate with frontend developers, QA, project managers, and client-side teams to make sure the CMS is not only technically correct, but also useful for editors and maintainable for developers.

What you will work on

• Building and extending Strapi projects with custom APIs, plugins, lifecycle logic, and integrations
• Designing content models, roles, permissions, workflows, and localization setups
• Migrating clients from legacy CMSs to Strapi, including data modeling and content transfer
• Upgrading Strapi projects between major versions and improving existing implementations
• Connecting Strapi with frontend apps, search, analytics, authentication, CRM, and third-party APIs
• Improving reliability, security, observability, and deployment quality across production systems

What we are looking for

You should have strong experience with Node.js, TypeScript, relational databases, and API design. Strapi experience is ideal, but we also value developers who have worked deeply with headless CMSs, NestJS, Express, PostgreSQL, GraphQL, REST, or complex backend integrations.

You think in systems. You care about content structure, naming, permissions, migrations, error handling, and operational clarity. You can read an existing implementation, identify the weak points, and propose a practical improvement path.

What you can expect

You will work in a team that treats Strapi as a core specialization, not as a side tool. We build enterprise-grade systems, rescue messy implementations, support long-term platforms, and contribute reusable ideas back into our own tooling and open-source ecosystem.

This role is a strong match for someone who enjoys backend architecture, CMS internals, structured content, and solving problems that sit between code, editors, integrations, and business operations.