Building payment products at Snapp
At Snapp, I worked as a Senior Software Engineer on backend systems and products in the fintech part of the business. My work included starting Instant Cash Out, Passban and an internal ERP product, alongside the move from a legacy application to Go microservices.
These projects connected engineering with three practical needs: access to driver earnings, management of passenger debt and less manual work for the fintech team.
Turning payment needs into products
I initiated Instant Cash Out, which let drivers withdraw their earnings automatically. It was a product change with a direct benefit for the people using the platform. The goal was to make access to earned income easier, with driver satisfaction as an important part of the outcome.
I also initiated Passban to address passenger debt. That was a different part of the payment experience, concerned with outstanding balances rather than driver withdrawals.
The ERP product focused on the people running fintech operations. It reduced manual processes within the team. Together, these projects covered both the visible payment experience and the operational work needed behind it.
Improving the backend underneath
Alongside the product work, I helped rebuild the platform around Go microservices and worked on concurrency problems in the existing software. The challenge included making the backend respond efficiently while handling work that happened at the same time.
This involved refactoring the legacy application and fixing issues with concurrent execution. Separating the system into services and improving how those services performed were both part of the work. Fixing concurrency issues improved response times by up to 50%.
The technology involved
The stack in this role included Go and PHP, with gRPC and REST for service interfaces. Kafka and NATS supported messaging, while Redis, MySQL and PostgreSQL were part of the data stack. We also worked with Docker, Kubernetes and OpenShift.
Observability was another part of the environment, including Grafana, Prometheus and Jaeger. Visibility into service behaviour matters when the engineering work spans performance, concurrency and several connected services.
What the work achieved
The outcomes included automated access to driver earnings, a product for handling passenger debt and fewer manual processes in fintech operations. The backend work also delivered a measurable improvement in response times.
My contribution combined product initiative with implementation. I helped turn problems in the payment experience into products, while also working on the architecture and performance of the software supporting them.
More on this role in my résumé.