My professional role
Senior Software Engineer
Who I am as an engineer, and what the work actually looks like. It splits roughly in half: setting technical direction, and staying close enough to the code to keep the bar high — because the moment you stop writing it, you start losing the feel for it. Below: what I own, a typical day, and the hard and soft skills behind it.
- 01
Technical direction
I help drive the modernization strategy across the connected-care portfolio — what migrates, in what order, and how to keep every app shippable along the way — and I back my calls with working code, not slides.
- 02
The .NET 10 migration
I work at the core of the incremental, app-by-app move off end-of-life runtimes (.NET Framework 4.8, .NET Core 3) onto .NET 10 — prioritized by risk and business value, without ever freezing delivery.
- 03
Innovation initiatives
I pitch, prototype and champion new concepts — the latest, a patient- and family-facing addition to the services catalog, was voted #1 in the innovation sprint, and I facilitated the innovation days where a 9-person team explored it.
- 04
Architecture & code quality
I weigh in on the architecture calls, review PRs with intent, and keep the bar on clean, well-tested, maintainable code.
- 05
Mentoring & influence
I mentor engineers on the team and move initiatives forward by selling ideas internally and building consensus, rather than relying on a mandate.
- 06
AI-augmented delivery
I fold AI tooling and agents into the workflow to move faster — delegating the mechanical, then reviewing and refactoring what comes back, so speed never costs us the fundamentals.
Not a clock — a rhythm. The shape of a typical day.
- Start of day
Triage across timezones
I catch up on async threads with the UK team, sweep the open PRs, and decide where my focus goes today — usually one deep-work block and whatever the team needs unblocked.
- Deep work
On the migration
A long, heads-down block on the .NET 10 migration: lifting an app off legacy, untangling dependencies, and keeping it green and shippable the whole way. This is the work that needs uninterrupted hours.
- The team
Pair, unblock, share
Time with teammates — pairing when something is genuinely gnarly, weighing in on an architecture question, running a knowledge-transfer session or helping someone new find their feet. On innovation days, this is where the catalog concept moves forward.
- Craft
Review and refactor
Code review with intent — not rubber-stamping — refactoring, and making sure the tests carry their weight. Senior does not mean stepping away from the keyboard; I keep my hands in the code on purpose.
- Wind-down
AI in the loop
I lean on AI agents for the mechanical stretches, then review and reshape what they produce. The bet is simple: amplify craftsmanship, don’t outsource it.
The toolbox. The full, interlinked map lives at /knowledge.
-
Languages & platforms
-
Web & mobile
-
Architecture
-
Data
-
Cloud & delivery
-
AI-augmented engineering
How I work with people and problems — and the part that doesn't show in a stack list.
-
Technical leadership
I lead through initiative rather than title — pitching concepts, prototyping them, and facilitating the innovation days where a 9-person team took the latest one forward.
-
Influence without authority
I move initiatives forward by pitching, prototyping and building consensus. The latest catalog concept started as an idea I sold internally, with no mandate to build it.
-
Client & stakeholder communication
Years of requirements gathering, functional analysis and validation directly with clients — closing the gap between what was meant and what gets built.
-
Mentoring
I help engineers grow through intentional code review and pairing — raising the bar without gatekeeping.
-
Ownership & initiative
I take problems end-to-end and push for the right thing even when nobody asked me to.
-
Continuous learning
I treat the craft like a language — practise it daily so fluency never fades — and stay ahead of where the industry is moving, AI included.