Backend Software Engineer · Node.js · TypeScript · AWS · Microservices

5+ years building financial systems, payment platforms and core banking services with a strong focus on reliability, observability, and clean architecture.

I’m a Backend Engineer working on core banking and billing for BanQi (digital bank) via Invillia.

I design, build, and evolve services that:

• Process millions of transactions per month (boletos, TED/PIX, payment webhooks).
• Run on AWS, leveraging event-driven architectures, retries and DLQs to keep high availability.
• Follow Domain-Driven Design (DDD), Clean Architecture, SOLID and TDD, with a strong focus on automated testing and observability.

Day to day, I work on:

• Node.js / NestJS / TypeScript microservices for financial and payment flows.
• Integrations with external partners and platforms (core banking, ledger, gateways, etc.).
• CI/CD pipelines, CloudWatch dashboards/alerts, DLQs and runbooks to reduce MTTR and recurring incidents.

Languages & Frameworks

• Node.js · TypeScript · Java
• NestJS · Spring Boot
• RESTful APIs · GraphQL

Cloud, Infra & Observability

• AWS: Lambda, API Gateway, S3, DynamoDB, EventBridge, SQS, SNS, CloudWatch
• Docker · Terraform
• Structured logging, metrics, dashboards, alerts, DLQ

Messaging & Data

• Kafka · RabbitMQ · Redis
• PostgreSQL · MongoDB

Engineering Practices

• Microservices · Event-driven architecture
• Domain-Driven Design (DDD) · Clean Architecture · SOLID
• TDD · Jest · Integration tests (including LocalStack)
• CI/CD with GitHub Actions (experience with Spacelift as well)

• Domain-first: model the business (payments, core banking, reconciliation) before thinking about controllers and endpoints.
• Testable & observable: services with meaningful tests, logs, and metrics — not black boxes in production.
• Resilient by design: timeouts, retries, idempotency, DLQs, and clear reprocessing flows.
• Clear contracts between teams: integration checklists, tracing, useful logs, and lightweight alignment rituals.

• Actively participate in code reviews, definition of standards, and helping teammates with architecture, testing, and AWS.
• Enjoy discussing DDD, Clean Architecture, event-driven systems, payments, and core banking.
• Always aiming to grow as an engineer (not just a “coder”), connecting technical decisions to real business impact.

If you want to talk about backend architecture, payments, DDD, testing, or AWS, feel free to reach out.