Start shipping again.
Your startup doesn't need to hire more "rockstar" engineers. It needs an experienced engineering leader to stabilize your platform, mentor your team, and build a technical foundation that supports growth. Stop the constant flow of technical tickets or runaway cloud bills.
If R&D feels chaotic, growth slows down.
- Every release is risky.
- Engineers are busy but throughput is low.
- Incidents steal roadmap time.
- The architecture fights every new feature.
- Hiring more people makes it worse.
Chaos isn't just technical. It's missed revenue, churn risk, and team burnout.
AI made you faster. Now it's time to get serious.
AI lets teams ship a lot more, but when you hit traction, the bottlenecks shift: incidents, regressions, unclear ownership, and rising infrastructure costs. My job is to keep the speed and add the discipline that makes it safe to scale.
Vibe coding is great for finding product-market fit. The mistake is leaving the prototype in charge of production.
Production-hardening checklist
- Guardrails: CI checks, formatting/lint/type, test strategy, release gates
- Observability: structured logs, metrics, traces, dashboards, SLOs + alert hygiene
- Reliability: incident process + Root Cause Analysis → prevention loop
- Architecture: boundaries, service ownership, migration sequencing
- Cost control: budgets, usage caps, performance baselines, top cost drivers
Craftsmanship = predictable speed
In an industry obsessed with moving fast and breaking things, I optimize for deliberate execution that keeps shipping fast next quarter not just this week.
Code is a liability
Every line is a maintenance promise. I reduce complexity to increase velocity.
Calm beats chaos
High output comes from safety rails: CI, tests, observability, clear ownership.
Mentorship multiplies
I level up engineers through standards, reviews, pairing, and clear decision docs.
Stability is a feature
Reliability isn't luck. It's process (SLOs, alert hygiene, RCA, prevention).
Boring software is a competitive advantage.
Engagement models
Fractional CTO / Interim Head of Engineering
Best for: Series A/B startups needing immediate leadership and delivery control.
- Delivery system: planning + execution cadence, ownership map, decision logs
- Reliability program: SLOs, monitoring, incident response, RCA loop
- Architecture direction: constraints, guardrails, migration sequencing
fewer incidents, faster releases, less thrash.
Staff+ Individual Contributor
Best for: Scale-ups needing high-leverage technical execution on critical systems.
- Deep technical projects with measurable outcomes (reliability, latency, cost)
- Refactors/migrations with safety rails and rollout discipline
- Mentorship via PR standards, pairing, docs
Team reset / Player-coach leadership
Best for: Teams stuck in low-trust, high-friction delivery patterns.
- Practical engineering standards (reviews, testing strategy, on-call expectations)
- "Show-don't-tell" coaching inside real work
- Lightweight operating system for engineering
Prototype → Production Hardening
Best for: Startups that shipped fast (often with AI) and are now seeing cracks: regressions, incidents, performance issues, rising cloud spend.
- Reliability & scale assessment (codebase + infra + ops)
- Quality gates in CI (format/lint/type + tests + smoke e2e)
- Production readiness baseline: SLOs, dashboards, alert rules
- Cost & performance baseline: budgets, top cost drivers, quick wins
- A hardening roadmap with milestones and measurable targets
safer deploys, fewer regressions, predictable shipping, ability to scale users without linear cost growth.
How it works
- Intro call (30 min): align on symptoms, constraints, desired outcomes
- Rapid assessment (1–2 weeks): interviews + repo/infrastructure review + metrics baseline
- Execution plan: prioritized roadmap, risks, sequence, success measures
- Delivery + enablement: implement + train + handoff playbooks
What I measure
- Lead time to production
- Incident rate / MTTR
- Change failure rate
- PR throughput & review latency
- p95 latency / error rates
- Cloud spend trend vs usage (unit cost per active user)
Track record
Logistics
- Based in Madrid (CET).
- Available for 4 hours of daily EST overlap.
- Seamless B2B invoicing.
- Remote-first by default.
- English / Spanish.
You should work with me if…
- You need predictable delivery, not heroics
- You want calm systems and clear ownership
- You can invest in fixing root causes, not just patching symptoms
- You shipped fast (often with AI) and now want to harden without losing velocity
Trigger symptoms
- Your team ships constantly but prod feels fragile.
- Regressions happen weekly.
- Infra costs are rising faster than usage.
- No one trusts releases; incidents derail the roadmap.
Not a fit if…
- You want "move fast" without quality gates
- You're optimizing for the cheapest option
- You expect miracles without organizational change
I'm not the cheapest engineer you can hire. I'm the one you hire when you can't afford to get it wrong again.
Let's build something solid.
Stop firefighting. Start shipping with confidence. Let's talk about what predictable delivery looks like for your team.