Product Engineer (PHP) - Commerce

FTMO · Prague office · Posted Oct 27, 2026


Transparency

Stale

Online for 3 weeks and never reposted. The first wave of applicants is in, so a reply is less likely. Apply if it's a strong fit.

First seen
Oct 28, 2026
Offered for
24 days

Overview

Category
Software engineering
Employment type
Permanent
Workplace type
On-site
Country
Czechia
Seniority
Senior
Schedule
Full time
Salary
Not listed

Key skills

PHP and Symfony Development
Design, implement, and ship production‑grade PHP services using Symfony and related tools.
Payment and PSP Integration
Build and maintain secure payment flows and integrate with payment service providers.
Static Analysis and Quality Gates
Create and enforce PHPStan rules, schema‑checked SQL, and CI checks to ensure code safety.
Event‑Driven Architecture
Develop and operate Kafka‑based event streams for real‑time commerce processes.
Observability and Incident Automation
Implement OpenTelemetry, Prometheus, Sentry alerts and runbooks to monitor and remediate issues.
AI‑Assisted Coding Agents
Leverage Claude‑coded agents for code generation, review, and release while guiding their output.

Key phrases

  • PHP 8
  • Symfony
  • Payments
  • PSP integrations
  • Kafka
  • event-driven architecture
  • static analysis rules
  • PHPStan (strict + custom rules)
  • CI checks
  • agent skills
  • internal CLIs
  • OpenTelemetry
  • Prometheus
  • Sentry
  • GitLab CI/CD

From the posting

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

Why join the FTMO team?

  • We are a Czech fintech that, since 2015, has grown from an idea into a global project. 🚀

  • 300+ amazing teammates. We’re a great team who learn from each other every day.🤜🤛

  • How do we work? We focus on meaningful work and open communication, while only adopting processes that make our lives easier.

  • Prague, Národní třída. Enjoy our modern offices at the Quadrio shopping center, offering beautiful views and excellent accessibility.

  • What if I don’t trade? No worries. We’ll show you what our product is all about and introduce you to the basics of trading.

  • Free fruit, snacks, and coffee are always within reach in the office.

  • How do we promote strong relationships and well-being? Company cottage, team building events, and running club.

  • Flexible hybrid model. We prefer collaborating in person to keep the team spirit high, but we offer the flexibility you need to stay balanced.

*The benefits mentioned above apply to FTMO on-site employees in our Prague office.

More jobs at FTMO

AI Engineer

FTMO · 6 days ago | Prague office | On-site · Staff · Full time

Create CV

Product Engineer (Python) - Trading Systems

FTMO · 6 days ago | Prague office | On-site · Mid level · Full time

Create CV

Product Engineer (Python) - Funding / Onboarding

FTMO · Last week | Prague office | On-site · Senior · Full time

Create CV

Product Engineer (Node.js) - Trading Platforms

FTMO · Last week | Prague office | On-site · Senior · Full time

Create CV

Product Engineer (Java)

FTMO · Last week | Prague office | On-site · Senior · Full time

Create CV
See all 40 jobs at FTMO