---
title: "How I Work"
slug: how-i-work
description: "Engagement model, process, and what it's like to work with me."
---

## The short version

I take on a small number of engagements at a time — product builds and long-term retainers — and own them end to end: architecture, code, infrastructure, and delivery. One person, the whole surface.

## What "owning it" means

- **From scoping to shipped.** I talk to stakeholders, design the system, write the code, set up the infra, and stay for the operations. No hand-offs, no "that's not my layer."
- **Judgment over ceremony.** The best code is the code never written. I'll question a complex request before building it, and I mark every intentional shortcut so it's a decision, not a surprise.
- **Boring over clever.** Standard library first, platform features second, dependencies last. Deletion is my favorite refactor.

## AI-forward, verification-first

I work in the forward-deployed model: embedded in your environment, turning frontier AI models into production workflows that hold up under real operational constraints. That's also how I build — AI agents accelerate my delivery (580+ production PRs in six months on my current engagement, solo), but every change gates through deterministic checks first: typecheck, lint, tests, structural rules. The agents write a lot of the code; the checks and I decide what's true.

## Communication

- **Async-first.** Clear written updates over meetings. When a call helps, we call.
- **A weekly rhythm.** You always know what shipped, what's next, and what's blocked.
- **Direct access.** You work with me, not through an account manager.
- **Timezone:** Andorra (CET) — solid overlap with both European hours and US mornings/afternoons.

## Engagements

I work through [Toptal](https://www.toptal.com/resume/eduardo-wass-rosado) or directly via my company, Wass Tech SLU. Retainers for ongoing product work, fixed-scope builds for well-defined projects.

If that sounds like what you need, [get in touch](/contact/).