My route into technology wasn't a straight line — and that's exactly what makes me useful on a delivery team. It runs in five chapters, and the timeline alongside follows the same arc.

Foundations. I started in the sciences in Ukraine — a degree in chemistry and environmental safety, then philology. Two disciplines that taught me the same lesson from opposite directions: break a complex system into its parts, understand how they interact, then communicate it so anyone can act on it. That's systems analysis before it had a job title.

The industry years. A decade in heavy and chemical industry followed — automated process control systems, electrical engineering, certification and compliance. Real machinery, real consequences, and the habit of writing specifications precise enough that someone else could build from them.

Into software delivery. From 2017 I moved into product, analysis and project leadership — across Ukraine, Estonia and US-facing teams. The work that found me again and again was the same: products that had stalled, teams that had lost alignment, requirements no one had written down. I became the person who maps the mess and gets it moving — most visibly on a logistics platform that had slipped twelve months and shipped its MVP six months after I took it on.

The UK chapter. Today I'm based in Bristol: an Advanced Diploma (Honours) in IT Systems Analysis & Design from Oxford, an MSc in ethical hacking and cybersecurity in progress, and an AI-assisted delivery practice running alongside — 30+ security audits, an ERP integration across Dynamics 365 and Sage 200, and a multi-tenant SaaS shipped to production.

Alongside the work, I give time back — humanitarian coordination for Ukrainian families, Oxfam in Bristol, and digital support for an environmental charity in Taunton. The throughline hasn't changed since the lab: curiosity, structure, and a stubborn focus on shipping.