Skip to content
Felipe Sousa

About

Fullstack Developer, frontend-focused: React, Next.js, TypeScript

Brasília, Brazil

Background

I started programming in 2015, studying Mechatronics Engineering at the University of Brasília, writing C for robots before writing JavaScript for browsers. I taught robotics in public schools, worked as an algorithms teaching assistant, and did undergraduate research on firmware and wireless communication for the joystick of a surgical robot.

That foundation led me into software. From October 2023 to October 2025 I was a Mid-level Fullstack Engineer (Pleno I), frontend-focused, at Algoricca Software Company, working on two SaaS products: Candidattus and Connexicco. I joined as the only frontend developer, chose the stack and started the frontend architecture, and stayed until the end of the contract.

Today I'm building the FelpsXP Ecosystem: my own modular platform where I apply what I've learned about architecture, identity and access, events and observability. One of its modules, FelpsXP Finance, is in production and in daily use, with isolation between households enforced by Row-Level Security in PostgreSQL. It's where my most recent experience lives, and where I'm consolidating a specialization in application security and identity management.

I like solving the hard problem, and leaving a record of why it was solved that way.

Current focus

  • Actively looking for a fullstack role, open to frontend or backend
  • Shipping the Hub's first public phase as real, live proof of work
  • Consolidating a specialization in IAM and application security
  • Studying the OWASP Top 10 and practicing algorithms on Beecrowd as a routine, building toward the AppSec track
  • Growing the FelpsXP Ecosystem as proof of platform architecture, not just a personal product

How I work

  • Decisions before code: anything costly to reverse becomes an ADR before it is built, with the alternatives considered and the consequences accepted.
  • Small, reviewed changes: one pull request per task, with Conventional Commits, validated on its preview before the merge.
  • Tests and controls on every pull request: unit tests, end-to-end tests with axe, CodeQL and gitleaks; OpenSSF Scorecard tracks the supply chain every week.
  • Security from the design: a STRIDE threat model, a strict CSP, security headers and Zod validation at the boundaries.
  • AI under written rules: I use Claude Code to draft, propose and explain, but architecture and merges are my decisions, as the repository’s AI.md describes.
  • Claims with proof: what this site says matches a verified fact or something the repository itself shows.

You can check it in this site's repository: the ADRs, AI.md, the pull requests.

Principles

  • Evidence over adjective
  • Public-first clarity
  • Systems thinking over isolated features
  • Architecture with product intent
  • Calibrated honesty: never inflate what is not yet confirmed

Where to go next