6 years in fintech · quality strategy + production code
🟢 Open to backend quality & engineering roles. Remote
I set up QA from scratch on a fintech platform, then crossed over to writing the backend — and kept both skill sets. Six years across investments, origination/KYC, payments, and order management. Working both sides taught me where these systems break and how to keep them from breaking.
Production Go lives in my employer's private repos; the public Go here is practice and coursework. The test frameworks below are the part of my work I can show.
Backend: Go, gRPC, REST, Kafka, Camunda
Data: PostgreSQL, MongoDB
Infrastructure: Docker, Kubernetes
Also: Java, Kotlin, Spring
rangiffler - microservices travel social network. Spring Boot, gRPC, Kafka, OAuth2, MySQL, a React frontend, plus a full E2E suite.
thank-go-practice - my solutions for the Stepik "Thank Go!" course: fundamentals, concurrency, the standard library.
tcp-chat-java - multi-client TCP chat in plain Java. Sockets, a small wire protocol, in-memory history.
alfabank-journey-of-the-day-autotests - UI, API and DB tests for a fintech payment app, running against both MySQL and PostgreSQL. Selenide, REST-Assured, JUnit 5, Allure, Docker Compose.
vivid-ui-tests - end-to-end UI tests for the Vivid Money web app. Page Object Model, parallel runs, local or Selenoid grid, Allure with video and logs, Jenkins, Telegram.
wikipedia-android-ui-tests - mobile UI tests for the Wikipedia Android app. The same code runs on BrowserStack, an emulator, or a real device. Appium, Selenide, JUnit, Allure, Jenkins.
spring-api-testing-demo - Spring Boot books/authors REST service with a black-box REST-Assured suite. OpenAPI 3.1, Swagger, Allure.
rest-api-test-framework - REST API tests with contract-first JSON Schema validation and data-driven cases. REST-Assured, Allure, Swagger, Jenkins, Telegram.


