Javier

Why do you do this work?

I kept hitting the same wall in every game with complex controls — the fix was always ‘memorize more,’ never ‘the software should just understand you.’ Building EchoControl was the itch that wouldn't go away until I built it.

How would you sum up how you work?

Decide slowly on the things that are hard to undo, decide fast on the things that aren't.

What frustrates you about this market?

How much of this space ships a demo that works great on stage and falls apart the moment a real player, a real accent, and an ugly headset mic show up.

What are you most proud of?

That the Custom Profile builder shipped without needing a scripting language — it took three rewrites, and it would've been easier to just document a config file and call it a feature.

What's non-negotiable for you?

If a decision doesn't have a reason attached, it doesn't ship — ‘we felt like it’ isn't a design rationale.

What do people get wrong about your role?

That ‘product lead’ means picking colors and writing user stories. Most of the job is saying no to good ideas that don't fit.

What does a normal day look like?

Mornings are for anything that can't be interrupted — architecture, profile logic. Afternoons are demos, support threads, and whatever broke overnight.

Anything outside work that shows up in how you think?

I still play the games EchoControl supports, off the clock, without taking notes — if I only played to test, I'd lose the instinct for what actually annoys a player mid-session.