Lead a small team.Partner with product.Stay in the code that ships.
I have spent a decade as the player-coach this role describes — co-founding , delivering complex cloud-native web & mobile apps across 9 geographies, and going Engineering Manager → CIO while staying hands-on. Over a decade, I engineered custom trading ERPs, media transformation pipelines, cost optimizations, and specialized medical software (patient progress and medicine effectiveness tracking for 2 multi-branch hospital groups) while establishing repeatable workflows and a high-performance culture.
- Cycle time ↓ 75%
- Team scaled to 22
- 0→1 across 5 verticals
A product idea. A delivery plan. A launch members feel.
The gap between a good product idea and a shipped, loved feature is where a Lead Software Engineer earns their seat. I sit between the product manager and the team — pressure-testing feasibility, turning ideas into a delivery plan, and staying in the code so architecture, quality and momentum never drift apart. Close to the members, close to the codebase, and building the process that lets a small team ship like a big one.
Is this the lead you're looking for?
Voy described a very specific engineer. Here's the role, point by point — and every box I tick.
- Lead a small, cross-functional team of frontend & backend engineers
- Be the technical partner to the product manager
- Turn product ideas into delivery plans and successful launches
- Stay hands-on across architecture, implementation and deployment
- Make quality a habit — TDD, code review, CI/CD
- Grow and develop the engineers around you
- Read business and engineering metrics fluently
- Work from the London Bridge office, three days a week
Eight for eight on the required bar — met head-on. The nice-to-haves and the two honest ramps are mapped just below.
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.
Leadership & Scale
Effective player-coach guidance to align and build teams.
Platform & Delivery
Clean architecture, automated pipelines, and solid test coverage.
Product & Cadence
Translating product ideas into business metrics and launches, aligned on-site.
Verdicts & Evidence
Detailed evidence, technical receipts, and ramp-up pathways mapped requirement by requirement.
Engineering Manager or Lead Software Engineer experience in product-centric environments
Evidence & Proof
I co-founded in 2017 — a product-centric venture studio — and led its engineering as Software Engineering Manager (2022–2024) then CIO, always as a player-coach. Over a decade, I engineered systems ranging from custom ERPs for trading businesses to compliant, specialized medical software (patient progress & medicine effectiveness tracking for 2 separate multi-branch hospital groups), delivering complex web/mobile apps across 9 global geographies.
Lead a small, cross-functional team of frontend & backend engineers, as the technical partner to the product manager
Evidence & Proof
This is my default mode. I led small cross-functional pods end-to-end — the dedicated Norway delivery team for Frontgo (Vipps payments, financing) from zero to production, and 's own product squads spanning frontend, backend, QA and design — and repeatedly acted as the technical partner translating fuzzy product intent into feasible, shipped plans.
Full product lifecycle experience — transform product ideas into delivery plans and successful launches
Evidence & Proof
0→1 across five verticals — music-tech, gaming/esports, hospitality, health-tech and professional networks — from discovery through launch. went idea → 15,000-user GDPR commerce flow → acquired by Loopcloud in 2026; went concept → live HIPAA clinical platform; I hold CSPO because the roadmap discipline matters as much as the build.
Understanding of business and engineering metrics — evaluate feasibility and continuously improve
Evidence & Proof
I run to numbers on both sides: 4× faster time-to-market (75% cycle-time reduction) through repeatable workflows and cloud-driven consistent delivery mechanisms; time-to-value, activation and unit economics on the business side, including cloud cost optimizations and modelling AWS cost against competitor clouds by region.
Solid understanding of architecture, programming concepts and patterns, and TDD
Evidence & Proof
Architected cloud-native systems with OIDC/RBAC/SSO and event-driven architectures. Driven by AI-native engineering in recent times, pushing the team toward system evals and controlling the speed of agentic development with careful guardrails, deterministic hooks, and repeatable skills.
Contribute hands-on across architectural design, implementation, and deployment
Evidence & Proof
I am a CIO who still ships daily — hands-on with cloud-native solutions, cost optimization, media transformation pipelines, TypeScript/Node.js, Go ('s ConnectRPC service on Cloud Run), and Python for AI. I earn technical credibility by being in the code, not by reviewing from a deck.
Grow and develop teammates — actionable feedback, growth opportunities, connect them with customers
Evidence & Proof
Coaching engineers into their best next role is the part I care about most. Alumni I mentored now lead at organisations in Norway (2), Canada and Germany, plus two leading local firms. I run weekly 1:1s and put engineers directly in front of clients so they build for real people, not tickets.
Strong communication with both engineers and leadership
Evidence & Proof
Manager-to-manager alignment across a cross-border Norway pod, C-suite discovery and translation for enterprise clients, and public teaching (writing, a YouTube French-learning series). I speak engineer and executive without a translation layer in between.
Ability to work from the London Bridge office 3 days per week
Evidence & Proof
I am relocating to the UK deliberately — it is one of my three target geographies, and I have family in the UK. I am ready for Voy's 3-day London Bridge cadence from day one; in-office product partnership is exactly the work I want next.
Nice to have: A/B testing and feature-flag experience
Evidence & Proof
Feature-flagged, gated releases and staged rollouts through CI/CD are how I ship safely; I have run funnel and conversion analysis on 's 15,000-user commerce flow.
Ramp Pathway
Formal, statistically-powered A/B experimentation platforms (multi-armed tests, guardrail metrics) are the lighter edge — I know the concepts and have shipped the flagging plumbing they sit on, so standing up Voy's experimentation cadence is a fast ramp, not new ground.
Nice to have: user-behaviour and design awareness
Evidence & Proof
I started as a UX Engineer and still design in Figma — design systems, prototyping, and shipping the interface myself. was designed Figma-first; I raise the craft bar by building it, and I read behaviour before I read a spec.
Nice to have: Computer Science degree
Evidence & Proof
Field of Study: Computer Science & Engineering, North South University (2012–2015) — then straight into building. Nine-plus years of shipped, production work since.
Ramp Pathway
The credential is experience-based rather than a completed degree; a decade of 0→1 delivery and engineering leadership is the operative qualification, and the JD lists this as nice-to-have.
The way Voy makes a member's levels visible, I've made a team's delivery health visible — for a decade.
At , I made TDD, code review and CI/CD gates the default rather than a fire drill — the same discipline that took a 22-person cross-functional team from ad-hoc delivery to 4× faster time-to-market (a 75% cycle-time reduction). That is a documented outcome, not a pitch: velocity, review latency and risk were tracked metrics for the team I led, every sprint.
Leading a delivery team.
The role is 'lead a small team, partner with product, stay hands-on.' Here's how I actually run that — not a management style deck, a daily practice.
Technical partner to the product manager
I sit next to product, not downstream of it. I pressure-test feasibility early, name the risky unknown out loud, propose the cheapest probe to close it, and turn intent into a delivery plan the team can commit to. Roadmaps I can speak to because I hold CSPO and have owned product-led scrum end to end.
Player-coach — in the code, raising the bar by example
I stay hands-on across architecture, implementation and deployment. Engineers trust a lead who ships with them, reviews their PRs, and takes the gnarly slice — so the craft bar goes up by example, not by memo.
Quality is a habit, not a fire drill
Repeatable workflows, review discipline, and automated CI/CD gates are the default operating mode — reducing time-to-market by 4×. In recent times, I've pushed the team toward AI-native engineering and system evals to validate LLM outputs.
Grow the team, connect it to real people
Weekly 1:1s, actionable feedback, and engineers put directly in front of customers so they build for members, not tickets. My alumni now lead teams in Norway, Canada and Germany — growing people into their next role is the point.
Real teams. Real outcomes.
EKAGRA: a HIPAA clinical platform, built and still running
I architected 's HIPAA-compliant patient-data pipeline and EHR integration across a multi-specialist clinical platform, and aligned it to Bangladesh Digital Health standards for Ministry-level rollout. It's the closest analogue to Voy's world — sensitive health data, clinical trust, real people — and I built the engineering and the compliance in from day one.
- 2026 platform: 3,242 patients · 13,340 schedules · 64 doctors · 7 centres
- HIPAA-compliant EHR integration and patient-data pipeline architected end to end
- Compliance aligned to Bangladesh Digital Health standards alongside a Ministry-level rollout
In the code with the team — reviews, the gnarly slice, deploys owned not delegated
Partner with product on feasibility, turn ideas into a plan, ship a launch members feel
TDD, review discipline and CI/CD gates as the default — quality is a habit
Actionable feedback and a path to the next role — engineers grown, not just managed
The player-coach seat — already my default
Leading a small cross-functional team while staying in the code is exactly how I operate: co-founder → Engineering Manager → CIO, a 22-person product engineering firm spanning design, engineering, QA, product and business, and I still ship daily. I am the technical partner a product manager wants — feasibility, trade-offs and a plan that actually launches.
Health-tech is home ground, not a new domain
I architected specialized medical software, including patient progress and medicine effectiveness tracking systems driving clinical decisions for 2 multi-branch hospital groups ( platform, 3,242 patients, 7 centres). Voy's world of care, sensitive member data and clinical trust is one I have already built in.
Compliance and quality as product care, baked in
GDPR, HIPAA and WCAG 2 shipped from day one across five client organisations — heading off six-figure retrofits and breach exposure. For a health platform serving a million-plus members, treating data protection and accessibility as user-facing care (not back-office tax) is exactly the instinct the codebase needs.
AI-native delivery — earned, not just claimed
My daily development is Claude-led (Gemini second); I build agentic workflows in Go/Python and run a Claude-powered CMS. I hold Anthropic certifications and push squads toward system evals, agentic guardrails, deterministic hooks, and repeatable skills.
I don't lead from a deck. I've architected the platform, scaled the team, and coached the engineers who now lead their own — and I want to do it for a product that makes everyday care feel joyful.Fauzul — on why Voy
The hard questions.
The objections a sharp hiring team would raise about this profile — answered straight, the way Voy answers a member's questions.
Yes, genuinely, and I'm energised by it. The title is co-founder/CIO, but the work I love and do daily is the player-coach lead: in the code, partnering with product, unblocking a small team. I've also held Software Engineering Manager, Staff Engineer and UX Engineer seats and adapted fast to existing hierarchies. Reporting to a PM and EM and owning one delivery team well is exactly the focus I want next — fewer hats, deeper craft.
The domain transfers cleanly — sensitive health data, clinical trust, compliance and care are what I built (specialized medical software, patient progress, and medicine tracking at 2 separate multi-branch hospital groups). The honest step up is consumer scale: my biggest consumer flow is at 15,000 users, so a million-plus members is genuinely bigger. But the failure modes of scale — caching, queues, event-driven load, cost-by-region — are ones I've engineered for, and I'll pick up Voy's specific growth and retention patterns fast working with your product and data teams.
I have the plumbing and the instinct, and I'll be honest about the edge. Feature-flagged, gated, staged rollouts through CI/CD are how I ship; funnel and conversion analysis I've done ('s commerce flow). What's lighter is running a formal, statistically-powered experimentation programme — multi-armed tests, guardrail metrics, an experimentation platform. That's concepts I know sitting on plumbing I've shipped, so it's a weeks-not-months ramp.
Yes. I'm deep in TypeScript/Node.js and React day to day, ship Go and Python in production, and I've onboarded onto unfamiliar client codebases across nine geographies for a decade — that's the job. I also use AI (Claude-led) specifically to compress codebase onboarding, so I get productive on a new stack in days, not weeks, and I'm careful to earn the team's trust by being useful in review early.
Because the work behind the title is my decade. Leading a small cross-functional team, being the PM's technical partner, owning architecture-to-deploy, growing engineers into their next role — I've done all of it, repeatedly, as EM and CIO. The title is new; the operating mode is my default. And health-tech plus compliance-by-design means I arrive already fluent in Voy's kind of product.
Yes, deliberately. The UK is one of my three target geographies, I have family here, and I'm ready for Voy's London Bridge 3-day cadence from day one. In-office partnership with product and the team is exactly the kind of work I'm optimising for — I'm not looking for fully-remote, I'm looking for this.
Your values, answered with receipts.
Voy's own values are the frame. Here's what I bring to each — past the JD's checklist.
Founder-operator who ships the whole thing
Co-founder/CIO who found market fit and shipped under real constraints — from architecture to deploy to the compliance nobody else wanted to own. I optimise for outcomes, not activity. This is the value that shows up first in how I work: nobody has to chase me for the unglamorous parts of a launch.
Compliance as care, baked in from day one
HIPAA, GDPR and WCAG 2 shipped across five client orgs — treating data protection and accessibility as user-facing care. For a health platform, that instinct protects members and the business at once.
Relentless, provable consistency
A 900+-day daily French streak, learning in public on YouTube, and CI/CD velocity discipline — the same compounding consistency I bring to a team's shipping cadence.
0→1 across five verticals, on the AI frontier
Music-tech, gaming, hospitality, health-tech and professional networks — plus frontier agentic-AI builds and two Anthropic certifications. I bring range and a bias to probe the risky unknown early.
Cross-functional leadership, not just engineering
Led design, engineering, QA, product and business inside one firm, and coached engineers who now lead teams in Norway, Canada and Germany. I keep a distributed, cross-functional team in one cadence.
Design-eng taste, raised by example
UX-engineer origins and daily full-stack building — I care how it feels, not just whether it works, and I raise the craft bar by shipping it myself.
A player-coach stack.
The stack and the receipts behind the claims.
Management
- CSPO
- SCRUM
- Linear
- Jira
- 1-on-1 coaching
- Stakeholder mgmt
- Remote-work lead
- GDPR / HIPAA compliance
- HR & hiring
Delivery & Team Leadership
- Technical partner to product (feasibility)
- Sprint planning & delivery predictability
- Cross-functional pods (FE · BE · QA · design)
- 1-on-1 coaching & growth
- Hiring & structured onboarding
Quality & Testing
- Code review discipline
- CI/CD release gates (GitHub Actions)
- Feature flags & staged rollouts
- Eval harnesses for AI output
- 4× faster time-to-market (75% cycle-time cut)
Player-Coach Stack
- React / Next.js
- Go (ConnectRPC · Cloud Run)
- Python (AI & data)
- PostgreSQL
- Docker · serverless · GitHub Actions
AI-Native Development
- Agentic systems in production (A2A · MCP · n8n)
- AI-assisted review, docs & onboarding
- Anthropic Claude Code & Agent Skills certified
Health-tech, Trust & Compliance
- OIDC
- RBAC
- JWT
- Auth0
- Multi-tenancy
- Magic-link
- Passport
- HIPAA (EKAGRA clinical platform)
- GDPR / VAT
- WCAG 2
- Sensitive health-data handling
- Auditability
Make everyday care life-changing.
I'm relocating to London for this — the UK is a deliberate target and I have family here, so I'm ready for Voy's London Bridge 3-day cadence from day one. Leading a delivery team as product's technical partner, in a health platform scaling joyful care, is exactly the work I want next.
982-day French streak · the same consistency I bring to shipping