SUBJECT. ZERO / PRODUCT ENGINEER + BUILDER

You can call me
Zero.

The identity is private. The way of thinking, building and shipping is not.

Zero is a real person working across product, frontend, backend, data and operations. AI expands execution; architecture, curation and responsibility remain human.

BY TESTA

The starting point.
The zero that starts everything.

I test.
I learn.
I share.
I build.
From scratch.

DOSSIER. DRAFT / PROVISIONAL TECHNICAL PROFILE

A professional profile.
Without a civil identity.

The labels below remain provisional. Technologies and decisions can be verified in the experiments; personal data only enters when it makes sense.

ROLE
PRODUCT ENGINEER / BUILDER
SHAPE
FULL-STACK END-TO-END
MODE
SOLO + AI AGENTS
FOCUS
SYSTEM DESIGN + PRODUCT
BASE
REMOTE / PROTECTED COORDINATES
SIGNAL
APPLIED CURIOSITY

CAPABILITY MAP. 04 / EVIDENCE IN THE PORTFOLIO

Full-stack not as a list.
As responsibility.

Each capability below points to systems where it had to work alongside the others — not to an abstract proficiency bar.

  1. 01

    Product interfaces

    Dense, responsive and accessible flows for operations, collaboration and play.

    • TypeScript
    • React 19
    • Next.js 16
    • Vite
    ERP / Auto Whats / AI_VTT / NEXO
  2. 02

    Backend & integrations

    APIs and adapters that isolate the domain from messaging, payments and native infrastructure.

    • .NET 10
    • Fastify
    • Node.js
    • ASP.NET Core
    Renaissance / Auto Whats / Castle Wars
  3. 03

    Data & realtime

    Relational state, caching, events and synchronization selected for consistency and use case.

    • PostgreSQL
    • Redis
    • ClickHouse
    • Socket.IO
    five state strategies across the lab
  4. 04

    Applied AI

    Models inside policies, with controlled context, fallbacks and a human in the loop.

    • Agents
    • Voice AI
    • Automation
    • Guardrails
    Auto Whats / AI_VTT / ERP

CORE. 03 / WHAT DOES NOT CHANGE

Mysterious,
not artificial.

  1. 01

    Anonymity without a character.

    The face stays out. Decisions, routines, costs, wins and mistakes remain part of the story.

  2. 02

    Competence without posturing.

    There is no guru here. There is one person learning quickly, building and owning the outcome.

  3. 03

    AI as leverage.

    Agents and models expand execution. Curation, responsibility and taste remain human.

OPERATING SYSTEM. 04 / HOW THE WORK MOVES

Less ceremony.
More signal.

A cycle short enough to learn early and rigorous enough not to confuse speed with improvisation.

  1. 01

    Frame the problem

    Hypothesis, user, risk and the smallest signal worth observing.

  2. 02

    Draw boundaries

    Domain at the center; integrations, models and infrastructure at the edges.

  3. 03

    Ship a vertical slice

    An operable end-to-end flow before the complete platform.

  4. 04

    Observe and iterate

    Telemetry, real use, documented failures and the next decision.

RECRUITER LENS. 04 / WHAT CAN BE EVALUATED

No inflated résumé.
Concrete signals instead.

  1. A

    System design

    Boundaries, state, security and trade-offs are visible in the case files.

    Open technical map
  2. B

    Delivery capability

    Two public products and five labs with declared stages and gaps.

    View experiments
  3. C

    Product judgment

    Every system starts with a question and makes the next required signal explicit.

    Read the manifesto
  4. D

    Technical communication

    Decisions and lessons become readable records, not only private code.

    Open field notes

PROTECTED IDENTITY / OPEN ENGINEERING

The name stays hidden.
The technical signal does not.

See what I am building