Jonatas Pedraza

• Evolving the credit platform (offering, management, and operations) across backend and frontend
• Integrating partner APIs into the credit engine (analysis and approval flows)
• Building the credit frontend with React, TypeScript, Figma, and Playwright
• Shipping back-office tools for a lean product/design/operations squad
• Investigating production incidents with Datadog (metrics, logs, root cause)

At Nuvemshop I evolve the credit platform — from offering and management through day-to-day operations. The work spans backend and frontend: I build scalable, reliable features, integrate partner APIs for the credit engine (system communication, data exchange, and automation of analysis and approval), and develop the credit frontend with React, TypeScript, Figma, and Playwright alongside design. In a lean squad with product, design, and operations, I also ship internal back-office tools that improve processes and speed up value delivery. When production breaks, I investigate with Datadog (metrics, logs, and root cause) and use generative AI tools as leverage in the development workflow — while still owning quality and what reaches the user.

TypeScript · Node.js · React · Figma · Playwright · PostgreSQL · Redis · AWS · Datadog

• AWS solution architecture for food-delivery microservices (NestJS/Node.js/TypeScript, plus services in Go and Python), covering compute (ECS/Fargate, EC2), APIs (API Gateway, ALB), data (RDS, ElastiCache), messaging (SQS/SNS), S3, IAM, VPC, and CloudWatch
• Created and evolved CI/CD pipelines with GitHub Actions (build, test, and deploy)
• Translated business requirements into solution decisions: service boundaries, API contracts, persistence, and cost/performance/security trade-offs
• Architecture specs, diagrams, and guides to steer implementation and platform evolution
• Technical standards and tech-lead support (code, CI/CD, agile practices) for coherence across squads
• Hands-on in critical squads with legacy systems and complex integrations, unblocking delivery without breaking the target architecture
• Composed data and runtime stack (PostgreSQL/RDS, MongoDB, Redis/ElastiCache, Elasticsearch, Docker) aligned to domain load patterns

As Software Architect at Delivery Much Brasil, I designed and led cloud solutions for food delivery as microservices on AWS, connecting business requirements to end-to-end architecture decisions: service boundaries, API contracts, persistence, and trade-offs across scale, performance, security, reliability, and cost. On the AWS platform I guided design around container compute and orchestration (ECS/Fargate and EC2 when it made sense), API exposure (API Gateway, ALB), managed data (RDS/PostgreSQL, ElastiCache/Redis, plus MongoDB and Elasticsearch in the solution ecosystem), messaging and decoupling (SQS/SNS), storage and artifacts (S3), identity and access (IAM), and observability (CloudWatch) — always with attention to networking (VPC, subnets, security groups) and continuous delivery. I created and evolved CI/CD pipelines with GitHub Actions to automate build, test, and deploy, reducing friction from code to production. I acted as the bridge between product and engineering — interviews, refinements, and stakeholder alignment — producing specs, diagrams, and guides to steer implementation and platform evolution. I defined and supported technical standards for teams (code, CI/CD, and agile practices), enabling tech leads to keep architectural coherence across squads. In critical moments I joined squads hands-on with legacy systems and complex integrations, unblocking high-priority deliveries without losing alignment to the target AWS architecture.

NestJS · Node.js · TypeScript · Go · Python · Docker · AWS · ECS · Fargate · EC2 · API Gateway · ALB · RDS · ElastiCache · SQS · SNS · S3 · IAM · VPC · CloudWatch · GitHub Actions · MongoDB · PostgreSQL · Redis · Elasticsearch

• SRE on online payment systems focused on availability and scale
• Architecture and infrastructure evolution for distributed applications
• Elasticsearch cluster design and operations with squad support: redesigned the read-layer cluster (dedicated nodes per workload, following Elastic best practices), cutting read-layer incidents by ~85%
• Automated provisioning and delivery with Terraform, Packer, Ansible, and Docker on AWS

On Pagar.me’s SRE team I worked on online payment systems under real availability and scale pressure. Day to day mixed architecture, development, and infrastructure evolution for distributed applications — including supporting squads on Elasticsearch cluster design and operations. I automated provisioning and delivery with Terraform, Packer, Ansible, and Docker on AWS, always aiming at the same outcomes: performance, reliability, and room to grow without production surprises.

Python · JavaScript · Go · C# · AWS · Terraform · Packer · Ansible · Docker

• Standardized and automated systems-infrastructure provisioning in operator on-prem datacenters (Packer, Ansible, Shell, SSH, Linux), cutting the cycle from ~168 h to ~48 h
• Site operational readiness: integration and delivery of Nokia solutions on heterogeneous stacks, focused on repeatability, risk reduction, and time-to-ready
• Defined and executed datacenter network standards (VLANs, switches, ports, rack topology) when the site had no dedicated networking team
• Coordinated with the vendor (Dell PowerEdge rack/blade) on physical expansion/sizing aligned to service capacity demand
• Field operational-architecture documentation: MOPs, runbooks, installation/commissioning checklists, topology diagrams, and validation/rollback plans
• OpenShift and OpenStack as the environment’s orchestration/virtualization foundation
• IoT integrations and ETL pipelines (Greenplum, MySQL) for operational data flows

At Nokia Networks I worked as a System Integration Engineer in on-prem datacenters for telecom operators, with end-to-end ownership of systems-infrastructure readiness and delivery: from defining the provisioning standard through on-site operational validation. I worked in corporate environments with rack/blade servers (Dell PowerEdge), datacenter networking, and heterogeneous stacks, designing and automating Nokia solution rollout with Packer, Ansible, Shell Script, SSH, and Linux — cutting the provisioning cycle from ~168 h (~7 days) to ~48 h (~2 days). When a site had no dedicated networking team, I led with the team the datacenter network provisioning (switches, ports, VLANs, and rack topology); physical expansion and hardware sizing were often executed by the vendor’s technical team, aligned to capacity requirements and service demand. Orchestration/virtualization in that project context was based on OpenShift (Red Hat) and OpenStack. With the team I produced field technical documentation — MOPs (Methods of Procedure), runbooks, installation and commissioning checklists, topology diagrams, and validation/rollback plans — to standardize execution, reduce operational risk, and ensure repeatability across sites. I also took part in IoT integrations and ETL pipelines (Greenplum and MySQL) connecting data sources to operational flows.

Packer · Ansible · Shell Script · SSH · Linux · OpenShift · OpenStack · MySQL · Greenplum · Elasticsearch · Git

• Backend services and APIs for live and on-demand video delivery
• Focused on performance, scale, and resilience in microservices
• Built AI agents to detect video transmission failures; ~35% of open tickets were of that type, and with the agents we brought that share down to nearly zero
• Improved CI/CD pipelines with the DevOps team

On Globo.com’s video platform I built and maintained backend services and APIs for live and on-demand delivery, focused on performance, scale, and resilience — where latency and stability truly matter. I also contributed to DevOps on automating and improving CI/CD pipeline efficiency, shortening the path from code to production. The work spanned microservices and distributed systems, with a data, cache, and load-balancing stack (PostgreSQL, MongoDB, Redis, Elasticsearch, Nginx) on top of Python, Node.js, and Docker.

Python · Node.js · JavaScript · Redis · Docker · PostgreSQL · MongoDB · Elasticsearch · Nginx

• Data-acquisition services for distributed Big Data systems
• Automation and continuous delivery/deployment pipelines on AWS
• Node.js stack with MySQL, PostgreSQL, MongoDB, and Redis

At Neemu I worked on the Big Data team building data-acquisition services for scalable, distributed systems — foundations that must absorb volume without losing reliability. I also joined DevOps, automating routines, improving continuous delivery/deployment pipelines, and managing AWS resources. Day to day mixed Node.js and JavaScript with MySQL, PostgreSQL, MongoDB, and Redis, plus Shell Script on Linux, Docker, and Git. I applied microservices, design patterns, and cloud practices so performance, scale, and maintainability stayed at the center of the decisions.

Node.js · JavaScript · MySQL · PostgreSQL · MongoDB · Redis · Docker · AWS · Shell Script

• Scalable REST APIs and backend services on the Cloud & Backend team
• Mobile applications and MySQL integration
• Linux automation with Shell Script and agile practices (Scrum)

At INdT (Nokia Institute of Technology) I was on the Cloud & Backend team developing backend services and mobile applications. I built scalable REST APIs integrated with MySQL, using Node.js, JavaScript, Java, and C++ depending on the problem. Development and production ran on Linux, with heavy Shell Script use for automation. Projects demanded close collaboration with other teams, agile practices with Scrum, and continuous improvement of architecture and processes — with Git and design patterns keeping the codebase maintainable.

Node.js · JavaScript · Java · C++ · MySQL · Linux · Shell Script · Git