Unblock the team.Make quality automatic.Keep velocity non-negotiable.
I have spent a decade as the operator who keeps high-output teams shipping — co-founding , growing it into a 22-person, cross-functional product engineering venture firm (52+ professionals total FT & contract), and going Engineering Manager → CIO. AI is already embedded in how I lead engineering, and I stay close to the code.
Any team, any sprint, any blocker. Surfaced in seconds.
The same way BigGeo turns spatial data into decisions, I turn delivery signals into unblocked teams — velocity, review latency and risk made visible before they compound into missed commitments.
Five tools. Six dashboards. One clear picture.
Sprint boards, pull requests, CI, on-call, 1:1s — the signals of a high-output org arrive fragmented, and velocity dies in the gaps between them. A Head of Engineering is the unifying layer: I keep engineers unblocked daily, make standards a habit instead of a review comment, and surface dependencies early so cross-team delivery stays on track. Close to the code, building the process that scales the people.
Every requirement, answered straight.
Mapped to the posting, verdict by verdict — the required bar met head-on, the nice-to-haves marked honestly with the bridge I'd take.
7+ years hands-on engineering, with 3+ years leading engineering teams in a people-and-process capacity
I co-founded in 2017 and have 9+ years hands-on since. People-and-process leadership specifically goes back 7 years — well before the CIO title landed in 2024, through Software Engineering Manager and a dedicated Norway delivery pod (Frontgo) with full recruitment and people management — reinforced by structuring the founding team from day one.
Proven track record running sprint cycles, code review processes, and deployment operations in a production environment
I ran 's delivery for enterprise clients across nine geographies — owning sprint planning, review and production deployment. At every content change ships to production only through CI/CD review gates, and standardizing that discipline is how I cut time-to-market 4× (75% less cycle time).
Strong coding skills in at least one modern language (Python, Go, Rust, Node.js, Java) and the credibility to participate meaningfully in technical decisions
Deep in TypeScript/Node.js; Go in production ('s ConnectRPC microservice on Cloud Run, ); Python for AI and data. I am a player-coach CIO who still ships daily, so I earn technical credibility by being in the code, not adjacent to it.
Demonstrated ability to improve team velocity and code quality without sacrificing engineer morale or shipping discipline
Velocity and quality went up together because review discipline and CI/CD gates were the norm, not a fire drill — a 22-person, cross-functional product engineering venture firm kept shipping without burning out, and several engineers grew into senior roles along the way.
Strong AI literacy and the ability to use AI tools to accelerate engineering workflows, code review, and team documentation
This is how I already work: daily agent-led development (Claude-led, Gemini second), Anthropic Claude Code 101 and Introduction to Agent Skills certifications, and a Claude-powered CMS at that turns plain-English requests into reviewed PRs. The JD names Cursor — I use AI to compress review, docs and onboarding every day.
Clear, direct communication with both engineers and leadership — no translation layer required
Manager-to-manager alignment across a cross-border Norway pod, C-suite discovery and translation for enterprise clients, and public teaching (writing, YouTube). I speak engineer and executive without a hand-off in between.
Nice to have: experience scaling an engineering org through a Series A to B growth phase
I scaled into a 22-person, cross-functional product engineering venture firm (52+ professionals total FT & contract) through real hypergrowth pressure and built the hiring, onboarding and standards machinery a growing org needs.
Ramp It was a capital-efficient bootstrapped product engineering venture firm, not a VC-backed A→B — so the new part is venture board and burn cadence, which I will absorb fast partnering with the CTO. The scaling craft itself transfers on day one.
Nice to have: background in geospatial, infrastructure, or platform engineering
Earlier in my career (2018–2019, New York, NDA) I built the geospatial core of a location-claiming platform: geofencing on Android and iOS, geospatial queries over Firebase, and a geohash-indexed claim system tied to Stripe payments — shipped first on Angular + native Android/iOS, then rebuilt in Flutter. I have kept shipping map-based data products since — 's live international markets map (d3-geo + a topojson world atlas) and 's anatomical wound-coordinate mapping — plus platform work (multi-tenant OIDC/RBAC, event-driven AWS).
Nice to have: familiarity with data-heavy or real-time compute environments
runs sub-50ms audio-video sync with event-driven AWS SQS/SNS/EC2 transcoding at 10k+ users; analyzes 47,091 matches to predict player-availability heatmaps; carries 13k+ clinical schedules.
Ramp Real-time media and data-analytics systems are adjacent to spatial real-time compute — I know the failure modes; BigGeo's specific engines are the ramp.
Nice to have: experience building engineering hiring pipelines and technical interview processes from scratch
I built 's hiring from zero to a 22-person, cross-functional team, led recruitment and people management for the Frontgo pod, and designed interview and structured-onboarding processes that compressed ramp time and carried the culture from day one.
Real teams. Real results.
ELO: 22-person firm, and still shipping
I co-founded in 2017 and ran it Engineering Manager → CIO — growing it into a 22-person, cross-functional product engineering venture firm delivering for clients across nine geographies. I made CI/CD and code review non-negotiable, which is how I cut time-to-market 4× (75% less cycle time).
- Owned sprint planning, code review and production deployment across a multi-year client portfolio
- Led a dedicated Norway delivery pod (Frontgo) through a Vipps integration, from kickoff to a clean in-house handover
- Partnered on 's HIPAA clinical platform, which onboarded 9,650 new schedules in 2026
I don't manage from a deck. I've scaled the team, shipped the code, and coached the people who now lead their own.
AI-native engineering leadership — already
My daily development is Claude-led, I build agentic systems in production ( on A2A, 's n8n pipeline), and a Claude-powered CMS in a client's stack turns plain English into reviewed PRs. I hold Anthropic's Claude Code 101 and Introduction to Agent Skills — earned, not just claimed.
A decade growing a 22-person product engineering venture firm (52+ professionals total FT & contract) — and keeping them shipping
Co-founded , went Engineering Manager → CIO, and made CI/CD and code review the default, not a special event — so a cross-functional firm kept shipping reliably as it scaled.
Player-coach who still ships
A CIO who codes daily in TypeScript/Node, Go and Python and builds the exact AI systems the team uses — credible in technical decisions because I am in the code, not a translation layer over it.
Standards as habit, compliance as design
Shipped HIPAA, GDPR and WCAG 2 across five client organisations and treated testing, review and deploy gates as non-negotiable — the discipline BigGeo needs for Governed Monetization on real-world data.
The engineering team building foundational infrastructure needs an operator who treats quality and momentum as non-negotiable. I've been that operator for a decade.
AI-native engineering, in practice
The team is AI-enabled and expectations are high — that is already how I operate. Not a memo about adopting AI; a daily practice.
- 01
Development is agent-led, by default
My daily development is Claude-led (Gemini second) — and I build agentic systems, not just prompt them: on Google's A2A protocol, 's multi-agent n8n pipeline, and a Claude-powered CMS whose plain-English requests ship to production only through CI/CD review gates.
- 02
AI compresses review, docs and onboarding
The JD names Cursor — I use AI to accelerate code review, keep documentation current, and cut onboarding ramp. It's how a small team ships like a big one without dropping the quality bar.
- 03
Certified where it's load-bearing
My Anthropic certifications back that up — earned, not just claimed. As BigGeo's own roadmap says 'Claude Coming Soon,' that depth lands exactly when you'll want it.
- 04
Evals over vibes
AI output gets the same discipline as human output — evaluation harnesses, review gates and auditability, so 'move fast' never means 'ship unverified.' That's how AI stays an accelerator, not a liability.
The hard questions.
The objections a sharp hiring team would raise about this profile — answered straight.
Because co-founder/CIO IS the operator seat this role describes. I've carried 7 years of people-and-process leadership at — through Software Engineering Manager and now CIO — on top of a decade owning sprint cycles, review and production delivery. The title is new; the work is my default operating mode.
It's real, not adjacent: geofencing on Android and iOS, geospatial queries over Firebase, and a geohash-indexed claim system tied to Stripe payments, shipped in production back in 2018–2019. That's honestly the scale to flag — an app-level location feature, not enterprise spatial infrastructure — so the real ramp is BigGeo's platform scale, not the domain itself. I've kept shipping map-based data products since (, ), and I have a documented record of getting productive in a new domain fast.
The AI-tooling skill is model-agnostic — I lead an AI-accelerated org regardless of provider. And it's actually well-timed: BigGeo's own roadmap says 'Claude Coming Soon,' so my Claude depth and two Anthropic certifications land exactly as you bring it into the Spatial Cloud.
I scaled into a 22-person, cross-functional product engineering venture firm under real pressure and capital-efficiently, which is arguably harder. The hiring, onboarding and standards machinery is identical; the genuinely new part is VC board and burn cadence, and I'll absorb that fast partnering with your CTO.
Yes — I'm a CIO who ships daily in Go, Node and Python and builds the agentic systems the team would use. I'd participate in code review and technical decisions, not watch from a deck. Engineers trust leaders who are in the code with them.
Yes, deliberately. Canada is a target geography for me and I'm ready for BigGeo's hybrid cadence from day one. Partnering with the CTO on hiring, team structure and strategy in-office is exactly the work I want next.
Any size, any slice. The whole operator.
The JD is the checklist. Here's what I bring past it.
I ship the product, not just the process
UX-engineer origins and daily full-stack building — I raise the craft bar by example, not by memo.
People who outgrow the role
Alumni I coached now lead teams in Norway; others went on to graduate study in Canada and design roles in Germany. Growing engineers is the point.
Led more than engineers
grew into a 22-person product engineering venture firm spanning design, engineering, QA, product and business — with 52+ professionals contributing full-time or on contract across its history. I led engineering within it, end to end.
Commercial instinct, capital-efficient
Co-founder/CIO who found market fit and shipped under real constraints — I optimise for outcomes, not activity.
Nine geographies, one cadence
Delivered remote-first for clients in London, Oslo, Zurich, Dubai, Florida and Montreal — comfortable keeping distributed teams in sync.
Relentless consistency
A 900+-day daily French streak and learning in public (YouTube, OSS) — the same consistency I bring to shipping.
A player-coach stack.
The stack and the receipts behind the claims.
Management
- High-agency ownership
- CSPO
- SCRUM
- Linear
- Jira
- 1-on-1 coaching
- Stakeholder mgmt
- Remote-work lead
- GDPR / HIPAA compliance
- HR & hiring
Engineering Operations
- Sprint planning & delivery predictability
- Code review & tech-debt discipline
- CI/CD & deployment operations
- Velocity & quality as tracked metrics
- Hiring pipelines & structured onboarding
- Daily unblocking cadence
AI-Native Development
- Claude-led daily development (Gemini second)
- Agentic systems in production (A2A · MCP · n8n)
- AI-assisted review, docs & onboarding
- Eval harnesses & auditability
- Anthropic Claude Code & Agent Skills certified
Player-Coach Stack
- TypeScript / Node.js
- Go (ConnectRPC · Cloud Run)
- Python (AI & data)
- React / Next.js
- PostgreSQL
- Docker · serverless · GitHub Actions
Geospatial & Data
- Geofencing (Android · iOS)
- Geospatial queries & geohash indexing
- Map-based data products (d3-geo · topojson)
- Real-time media & sync (sub-50ms)
- Event-driven AWS (SQS/SNS · Lambda)
- Analytics over large corpora
- Multi-tenant platforms
Trust & Compliance
- OAuth2
- OIDC
- RBAC
- JWT
- Auth0
- Multi-tenancy
- Magic-link
- Passport
- HIPAA
- GDPR / VAT
- WCAG 2
- Auditability
Stop guessing. Start shipping.
I'm relocating to Vancouver for this — Canada is a deliberate target, and I'm ready for BigGeo's hybrid cadence from day one. Partnering with your CTO on hiring, team structure and engineering strategy is exactly the work I want next.
982-day French streak · the same consistency I bring to shipping