— 01 —
Advisory
2–8 hours / week
Architecture review. ADRs on a roadmap. Second-opinion on a buy-vs-build call. Interview support for your senior hires.
Best whenyou have an instinct that something is off and need a fast calibration check.
§ 05 — Work with me
Two paths in.
One conversation.
Most of what I do falls into one of two shapes. Either an independent engagement where I take an idea through architecture, solution design, cloud infrastructure, and into production code — solo when the team is small, with a team when it's not. Or a senior architecture role inside a company building something I want to be inside.
I don't hand off blueprints and walk away. Architecture and implementation are the same conversation; I refuse to let them be different jobs.
§A — Engagements
I take a small number of independent engagements per quarter. Three shapes, increasing in commitment.
— 02 —
Solution Design
4–8 weeks · fixed scope
Bounded-context maps, service blueprints, event schemas, ADRs, POVs, POCs, vendor evaluations.
Best whenyou know what to build and need someone to hand the team a real blueprint plus the decisions behind it.
— 03 —
Embedded Lead
1–2 quarters · part- or full-time
Tech lead / architect role on a delivery — I own the design and supervise the build.
Best whenyou have a funded program but no senior architect on the team yet, and you want one for a fixed stretch.
Idea → production. End-to-end.
- — Architecture & solution design
- — Cloud infrastructure (GCP, AWS, Azure)
- — Distributed, event-driven, multi-tenant systems
- — Domain-driven design and bounded-context decomposition
- — Full-stack implementation when the team is lean
- — Delivery, deployment, and the on-call that follows
- — Modernization and digital transformation (legacy → modern)
- — AI engineering and AI-system integration
Where I'm not the right call
Pure mobile-app shops, pure data-science work, anything that needs a hands-on Kubernetes operator more than an architect. I'll tell you in the first call.
Industries: Public sector, FinTech & Wealth Management, product (SaaS, multi-tenant platforms, regulated B2B/B2C).
Engagement-shaped, not hourly. Rates discussed in the intro call — they reflect scope, urgency, and confidentiality, not seat-time. I work in EST and accommodate EU and Middle East time zones.
§B — Full-time roles
I'm currently open to senior, staff, and principal-level architecture roles. The bar I hold for myself is the bar I hold for the role.
Open to
- — Software / Solution Architect
- — Senior / Staff / Principal Architect
- — Lead Architect for a product or bounded program
- — Founding-engineer / founding-architect at funded early-stage companies
Not looking for
- — Pure people-management roles
- — Roles where the architect doesn't ship
- — “Architect” titles that are really tech-lead titles
- — Relocation to regions outside Europe or the Middle East
What I'm looking for
- — A team that takes architecture seriously enough to staff it, and small enough that I'm still close to the code.
- — A domain with real complexity — distributed, event-driven, multi-tenant, regulated, or all four.
- — A culture where architectural decisions are written down and revisited.
- — A founder, CTO, or VP of Engineering who's read at least one of the things I've written.
Where
Toronto, Ontario. Remote-first across Canada and the US. Open to physical relocation to Europe or the Middle East for the right role. Open to occasional travel.
Work status
Authorized to work in Canada. Open conversation about US work authorization for the right role.
Compensation
Discussed with the recruiter or hiring manager once we both know the scope of the role. I don't publish ranges.
For recruiters
What helps me reply faster:
- — Company name
- — Role's level and reporting line
- — Team's size and stage
- — Compensation band
- — One specific thing about the architecture problem you're hiring for
That's enough for a first call.
§C — Start a conversation
Pick the lowest-friction path.
- Scheduling
- Phone
- On request after a first email
What helps me reply faster
- — A two-line description of what you're building or hiring for
- — Whether this is consulting (§A) or full-time (§B) — or unclear (§C)
- — Your timezone
Slow replies are a feature, not a bug. I sit with new conversations for at least a day before responding, especially the consulting ones.