Available for work

Leo
Quinteros

Product Engineer

I build, fix and scale apps that people depend on. Bubble, Xano and code when I need it.

6 years of experience30+ projects shipped
How I work

Three things I do every time.

I probably spend too much time thinking about dbs.

The screen is usually the easy part. What sits behind it, the data and how it's structured, is what makes an app survive.

I like owning the whole thing.

From the first conversation to production and whatever comes after. I'd rather see how all of it fits together than just own my one piece.

I care about what happens after launch.

Most of what I work on is already in production. I keep it fast and documented, and I tell you plainly when something isn't worth doing.

I like building things properly.

Even when nobody is going to notice.

Experience

Six years, mostly on live apps.

Scoping · Project management · Development · Testing

Lead Developer, Backend

Toke AIMainly backend and technical lead: Xano architecture, data models, endpoints, tasks and integrations, plus scoping, estimates and the review process. End to end when needed.
Nov 2025 — Jul 2026

Bubble & Xano Developer

Toke AIFeatures end to end: scoping, build, testing and release. Bubble front, Xano behind, and the wiring between them.
Mar — Nov 2025

Independent No-Code Developer

Nocode SolutionsEverything myself: scoping, project management, data design, build, testing, launch and maintenance. Bubble and Xano apps for founders.
2020 — now

Product Lead

Million LabsThe full cycle across many client apps: scoping and estimates, project management, hands-on development, and testing before release.
Jun 2023 — Mar 2025

Data analysis & project management

Earlier careerMinistry of Education, Buenos Aires; EY. I've always been a bit too interested in how things fit together.
Before
On building with AI

I use AI a lot. I also don't trust it.

I use AI every day, for scaffolding, first drafts, the boring parts. It makes me much faster. It also makes it much easier to build the wrong thing very quickly.

  • II still decide what is worth building.
  • III still care about the data.
  • IIII want to understand what can break.
  • IVAnd when something goes wrong, it's still my problem.
Contact

Let's talk.

Prefer to talk it through first?

Book a callor email leo@nocodesolutions.dev
Leo Quinteros · Nocode Solutions