Looking for a senior Directus developer for a headless hospitality platform with Next.js, booking, integrations, and guest app automation.

Job Board
, , , ,
1

Role title

Senior Directus Developer / Senior Full Stack Developer

Skills/experience required and desired

We are looking for a senior developer with proven Directus experience in production.

Required:

  • Strong hands-on experience with Directus.

  • Good knowledge of collections, relations, permissions, roles, and ACLs.

  • Experience with REST API, GraphQL, and the Directus SDK.

  • Ability to build Flows, webhooks, and automations.

  • Experience with headless / API-first architectures.

  • Strong relational database and data modeling skills.

Desired:

  • Experience with Next.js or similar modern frontend frameworks.

  • Experience in hospitality, booking systems, PMS, or channel managers.

  • White-label or multi-tenant architecture experience.

  • Experience with Stripe or custom checkout flows.

  • Knowledge of logging, audit trails, and application security.

Employment details

Freelance, project-based, remote.
Potential for continued collaboration on future phases.

Compensation details

Open, depending on experience and scope.
Please include your rate expectations and an estimate for the first phase.

Job description

We are building a headless digital platform in the hospitality space. The stack includes Directus as the central data platform, Next.js for the public website, a custom booking engine, integrations with PMS / channel manager systems, and a guest app / web app for guest experience and automations.

We are looking for someone who can think in terms of architecture, scalability, security, and maintainability, not just implementation.

Please apply only if you have real, demonstrable Directus experience.

Note:
This is an early scouting phase. Shortlisting and selection are expected to begin around September–October 2026.

2

Hi @mauroman, interested — this is my main area of work.

I’ve been building Directus in production for 2+ years, have merged contributions to Directus core (v11.x), and have three published Marketplace extensions: khanahmad4527 (Ahmad Khan) · GitHub

Closest relevant work: a 7-language e-commerce platform on Directus + Remix with Stripe checkout, and a community platform on Directus with real-time messaging and Stripe subscriptions. Frontend side I work in React Router 7 / Remix rather than Next.js, but it’s the same data-loading model.

Happy to send rate expectations and a phase-one scope directly — I’d suggest starting with a short paid architecture sprint before anyone estimates a build, since the booking engine needs its transaction and locking model settled first.

No rush given your September–October timeline.

— Ahmad

3

Hi — this is a close match for what I do, and I’d like to be considered.

I’m a senior full-stack engineer, front-end leaning, with eleven years at Okam, a headless development agency in Montreal, where I lead builds that pair Directus with Next.js front ends. Relevant to your stack:

  • Directus: collections and relations, roles, permissions and access control, Flows, webhooks and automations, custom extensions, and REST/GraphQL APIs through the Directus SDK, feeding web and mobile clients.
  • Next.js: my primary front-end framework, with design systems, performance work and EN/FR localization.
  • Booking and scheduling: lead engineer on the Canadian Olympic Committee’s Games Portal (equipment booking, travel and scheduling for athletes, plus the internal management tool and admin backend; 90% adoption in its first month), and on HiSports, a league-management platform with referee booking and scheduling across 131 associations, later acquired by Spordle.
  • Architecture: headless, monorepo-based delivery (Turborepo, shared packages, Storybook design systems) designed for scale and long-term maintainability.

Case studies: okam.ca/work/coc · okam.ca/work/hisports

I’m happy to send my rate and a phase-one estimate privately. For the estimate, I’d want a short call about the booking engine and the PMS/channel-manager integrations first, since those drive most of the effort. Alternatively, I can scope it as a short paid discovery phase.

Available immediately, working remotely from Florida (US Eastern).

max.hilland@gmail.com · Max Hilland - HZM | LinkedIn

Max