10+ years
Software engineering
Frontend and full-stack delivery across product, web and enterprise environments.
Technical Project Manager · Fractional CTO · Software Delivery
Planning, stakeholders, technical teams, risks, dependencies and delivery — backed by more than 10 years of hands-on software engineering experience.
Relevant experience
My background combines software engineering, founder-level coordination and enterprise Agile delivery. The point is not to move away from engineering, but to manage software projects with a practical understanding of how they are actually built.
10+ years
Frontend and full-stack delivery across product, web and enterprise environments.
2+ years
Founder-level ownership across product decisions, technical direction, team coordination and end-to-end delivery.
3 years
Scrum-based software delivery in banking and insurance, working across complex multi-stakeholder environments.
Technical Project Management
I can take responsibility for the coordination work that keeps software projects moving and makes progress visible to both technical and business stakeholders.
01
Scope, priorities, milestones, estimates and sequencing.
02
Shared decisions, clear ownership and communication across business and technical teams.
03
Workflows, blockers, handoffs and delivery cadence across internal teams, freelancers or suppliers.
04
Early visibility on constraints that can affect timing, scope or technical choices.
05
A realistic view of project status based on completed work, current constraints and upcoming milestones.
06
Coordination through validation, readiness and release, including the technical details that affect delivery.
When I can help
I am most useful where software delivery needs stronger ownership, better visibility or someone who can connect project decisions with technical reality.
Priorities keep shifting, dependencies surface late, estimates lose meaning, or progress is difficult to read from outside the team.
Requirements, scope and technical constraints need to become decisions that both sides can act on.
Project decisions depend on architecture, implementation constraints or code-level trade-offs that cannot be treated as a black box.
Ways to collaborate
Three focused ways to cover the path from early technical decisions to software delivery and release.
01
Clarify the product, MVP, technical risks and roadmap, define the skills and roles needed, and support the technical evaluation of candidates, freelancers or suppliers.
02
Turn business goals into an executable delivery plan: scope, backlog, milestones, responsibilities, technical dependencies, quality criteria and release path.
03
Ongoing technical leadership and delivery coordination between founders, business and the technical team: priorities, technical decisions, progress, risks, blockers, suppliers, quality and releases without adding a full-time CTO or Technical PM too early.
Selected public work
These projects show how I approach bounded execution, planning, technical trade-offs, verification and maintainability.
Public release · v0.4.0
Public project · work in progress
A React, TypeScript and Fastify application for planning and monitoring software delivery, including project and feature flows, shared contracts, automated tests, OpenAPI documentation and architecture notes.
Public project · MVP complete
A travel planner that compares round-trip flights across multiple dates, coordinates home-to-airport transport and adds source-backed destination information in one end-to-end flow.
How I work
I start from project goals and constraints, make priorities and dependencies explicit, keep delivery measurable, and use technical context to support realistic decisions on scope, timing and implementation.
Notes
A growing collection on maintainability, Agile work, project risk and the practical use of AI in software development.
Start a conversation
Tell me what you are building, where the project is getting difficult and what responsibility needs to be covered. A few lines are enough to understand whether I can help.