Engineering
I design and build systems where architecture, reliability and scale matter. I care less about a single feature than about the infrastructure: what survives releases and what teams run on.
Most of my work is platform work. Internal tooling, feature flags, developer infrastructure, backend–frontend integration. This is code used not by end customers but by other engineers — which sets a different bar: predictability, observability, clear boundaries.
Lead fullstack engineer: I own the architecture and development of high-load banking services — backend and frontend, platform solutions and integrations.
I lead both the technical decisions and the team: setting engineering standards and working on reliability, performance and maintainability at a bank's scale.
- Architecture and fullstack development of banking services
- Technical leadership and engineering standards
- High load, reliability, scale
I developed and extended Unleash — an open-source feature-flag platform. I owned feature development and engineering decisions as tech lead.
Feature flags are more than switches. They are a control layer over what a product shows, and to whom: gradual rollouts, targeting, experiments. I built tooling that makes this layer transparent and safe for teams.
- Platform feature development
- Technical leadership and architecture
- Tooling for gradual rollouts and targeting
Introduced A/B testing and CI/CD into team processes. Ran TypeScript and JavaScript assessments — evaluating engineering competency.
- Introduced A/B testing
- Set up CI/CD
- TypeScript / JavaScript assessments
Built a portal serving more than 40,000 users: high-load interfaces and real scale.
- High-load interfaces
- Scale of 40,000+ users
Product development: features, interfaces and iterations close to users and business goals.
- Product interfaces
- Iterative feature development
Learning and side projects — for context, not as primary work.