JONH O DEV
GITHUBLINKEDIN

JONATHAN FARIAS

SOFTWARE ENGINEERFULL-STACKDEVOPS

SYSTEMS ONLINE

SYSTEMS
BUILT
END TO END.

Projects spanning interfaces, backend, infrastructure, and hardware — presented without exposing private code or sensitive details.

Seraphine

Local multimodal assistant

A personal interface combining local models, voice, a browser-based 3D avatar, persistent memory, and human-confirmed tool access.

  • Local AI
  • Voice
  • 3D Web
  • Memory

ESPMusic

Distributed home audio

A multi-room audio system built with ESP32 devices, Python services, real-time communication, and a control PWA.

  • ESP32
  • FastAPI
  • WebSocket
  • React PWA

Seraphine Firmware

Embedded audio streaming

ESP-IDF firmware that receives PCM audio from a home server over TCP and sends it through I²S, with persistent reconnection for embedded installation.

  • ESP-IDF
  • TCP
  • I²S
  • Embedded

ArquitetoHub

AI-assisted construction management

VIEW LIVE

A SaaS product for architects where a photo of an invoice becomes classified items and updates the project budget, with human review and spending views by stage and supplier.

  • React 19
  • Fastify
  • Prisma
  • MySQL

I BUILD THE
ENTIRE SYSTEM.

I’m Jonathan Farias — a software engineer, full-stack developer, and DevOps engineer. I work between the product people use and the infrastructure that keeps it alive.

I turn complex moving parts into clear, reliable experiences designed to evolve.

PRODUCTEXPERIENCE
APPLICATIONLOGIC
INFRASTRUCTURERELIABILITY
DEVICESIGNAL

STACK IS
ARCHITECTURE,
NOT A LIST.

I choose tools for the role they play in the system. Technology changes; clarity, observability, and reliability remain.

JONHBUILDING
SYSTEMS
Interfaces

React · Astro · TypeScript · PWA · WebGL

Systems

Python · FastAPI · Node.js · APIs · WebSocket

Infrastructure

Linux · Docker · CI/CD · Observability · Networks

Embedded

ESP32 · ESP-IDF · C/C++ · I²S · TCP

CODE IS JUST
ONE OF THE LAYERS.

A strong product also needs clear decisions, sustainable operations, and attention to what happens after deployment.

  1. 01

    Understand the system. Before choosing a tool, understand the flow: people, data, risks, and constraints.

  2. 02

    Build with evidence. Interfaces, logs, and metrics should make system behavior visible.

  3. 03

    Operate with confidence. Delivery includes automation, observability, recovery, and evolution.

LET’S BUILD
SOMETHING THAT
TRULY WORKS.

VIEW GITHUBCONNECT ON LINKEDIN