01 · owner
No bench, no juniors
You work with the engineer who owns the outcome. One inbox. One PR author.
no fluff · no bench
A senior AI developer who ships
Twelve years of product engineering plus AI-first delivery. Embed for sprints or months — code, reviews, and production releases. You merge the PR; the outcome is already owned.
● checks passed branch: feature/ai-wedge reviewer: you owner: info@clutchdeveloper.com
// diff --stat why/
What you get at the merge boundary
Embedded AI engineering — architecture, implementation, and release leadership. No agency layers between you and the person who writes the code.
02 · workflow
AI-first, taste-gated
Same speed boost used on live Clutch products — generate faster, reject harder. Strong models when they fit.
03 · stack
Full stack comfort
Mobile, web, backends, and model integration. If it ships to users, it is in scope.
04 · timezone
Barcelona · remote
CET-friendly with US East Coast overlap. Async by default; standups when they earn their slot.
// open pull requests
Engagement shapes that merge
Embedded engineer
Join your standup, board, and release train. Tickets in, merged code out.
Rescue sprint
Unstick an AI feature or mobile release. Kill the thrash; land the wedge.
Architecture review
Threats, cost, and scale before you overbuild. Written findings, not vibes.
Pair programming
Level up your team while shipping the thing. Knowledge transfer is the product.
// git commit -m "schedule call"
Ready to open a branch together
Reply within business days. Bring a repo link or a stuck ticket. No discovery theatre.