I’ve spent my career on one question: a customer reports a problem — what happens next? For over ten years, across fintech and enterprise platforms, the answer has been the same job in different costumes: investigate honestly, communicate clearly, fix the cause, and make sure the second occurrence never happens.
The thread
I started on service desks and software support for enterprise implementations — owning escalations end-to-end, writing the support materials, sitting with users during go-lives. That’s where I learned that customers rarely leave over a bug; they leave over silence. Ownership and proactive communication are retention features.
I then moved into QA at AZA Finance, a payments and FX platform — where “the customer hit a bug” has real consequences — and built the prevention side: root-cause analysis frameworks, automated regression and API validation in CI/CD, and a 30% reduction in production bug leakage. Currently at Cellulant, I lead quality initiatives across backend services, APIs, mobile apps, and pipelines, and I’m the bridge between support and engineering: customer-reported issues in, preventive safeguards out.
My title says QA, but the work has been about converting customer pain into prevention — which is retention work under a different name. That’s the job I’m looking to do as my primary focus: the technical face of the product for customers, solving real problems myself, and making sure no customer is ever surprised by an issue.
What I work with
- Technical: Linux/Unix, Bash, Python, Git, REST APIs, Postman, Rest Assured
- Automation & CI/CD: Cypress, Playwright, k6, GitHub Actions, Jenkins
- Observability: Grafana, Datadog, Sentry, structured logging
- Support & collaboration: Jira, Confluence, TestRail, ClickUp
- Methods: RCA frameworks, test pyramid design, Agile/Scrum, incident prevention
CV
Download CV — Customer Success positioning (PDF)
Download CV — QA positioning (PDF)
Beyond work
I keep a hand in building for the web — this site is self-managed, and I rebuilt my portfolio after studying how sites like PostHog’s are put together. Outside work I race go-karts on weekends — a hobby that, like debugging, rewards staying calm and paying attention to small details under pressure. I’m also a casual Formula 1 fan, mostly for the strategy.