After thirteen years in commercial software I still describe myself the same way: an engineer who can draw the architecture, an engineering manager who can run the room, and a solution architect who can tie both to business reality. The through-line is not a title - it is how I move from ambiguous problem to shippable system without losing the thread.
Top to bottom, without losing the plot
I am comfortable from schema design and API contracts through production logs, deploy paths, and the conversation in a board meeting. That full-stack depth is deliberate: you cannot pinpoint a failure or defend an architecture if you have not recently touched the layer where it hurts. When pressure rises, my default is diagnosis first - narrow the blast radius, name the owning component, prove the fix against runtime evidence - then scale the answer into something the team can repeat.
Strong context switching is part of the job, not a boast about workload. Different clients, stacks, and time zones ask for different mental models; the skill is keeping each boundary clean so work in one lane does not contaminate another. I treat that as architecture for attention: explicit ownership, durable notes, and handoffs that the next session can read cold.
Leadership that stays technical
I have led engineering groups of roughly fifteen people and delivered on global programmes from discovery through production. At that scale the work is part direction, part operating rhythm: who owns which surface, how incidents become standards, how executives hear truth without drowning in jargon. I mentor by building the map and scaffold, then handing off ownership where someone's domain knowledge is stronger than mine - always with verification and risk visible, not buried in optimism.
Stakeholder and shareholder reporting, recruitment design, and cross-team coordination sit in the same picture as code review and architecture review. The goal is not to manage away from engineering but to make engineering legible enough that decisions stick after the meeting ends.
For applied AI, guardrails, and the agent session loop, see AI.