About
How I work across client needs, technical decisions and delivery.
Most of what I do at Rezolve has the same shape: a club brings a portal problem — sale collapses, members get blocked, data drifts — and I'm the person who turns that into a written spec, a demo, and a release that survives match day.
From the client call to the AWS box
I take the requirement directly from the client, push back on the parts that won't survive contact with production, write the spec, build it, and put it on the EC2 instance it runs on. No internal handoff between any of those steps.
Where the work actually lives
Frontend in WordPress and Next.js, backend in PHP and Node.js, MySQL behind it, and the integration layer I operate against LALIGA's ticketing and member-management APIs. AWS (EC2, RDS, S3, ACM) and Nginx are the engine room.
Spec first, AI-assisted delivery
Every change starts as a written spec: scope, acceptance criteria, and the security and failure cases up front. Implementation is AI-assisted; my part is the spec, reviewing every diff and verifying against the acceptance criteria before anything ships. On a recent platform hardening that meant 70+ specs and 200+ traceable commits in about a month. Releases that survive match day are the test.
Stack
Languages
Frameworks
Data
Infrastructure
Testing
Tools
Experience
6+ years in IT, building and operating production systems.
Location
Palma de Mallorca, Balearic Islands, Spain · Remote · CET
Availability
Open to engineering roles, 2026
10+ years in tech and product, with a background in commercial operations.