Open to full-time, contract & fractional — remote (UTC−5)

Product engineer. I ship the whole thing.

Frontend, backend, database, infrastructure — and the product decisions in between. I've built and operated production SaaS across esports, fintech, and regulated consumer products, working AI-native with Claude Code at team-scale output.

Work

Real products, in production, built end-to-end. Architecture notes included — ask me about any of it.

Seedro

Founder & Product Engineer — esports coaching & team management SaaS

An esports coaching and team management platform, built solo, end-to-end: Flutter/Dart frontend, Flask REST backend, PostgreSQL database.

The product is architected as a multi-role platform — coaches, players, and recruiters — with a three-tier access model, game-specific theming across six titles, and a full curriculum and season-management system. I took it from stakeholder spec to shipped frontend: translating a ten-feature-area product document into a structured engineering spec, establishing the design system and brand asset pipeline, and delivering the build against it, coordinating with a distributed team across engineering, business analysis, and design.

Flutter/Dart Flask PostgreSQL Multi-role architecture Design systems

Production database migration: Supabase → DigitalOcean

Seedro infrastructure

Migrating a live product off a managed backend is where "full-stack" gets tested. I planned and executed Seedro's move from Supabase to DigitalOcean managed Postgres:

  • Audited the full Row-Level Security surface and rewrote 51 RLS policies, replacing auth.uid() dependencies with session-variable patterns (current_setting) so the database no longer assumed Supabase's auth layer.
  • Replaced Supabase Auth with a custom Flask authentication service (JWT), keeping the Flutter client contract stable.
  • Schema dump, migration sequencing, and rollback planning for a production dataset.

The point of this case study: I don't just build on managed platforms — I can take ownership of the layer underneath when the product outgrows them.

PostgreSQL Row-Level Security Auth systems DigitalOcean Migration planning

Consumer intelligence platform

Product & Tokenomics Engineer — US fintech

Behavioral-intelligence fintech with a registered security token. I authored the token litepaper — rewriting governance language for regulatory accuracy in a registered-security context — and designed the SAFT pre-sale structure, staking tiers, data-quality scoring mechanics, and emission schedule.

This is the product-judgment side of my work: documents that had to satisfy engineers, investors, and compliance simultaneously.

Tokenomics Regulatory writing Fintech Product strategy

Momoñus & regulated consumer products

Co-Founder

A regenerative agtech and consumer lifestyle brand (co-founder, 4+ years). I designed its WhatsApp-commerce architecture and website plan, and built the digital design system from the brand identity.

On the regulatory side, I led federal compliance analysis for a US-licensed processing operation under P.L. 119-37, identifying product reformulation requirements ahead of the November 2026 deadline — experience navigating a regulated industry where engineering and compliance constraints collide.

WhatsApp commerce Regulated products Compliance analysis Brand systems

Want to see code running, not just described? Try the API Playground.

How I work

AI-native, judgment-first

I treat AI coding agents as leverage, not a substitute for engineering judgment. I own architecture and data-model decisions, decompose work into verifiable specs, direct Claude Code against them, and review, test, and edit every change before it ships. The result is solo delivery of full-stack systems — apps, auth services, database migrations — at team scale, with an auditable trail of specs and design docs.

Builder mindset

I'm comfortable owning a feature from idea → UI → backend → infra → deployment. Fewer handoffs, faster iteration, no "works on my machine" surprises.

Operational discipline

Clean deployments and strong defaults: firewall rules, TLS, sensible access, secrets management, and documentation so your team can maintain what we build.

Engagements

I'm open to three shapes of work:

  • Full-time remote — product engineer / founding engineer roles where I own features end-to-end.
  • Contract & contract-to-hire — scoped builds, migrations, or "we need this shipped" projects. Contract-to-hire welcome: evaluate me on real work.
  • Fractional — ongoing part-time engineering ownership for early-stage teams.

Based in Panama City, Panama — full US business-hours overlap. Experienced international contractor.

Toolbox

A snapshot of the tools I regularly work with, grouped by layer:

Backend
Python Flask REST API design JWT auth PostgreSQL (schema, migrations, RLS)
Frontend
Dart Flutter (web + mobile) React JavaScript Design systems
Infrastructure
DigitalOcean AWS EC2 Ubuntu/Linux Nginx TLS/Let's Encrypt DNS Supabase
AI-assisted engineering
Claude Code Anthropic API Spec-driven agentic workflows
Integrations
Stripe Google APIs Document extraction pipelines

Contact

Hiring, or have something that needs shipping? Tell me about the role or the project — I’ll reply within one business day.

GitHub LinkedIn API playground