Skip to content
Bruno Ferreira

Senior Backend Engineer

I build backend systems that stay correct when concurrency, money, failures, and production reality show up.

I’m a Senior Backend Engineer focused on TypeScript, Node.js, PostgreSQL, system design, and production readiness. I turn architecture decisions into verifiable code, tests, operational evidence, and explicit trade-offs.

View ProjectsView GitHub
Bruno Ferreira smiling on a wooden outdoor deck, wearing glasses and a white T-shirt.

Core stack & systems I work with

Trusted by TypeScript, Node.js, PostgreSQL, Docker, GitHub Actions, OpenAPI, Prisma, k6, AWS, Redis, Kafka, AI Engineering

(01) About

Backend-first engineering for systems where correctness, recovery, and operability matter.

I’m a software engineer with 8+ years of experience building and leading delivery of scalable systems, from full-stack implementation to development management. My professional background spans APIs, distributed systems, omnichannel platforms, CRM, automation, mobile applications, and production integrations.

I work closest to the parts of software where small mistakes become expensive: data consistency, API contracts, concurrency, authentication, payments, integrations, and production failure modes. My approach is evidence-driven, and I use AI aggressively to accelerate engineering while keeping requirements, trade-offs, verification, and final ownership human.

8+ years
Professional experience
Backend
Primary axis
System Design
Architecture
AI-native
Engineering workflow

(02) Engineering Case Studies

Systems, trade-offs, and evidence you can inspect.

(03) Professional Experience

From implementation to technical leadership.

JUL 2019 — PRESENT

Development Manager — Ubicua

Leading software projects focused on automation, customer experience, and omnichannel solutions, including WhatsApp-integrated platforms and Dialogflow conversational flows. Owns delivery from requirements analysis through execution, stakeholder alignment, prioritization, quality, and coordination across product, design, and engineering. Coordinates multiple concurrent initiatives spanning CRM, BI, mobile applications, and RPA.

Leadership · SDLC · Omnichannel · CRM · BI · RPA

JUN 2017 — JUL 2019

Full Stack Developer — Ubicua

Built full-stack solutions for automation and customer experience, including omnichannel service platforms integrated with the official WhatsApp API and Dialogflow. Worked across CRM, dashboards and BI, iOS/Android applications, marketplace and gamification features, REST API integrations, RPA, SMS campaigns, and evolutionary maintenance of production systems.

REST APIs · WhatsApp · Dialogflow · CRM · Mobile · RPA

(04) Technical Surface

Capabilities first. Tools second.

Backend & Runtime

  • TypeScript
  • Node.js
  • Express

Data & Consistency

  • PostgreSQL
  • Prisma
  • Redis

Distributed Systems

  • Kafka
  • Messaging
  • Caching
  • Idempotency

Production Engineering

  • Docker
  • GitHub Actions
  • OpenAPI
  • k6
  • AWS

(05) Engineering Evidence

Claims should be one click away from proof.

Neon Arsenal ADRs

Architecture decisions covering order idempotency, webhook reliability, OpenTelemetry, hot-path indexes, seller ledger design, transactional outbox, pagination, and other production concerns.

Architecture · Reliability · Data consistency

Inspect ADRs

Load-test evidence

The reproducible CI workflow behind the Neon Arsenal catalog performance claim, including the controlled test topology and repeated k6 execution.

k6 · GitHub Actions · Performance

Inspect workflow

Portfolio engineering decisions

ADRs for this site covering the App Router, server/client boundaries, content modules, design tokens, image handling, animation strategy, and publishing workflow.

Next.js · ADRs · AI-assisted delivery

Inspect ADRs

(06) Engineering Principles

  • Correctness is a feature. Concurrency, retries, duplicated requests, and partial failure should be modeled before production forces the lesson. — Correctness first, Concurrency · Idempotency, Backend
  • External systems fail in inconvenient ways. Reliable software needs a path back to a valid state, not just a successful happy path. — Design for recovery, Retries · Reconciliation, Reliability
  • A technical claim becomes useful when someone else can inspect or reproduce it. Tests, contracts, traces, benchmarks, and ADRs turn confidence into evidence. — Evidence over claims, Tests · Observability · Load, Operations

(07) FAQ

How I think about engineering.

Backend-first. I focus on APIs, data consistency, system design, integrations, reliability, and the production behavior behind business-critical workflows.

Correctness first, then maintainability and operability. I prefer explicit invariants, measurable evidence, and simple architectures that can evolve when real requirements justify more complexity.

Skeptically. Queues, caches, event streams, and service boundaries are tools, not seniority badges. I add them when scale, isolation, latency, ownership, or failure recovery makes the trade-off worthwhile.

As an implementation and review accelerator. Agents can write, investigate, test, and challenge ideas, but requirements, architecture, trade-offs, verification, and final acceptance remain human-owned.

Start with Neon Arsenal for backend correctness, payments, failure recovery, observability, and performance evidence. Team Scrapbook shows real-time and integration breadth; Pokédex 98 Agent shows product-oriented AI integration.