HOW I LEAD
Predictable delivery, teams people trust and engineers who grow.
My leadership style is rooted in psychological safety, trust, and autonomy: give people clarity and room to own their work, and they'll surprise you.
WHAT DRIVES ME
Integrity, work ethic, and doing things the right way.
Outside work I do endurance sports and volunteer. Both come down to the same things: integrity, work ethic, and doing things the right way and in the most optimal way, with no corner-cutting and no wasted effort.
That philosophy carries straight into my professional work: doing the right thing, the right way, and directing a team's effort where it has the most impact.
Delivery
Predictable delivery, with clear visibility for stakeholders.
I own delivery end to end across the product lifecycle, for customer-facing products and internal platforms. Together with product, tech and design, I manage the backlog and priorities, and I set up the development and service desk processes and the planning cadences that give stakeholders visibility of progress.
Product metrics and delivery dashboards guide prioritization and expose bottlenecks. I define the roadmap together with product and work to stay aligned. When needed, I push back to protect the engineers and keep commitments realistic.
Cross-functional leadership
Engineering, product and the business pulling in the same direction.
I work across engineering, product, operations and business stakeholders to keep dependencies visible and decisions moving, including for integrated systems that support financial reporting and core business operations. On company-wide initiatives I translate strategic objectives into structured plans, track progress, resolve cross-functional issues and make sure agreed actions are followed through.
People and growth
Teams people trust, and engineers who grow.
10/10
Trust, Workleap
9.8/10
Relationship with Manager, Workleap
People come first, because none of the rest of the work is possible without them. I build psychological safety in the team, and it shows in the Workleap metrics above.
I invest in growing the people I work with, through regular 1:1s, coaching and personalized development plans: one engineer moved from junior to mid-level and two from mid-level to senior, one of them growing into technical leadership on the team.
I take responsibility for team planning, onboarding, recruitment, budgeting and resource allocation while meeting delivery commitments, for teams of three to twelve people.
Mentoring beyond my team
A team lead I mentored for six months has since been promoted again.
A newly appointed team lead outside my team asked for help, and I mentored them formally for about six months. We met weekly, and every session had a clear plan and a practical assignment tied to their current work, such as reading on managing stress and change or on giving constructive feedback. I adapted my approach to how they work best, and they asked questions and completed every assignment.
Team practices on each product
Eficode Data Platform
We stabilized and documented the platform, then completed the technical handover to another team. I continued to manage it, and the handover expanded the resource pool and freed capacity for other strategic priorities.
Eficode Connectors
Ownership was split so that each connector had one main engineer and a second engineer in a supporting role. Once we scaled up, templates and shared ways of working let us launch new connectors quickly: each engineer took one, assessed its technical feasibility and then built the logic for extracting the data.
Eficode Journey
The team grew with the product: we started from a small prototype of reports and developed it into a full product. We maintained what we shipped, so the team also owned the entire infrastructure.
Clear ownership, so no single person was a bottleneck.
Technical judgment
Pragmatic technical decisions, with reliability and security in focus.
I stay close enough to the technology to mentor the team: guiding system design, managing technical debt and enabling pragmatic engineering decisions. I come from hands-on software engineering, full-stack and infrastructure, and I work with cloud platforms such as AWS and Azure from a management perspective. I focus on reliability, secure integrations and operational visibility, and I own the documentation for security audits.
AI in the SDLC
AI is a tool. Knowing where it fits in the process is the skill.
Understanding processes and systems is the core of my work. Across the software development lifecycle, I use AI where it fits the context, for research, automation and rapid prototyping, to speed up delivery and help the team build maturity in using it, so people can focus on higher-value thinking.
One example: unit and integration test suites that would have taken days were generated in minutes and reviewed by the engineers, so coverage grew quickly while their time went into design and problem-solving.
CONTACT
Let's talk about your engineering organisation.
Engineering leadership, delivery, or the operating model behind both: I'm happy to talk.