Backend

GraphQL

The client describes exactly what it needs

01 — Mastery

Mastery and experience

Self-assessment grounded in projects shipped to production and continuous learning.

02 — Playground

Where GraphQL delivers the most value in my work.

Multi-source aggregation APIs
A use case proven on projects shipped to production.
Secure by default
Authentication, fine-grained permissions and systematic input validation.
Observability
Structured logs, metrics and alerts: understanding production before the incident.
Reliable integrations
Idempotent webhooks, retries and tested contracts with third-party services.
Domain modelling
Clear module boundaries so the system evolves without breaking everything.

03 — Proof

Products shipped to production, where GraphQL plays a central role.

05 — Ecosystem

The building blocks I pair with GraphQL most often.

Let's talk about your product: I design and build web and mobile experiences end to end, from design system to production.