Skip to main content
// Work01/05

With a team03

Products I worked on with a team. Click an image to open the live site.

Corta-ai

SaaS for barbershopsIn pilot

A barbershop runs its schedule, billing and analytics in one product. Its clients book by chat.

corta-ai-barber.com.br
Corta Aí admin dashboard for the last 30 days: 92.48% occupancy, 90.2% completion rate, R$ 7,355.00 in revenue and a revenue chart over time.
demo data

Problem

A barbershop needs one place for schedule, clients and billing. Its clients and barbers already live in a chat.

Decision

I proposed it, validated it with the team and the PO, and built it on the automation base I designed as a Jr. The chat is one more way in.

What I did

  • Web admin
  • API
  • Roles
  • Billing
  • Analytics

StatusTwo barbershops are testing it.

  • OTP login, roles per barbershop
  • Schedule, services and cancellations
  • Daily billing: Pix, trial, grace period, block
  • Analytics by plan
  • Chat: fixed flows, an LLM for the rest
  • Self-hosted Evolution API, cheaper than Meta's
One API, two entry points
    • Web admin
    • Chat
  1. BFF
  2. NestJS API
  3. Schedule, billing, analytics
  • Next.js
  • NestJS
  • PostgreSQL
  • n8n
  • Pix billing
  • WhatsApp

Kaizen

Face access for condominium guests, the Atrium productIn development

Atrium opens the door for a guest only between check-in and check-out. The host sends a link on WhatsApp, the guest registers with a selfie, and the reader does the rest.

Problem

Access depends on hardware from several makers, each with its own protocol. Managers and residents just want the door to open.

Decision

I own the flow from registering a person to the door opening. I build it with the founder and the other partners.

What I did

  • Registration
  • Temporary access
  • Automatic events

StatusIn active development, with a public site.

  • Public site live
  • Team across Madrid, Mexico City and Brazil
  • Hikvision and Control iD readers
From registration to the door
  1. Person registered
  2. Temporary access
  3. Automatic events
    • Hikvision
    • Control iD
  4. Door opens
  • NestJS
  • Next.js
  • Prisma
  • Hikvision
  • Control iD

Aeon Audio landing and front end

Aeon Tech · built as a JrDelivered

I built the Aeon Audio landing page and most of the front end behind it: feedback, profiles and auth. Typed and tested, with an accessibility pass.

aeonaudio.com.br
Aeon Audio landing hero: a dark carousel slide with the word Connection in large type and the buttons to start and to understand the process.

Problem

Aeon Audio is a community for musical feedback. The MVP front end had to ship fast and stay safe to change.

Decision

I treated the front end as a product. The landing is its own piece, and the app is typed Next.js with its own components. One SoundCloud player stays mounted when the view toggles.

What I did

  • GSAP scroll animation
  • Parallax system
  • Kinetic text
  • Radix mobile menu
  • Tests with every feature

StatusLive at aeonaudio.com.br.

  • Landing: hero, manifesto, masterclass, events, story
  • Feedback with tag filters and search
  • Profiles and auth
  • Unit and behavior tests
  • Accessibility pass
  • Move to Tailwind v4
From form to player
  1. Form (React Hook Form + Zod)
  2. React Query
  3. API
  4. Feedback card
  5. SoundCloud player
  • Next.js
  • React
  • TypeScript
  • Tailwind
  • GSAP
  • React Query
  • Jest

On my own06

Most of these began as tools for my own routine. I like changing what is around me, and music works the same way. Many were built at night, when the ideas show up. Each image opens the live app, or the repository for a command-line tool.

— Web and apps

  • 04
    gym-stuff

    A workout assistant for the phone: one exercise at a time, set logging, an adjustable rest timer, and it works without a signal.

    Decision

    Write to the device first and sync later, so a missing signal never loses a workout. One tap per set, and only the current exercise on screen.

    • PWA
    • offline-first
    • Supabase
    • Vercel
  • 05
    SAERIX portfolio

    This site. Next.js 16 and React 19 with GSAP, in English and Portuguese. It holds two identities, the engineer page you are reading and SAERIX, the page for my music.

    Decision

    Keep the two identities apart. Each has its own voice, layout and motion, and neither borrows the tone of the other.

    • Next.js
    • TypeScript
    • GSAP
    • Tailwind
    • i18n
  • 06
    Como-Eles-Votaram

    A transparency tool to see how politicians voted, simply and clearly.

    Decision

    Prisma and tRPC keep the types from the database to the screen. It has tests, lint and typecheck scripts, and Husky and commitlint on every commit.

    • T3 Stack
    • Next.js
    • Prisma
    • tRPC
    • Jest

— Command line

  • 07
    matrix-rain

    Matrix rain for the terminal in Python and curses, now becoming a multi-mode visualizer. I run it like a product. Spec first, then tickets, TDD and review, all public.

    • Python
    • curses
    • TDD
  • 08
    lightsync
    private repo
    $ lightsync

    A local service that makes a smart bulb follow the screen and the music playing on the computer. It runs without the cloud and has four modes: screen sync, white, color and music.

    • Python
    • PipeWire
    • Tuya
// Stack02/05

Languages

  • TypeScript
  • JavaScript
  • Python

Front end

  • React
  • Next.js
  • Tailwind CSS
  • React Query
  • GSAP

Back end and data

  • Node.js
  • NestJS
  • FastAPI
  • PostgreSQL
  • Prisma
  • TypeORM
  • tRPC
  • Supabase

Automation & AI

  • AI agent orchestration
  • n8n
  • WhatsApp API
  • Chatbots

Quality & delivery

Used at work

  • Jest
  • Vitest
  • Playwright
  • JUnit
  • CI/CD
  • Docker

Daily tools

  • Linux
  • Neovim
  • Git
  • pnpm
  • Claude Code
// How I work03/05

Speak-driven development.

I talk, Claude asks, and the spec comes out of the conversation. It is not prompt engineering.

I talk

I describe the problem out loud, then answer Claude's questions the same way.

Then the same five steps, every time

01/grill-me

Grill the plan

One question at a time, each with a recommended answer, until no decision is left open.

Each repo keeps a CLAUDE.md and docs for the agent, so the context lives in git and not in my head.

Replay of a session: Claude asks where the origin story lives and recommends an answer, and I pick it.
  1. 01

    Align on the whole

    I ask before I code. The team and the PO share one vision before the first ticket.

  2. 02

    AI executes, I direct

    It researches and executes faster than I do, and it flags risks early. But it has bias and does not always show every option. The mental model and the questions stay mine.

  3. 03

    Prove it in the open

    Spec, tickets, TDD and review in a public repository. Anyone can check.

  4. 04

    Speak up when something is off

    In the payments module and see an auth problem elsewhere? I say so, and since code is cheap now, I fix it or write it up right then.

matrix-rain: spec #14, tickets #15 to #22, 15 merged PRs and unit tests.

Read spec #14 ↗
  • >80%test coverage on Aeon Tech's product
  • CI/CDwith pre-commit hooks
  • Mentoringan intern, with a structured plan
  • Java in high school

    Through Alura, pulled in by Minecraft.

  • Exams on paper

    Data structures on paper, Java in Notepad.

  • The whole in my head

    I started college before AI wrote code. Typing is the fast part now.

ADHD, as a strength

Hyperfocus keeps the mental model loaded. I follow the logs, a deploy and a merge while I talk to Claude, and still answer a message in the gap.

Keyboard first

H → tile left

  • MetaH J K Ltile the window
  • MetaAltH J K Lswitch window
  • MetaShiftH Lsend it to another screen

My KDE shortcuts follow Vim and tiling window managers, so I move between windows and screens without the mouse. I keep many things open at once and know the whole system, so I can document one bug while I fix another. Neovim, in kitty, with fish and starship.

Built on Matt Pocock's open-source skills, plus a few of my own. ↗
// Path04/05
  1. SchoolAlura

    Java, because of Minecraft

    The state of Paraná gave students access to Alura. I wanted to change what was around me with code.

    • Java
  2. 2022UTFPR + TCSIntern

    College and a first job, before ChatGPT

    First job in June, degree in July. I made class assignments bigger, with console menus and ASCII art. At work I touched front end, back end, tests and Scrum.

    • Java
    • Tests
    • Scrum
  3. 2023TCSAnalyst

    Night on-call

    Critical systems of a large retail chain. In incident war rooms I was the technical link between engineering and managers.

    • Incidents
  4. 2024Aeon TechJr

    Rebuilt the product

    A team of four to five. I delivered the front end, with feedback, profiles, auth and the landing page, plus a self-hosted WhatsApp automation base.

    • Next.js
    • React
    • GSAP
    • n8n
  5. 2026Aeon Tech + KaizenMid-levelcurrent

    Corta-ai and Atrium

    Mid-level at Aeon Tech since March, on Corta-ai across web, API, billing and analytics. Partner-dev at Kaizen, on Atrium.

    • NestJS
    • Next.js
    • Prisma
    • PostgreSQL

I like understanding how technology works underneath. It is the closest thing to magic we have: with a computer and an idea, I can change what is around me.

// Contact05/05

Open to work as a mid-level full-stack engineer.

Londrina, Brazil · Portuguese native · English: EF SET 72/100

Sérgio Alexandre — Full-Stack Software Engineer