Lead Software Engineer
- Leading engineering on enterprise client platforms — including a business-critical risk management platform in global commodities trading.
- Driving adoption of AI-assisted development and LLM-powered features across the team.
> Lead Software Engineer building
Eight years turning hard technical problems into the systems businesses run on — from core platforms and integrations to AI-powered products that people actually use.
I'm a software engineer who cares less about the code itself and more about what it changes for a business — fewer manual steps, faster decisions, and systems a team can rely on every day.
Over eight years across six companies — most recently as a Lead Engineer at EPAM Systems — I've built software for insurance, healthcare, e-commerce, B2B and enterprise risk teams, shipped 10+ products and platforms and led teams of up to eight engineers.
I've also been on the other side of the table: I founded Salymed, a healthcare SaaS, and learned first-hand what it takes to turn a real problem into a product people use.
Today most of my attention goes to AI engineering: putting LLMs to work inside real business workflows — reliably, measurably, and not as demos.
By the numbers
A business-critical risk management platform for a global commodities trading company, used by traders, risk managers and credit analysts. I lead the team of 8 moving it step by step from legacy code to microservices, and the integrations with credit-rating and market-data providers such as Moody's.
A healthcare SaaS I founded and built on my own: customer interviews, product decisions, architecture, development and launch. I wound it down in 2026, and what it taught me about building the right thing now shapes how I work.
Moved a CRM module out of a monolith into microservices built with CQRS and Clean Architecture, talking over RabbitMQ and Kafka, containerised and deployed on Kubernetes with Jenkins CI/CD.
A document-style product page assembled on the fly from API data, so each customer gets a tailored, detailed product sheet generated from live data.
A microservices platform on Azure for managing small and mid-sized business insurance products, with APIs connecting it to the company's internal systems.
An ERP system and the REST APIs behind several mobile apps, including a sports social app. This is where I learned to own a product all the way to its deployment.
LLM-powered features — retrieval, agents and automation — built into real business workflows and shipped as dependable product, not prototypes.
Tools
Certified
Education
Research · 2026
Across the products I've built, the same pattern keeps showing up: the software is rarely the hard part — the workflow around it is.
So I'm spending time with operators, team leads and founders to understand where work still runs on spreadsheets, inboxes and manual hand-offs — and where software, and AI, could genuinely help.
Questions I'm asking
If your team deals with this, I'd value 20 minutes of your perspective.
Share your perspectiveA tiny shell that knows about me. Try help, impact, projects or research.
A hard problem, a project, or 20 minutes to compare notes?
Search for a command to run...