Senior PHP Engineer, Commerce Team

About the role

We build the money side of FTMO: orders, payments, payouts, and the payment providers behind them. Every purchase goes through our code. A bad deploy here is not a broken button;, it is somebody's money, and the way we work reflects that.

We take coding agents seriously, not as an experiment or a shortcut. Most of our code is generated. Every change passes strict PHPStan with custom rules, schema-checked SQL, API breaking-change checks, AI review, and a human sign-off. Incidents went down while output went up. Secure enough for payments, fast enough to ship every week.

WHAT YOU WILL DO

- Own features end-to-end: understand the business need, design the domain and the API, build it with agents, ship it, watch it in production.

- Spend more time specifying, reviewing, and verifying than typing. Know where generated code tends to be wrong and look there first.

- Improve the guardrails, quality gates, and observability that keep the agents safe, and cut repeated operational work with runbooks, alerts, and automation.

- Review other people's work, generated or not, and mentor the engineers around you.

HOW WE WORK

- Weekly sprints. Small scope, real output, every week.

- The team owns its process and its planning. Nobody hands us a process, and no process stays unless it helps.

- Ownership is expected and rewarded. If you see a better way to build, test, ship, or run something, bring it. Good ideas get adopted on merit, not on seniority.

- Agile that works. We keep the daily, planning, and retro because they work for us. We drop ceremonies that do not.

WHO WE WANT

Seniority here means judgment and ownership, not years with a framework. The stack is secondary, and we teach it.

- Not a detractor, not a vibe coder. You use coding agents on production code today; you can say concretely where they helped and where they failed, and you stand behind what you ship, whether you or an agent wrote it.

- You know the difference between the perfect solution on paper and the one that ships. No three-day debates: pick the clean option that works and build it.

- Ownership: problems come with a proposed fix, status is always honest, and once the team decides, you execute.

- Appetite: you like a fast pace, you learn fast, and you ask for help early rather than stay blocked.

- You shipped, broke, and fixed real systems in production, ideally with real money in them. PHP and Symfony help; strong engineers from a similar stack pick them up fast.

NICE TO HAVE

- Payments, PSP integrations, or other regulated money flows.

- Kafka or event-driven architecture in production.

- Tooling you built for other engineers: static analysis rules, CI checks, agent skills, internal CLIs.

OUR STACK

PHP 8, Symfony · Python, TypeScript · MariaDB, Redis, Kafka · PHPStan (strict + custom rules), PHPUnit · GitLab CI/CD, Docker, Kubernetes on GCP · OpenTelemetry, Prometheus, Sentry · Claude Code and our own in-house agents for implementation, review, and release