Skip to content
Pedro Augusto
Pedro Augusto

I build the systems companies sit inside all day.

I'm Pedro Augusto, a full stack developer in Goiânia, Brazil. I started out checking records in a government system, moved on to web apps and Laravel APIs, and today I architect and write the AI-powered CRM that more than 200 clients use to sell — from the data model to the screen.

Work

Three systems in production. What I did on each, and what changed afterwards.

CRM MaquinIA screen

CRM MaquinIA

Grupo Máquina de Vendas, 2026

TypeScript, Node.js, Express, JWT, RBAC, PostgreSQL, React, Playwright

The business ran on spreadsheets, one per agent, no trace of a lead. I took on the system that replaced it and built both ends: a Node and Express API, JWT authentication with role-based access enforced inside PostgreSQL itself, typed queries through Kysely, a phased portfolio importer, and the AI layer that drives the conversation.

More than 200 clients use it daily. I covered the critical path with Playwright, API integration tests and tests against the database itself, because a permission bug here leaks one client's data into another's.

Closed source — it is the company's internal product.

D.A financial control screen

D.A — financial control

Own project, 2026

Next.js 16, React 19, TypeScript, Supabase, Zod, Vitest

An auction business tracked money across parallel spreadsheets, with no reliable history and everyone seeing everything. I built the app that took its place: Next.js 16 with Server Actions, role-based auth on Supabase with RLS, and Zod validation at every entry point — because bad data on the way in is what breaks the month-end close.

I worked in vertical slices, each shipped as a pull request and covered by Vitest with coverage reporting. It is the project where my process shows end to end, which is why the code is open.

Sites Renderer screen

Sites Renderer

Grupo Máquina de Vendas, 2026

Next.js, React, Mapbox, Zod, Testing Library, sharp

Every client wanted their own website, and maintaining dozens of near-identical projects was choking delivery. I wrote a Next.js engine that assembles a site from the client's own data: property search by region on Mapbox, forms validated with React Hook Form and Zod, images optimized through sharp, and fonts served from our own domain so the site opens fast on a phone.

One codebase now serves every client. What used to be a new project per contract became configuration.

Closed source — it is the company's internal product.

Path

From checking public records to owning a product's architecture.

  1. Jan 2026 — present

    Grupo Máquina de Vendas

    Mid-level software developer

    I own the architecture and development of the company's CRM, from the database to the interface. I wrote the Node and Express API with JWT authentication and role-based access enforced in PostgreSQL, built the AI layer that drives customer service, and structured queues and Redis caching so the system holds up as it grows.

    I lead the critical modules independently, writing System Design Documents before writing code. I standardized environments on Docker.

    Node.js, Express, TypeScript, PostgreSQL, Redis, Docker

  2. Jul 2025 — Jan 2026

    BecoDiagonal

    Junior software developer

    I built multi-user web applications in React and maintained the PHP and Laravel APIs behind them, with attention to security and response time. I worked the full cycle, from requirements to cloud deployment, and sat with product and clients to define what would be built.

    React, JavaScript, PHP, Laravel, REST

  3. Nov 2023 — Jul 2025

    Jucetins — Tocantins Board of Trade

    Intern

    Where I learned to take data seriously. I checked and corrected records in government systems, resolving inconsistencies across MySQL and MariaDB and supporting the people who used the internal platforms. This is where I understood the cost of wrong data, before I learned to write the system that prevents it.

    MySQL, MariaDB, SQL

Tools

What I use every day:

  • TypeScript
  • React
  • Next.js
  • Node.js
  • Express
  • NestJS
  • PostgreSQL
  • Docker

And what I've shipped to production before:

  • Redis
  • Supabase
  • Astro
  • Tailwind
  • Playwright
  • Vitest
  • PHP
  • Laravel
  • Python
  • MySQL

About

Education

BSc in Software Engineering

UNIALFA — Centro Universitário Alves Faria

2025 — 2029

Languages

  • Portuguese , native
  • English , technical, intermediate

I like working at both ends. Modelling the database and the business rules is as good a time as shipping the screen someone actually uses — and doing only half of it tends to make the other half worse.

I work in vertical slices: every piece arrives complete, with tests, through a pull request. That isn't rigour for its own sake. Systems with real users don't forgive sloppiness, and I've seen up close what one wrong record costs.

Let's talk

I'm open to full stack developer roles, remote or in Goiânia. Write to me.

panuness1010@gmail.com