Symfony and API development for teams that need it to hold

Most API work fails slowly. The first version ships, then every new consumer needs a special case, the contract drifts from the documentation, and two years later nobody can change an endpoint without breaking something they cannot name.

I have spent fifteen years on the other end of that, and the work I do now is mostly about not arriving there.

What this looks like

• API design and implementation in Symfony and API Platform — resources, serialization groups, versioning, pagination, and error semantics that a client developer can actually predict.
• Third-party and ERP integration, including the unglamorous parts: retries, idempotency, partial failure, and reconciling data models that were never meant to meet.
• Search — Elasticsearch integration where relevance and speed both matter.
• Headless backends for React and other front ends, where the API contract is the product surface rather than an implementation detail.
• Test coverage that is load-bearing, not decorative. PHPUnit for domain and API behaviour, so the contract is enforced by something other than memory.

How I work

I prefer to start with the seams — where your system meets other systems, and where it will need to change. That usually surfaces the real constraint faster than a full audit, and it means the first thing I ship is something you can use.

Engagements are typically part-time and remote, running alongside your team rather than around it.