ENGINEERING LEADER · ADVISOR · SKOPJE, CET
I've spent 19 years building and running engineering teams in fintech, healthcare and e-commerce, as CTO, CEO and engineering director. I help founders and engineering leaders bring AI into how their teams build software, without losing control of quality, security or accountability.
19+
years leading engineering
100+
engineers led across 3 countries as CTO
5
leadership levels, from team lead to CEO
PhD
candidate in generative AI safety and ethics
// HOW I HELP
I work with founders, engineering leaders, and boards on the parts of technology that are hardest to get right.
Getting AI tools into daily work in a way that actually helps people. Where AI saves time, where humans stay accountable, and what guardrails you need — especially if you work in a regulated space. This is built on my GEF-SDLC framework and PhD research.
Going from a few engineers to a few dozen without losing speed or culture. Team structure, hiring, delivery rhythm, and the habits that keep people focused on outcomes, not just output.
Architecture, cloud migration on Azure or AWS, and CI/CD that holds up as you scale. I've led platform, data, and AI teams, and I know which shortcuts come back to bite you.
Build or buy, who to hire next, which vendor to trust, what goes on the roadmap. I also mentor first-time CTOs and engineering leads as they grow into the role. Sometimes you just need someone who has made these calls before and will tell you honestly what they think.
Helping boards and leadership teams ask better questions about technology. I bring an operator's view on AI risk, engineering health, and delivery, so the board can see what's really going on behind the status reports.
// WHAT I'M BUILDING
Practical software for small businesses. Focused tools that automate the repetitive 90% of the work and leave the human 10% to the owner, built transparently with AI and delivered in weeks.
// RESEARCH
A gated model for using generative AI responsibly at every stage of software delivery, built on transparency, interpretability and explainability. It comes from my PhD research and is in peer review.
Requirements
Design
Build
Test
Release
Operate
◆ = governance gate
Is it clear where AI was used?
Can the team understand what it produced?
Can a person explain and own the decision?
// EXPERIENCE
// The short version
Nineteen years in software: from writing code on a web team to CTO and CEO. Along the way I have run engineering organisations of 100+ people across three countries, and held every leadership level between team lead and chief executive.
// SELECTED ADVISORY
Engineering processes, AI strategy, senior advisor to the C-level team.
Mobile development strategy, team structure and hiring.
Migration to Microsoft Azure, and the team and process around it.
Set up the engineering team, process, hiring and technology strategy.
Technical vision and development method.
Engineering process and tools.
// TEACHING & EDUCATION
// CONTACT
If you're working out how AI fits into your engineering team, or your team is growing faster than its habits, write to me. I reply to every message.