Backend platforms
FastAPI, Node.js, TypeScript, PostgreSQL, authentication, queues, caching, internal tools, and service boundaries built around operational requirements.
I design backend systems, applied AI, automation, and API integrations for real operational environments — with traceable data flows, observable execution, and software that can keep evolving after deployment.
My work sits between backend engineering and day-to-day operations. I build software that connects platforms, moves data between systems, automates repetitive processes, and gives teams a clearer way to understand what is happening inside their workflows.
The architecture changes with the problem, but the priorities stay consistent: clear boundaries, reproducible execution, controlled failure modes, useful logs, and enough context to maintain the system without treating production behavior as a black box.
FastAPI, Node.js, TypeScript, PostgreSQL, authentication, queues, caching, internal tools, and service boundaries built around operational requirements.
REST APIs, OAuth, webhooks, ERP and CRM connections, idempotent ingestion, synchronization workers, and replayable data pipelines.
RAG, contextual assistants, multi-agent workflows, vector memory, controlled tool execution, fallback behavior, and observable AI processes.
Scheduled jobs, ETL, validation, reporting pipelines, dashboards, business rules, and workflows that replace repetitive manual operations.
The projects below are not isolated visual demos. They document implementation choices, data flows, system responsibilities, and the engineering constraints behind each build.
Multi-agent orchestration, Kanban execution, RAG knowledge, vector memory, local models, and real-time observability.
DATA / 02Replayable ingestion across operational APIs with normalization, idempotent identifiers, SQL persistence, and scheduled execution.
OPS / 03Autonomous paper trading with Kronos-base forecasts, portfolio risk limits, simulated execution, and a public dashboard.
AI / 04A contextual assistant using Cloudflare infrastructure, manual RAG, multilingual conversation, sessions, caching, and provider fallback.
The portfolio shows finished systems. The blog is where I expand the reasoning around them: backend patterns, APIs, automation, cloud infrastructure, developer tooling, applied AI, data workflows, and the practical decisions that appear while building and maintaining software.
Articles are used to document implementation details, explain technologies in context, compare approaches, and keep a public record of what I am testing or improving. The goal is useful technical material, not a second copy of the resume.
Open the blogI am Patrick Araujo, a Backend Software Engineer based in Belo Horizonte, Brazil. I work with backend platforms, internal systems, applied AI, integrations, data pipelines, automation, and cloud infrastructure. My professional work has involved systems used for operational, administrative, financial, inventory, reporting, and customer-service workflows.
This homepage is intentionally an overview. The About page contains the full professional timeline and stack, Projects contains implementation-specific material, and Certifications documents training and continued technical development.