Mateo Briosso · software engineer · montevideo, uy I build software that holds up.
frameworks, pipelines, and the code that proves the rest of it works. seven companies, nine years.
scroll ↓
one dot · one feature · one thing that has to keep working
Every dot is a feature you shipped.
the surface area grows faster than the team does
Every one of them can break.
add a feature and you inherit everything it touches. nobody has time to check all of it by hand.
And then one does.
✗ a refactor takes the session with it
✗ a rounding change moves a total by a cent
✗ a dependency bump breaks one browser
nobody wrote a test for that one. your users found it first.
I build the systems that stop this.
The grid is what a checked system looks like. Same dots, same features, nothing moving on its own.
✓ frameworks that run on every push, whether or not anyone remembers
✓ pipelines that stop a bad build before a user sees it
✓ suites that survive the next refactor instead of getting deleted after it
✓ a failure that tells you what broke, not that something did
nine years of this. web, mobile, api, in four stacks and five languages.
three ways in
Depending on what you came for.
I am a software engineer in Montevideo, Uruguay, working remotely. For nine years I have built the software that other software gets tested by: automation frameworks, CI pipelines, and the parallel-execution machinery underneath them, in Java, JavaScript, TypeScript, Python and SQL. Seven companies, from Abstracta in 2017 to a US insurance company now. US clients are contracted through a Wyoming LLC.
Where to go next
- Experience: nine years by employer, what I built at each, and the stack. For anyone hiring.
- Work: Briosso, my QA service for AI-built software. Playwright regression suites for founders shipping with Cursor, Claude Code, Lovable, Bolt, v0 and Replit.
- About: where I am from, how I got here, and how I work with a team.