01
Technical Leadership
Lead technically complex initiatives from architecture through production. Create clarity from ambiguity, set direction, and keep engineering decisions aligned with product and operational goals.
Yeradis Barbosa Marrero
Senior Software Engineer · Technical Leader
I build products. I lead the engineering behind them.
I turn user problems into working products, design and evolve production systems, and lead technically complex work from the first decision to how it behaves in production.
01 / CONTRIBUTION
Engineering beyond the implementation.
I connect product goals with technical direction and hands-on delivery: system design, coordination across teams, and helping engineers build and operate software with confidence.
02
Systems & Architecture
Build services that stay correct when their dependencies fail: delivery guarantees, backpressure, and retries that don't amplify outages. APIs, integrations, and asynchronous workflows designed to be observable and maintainable.
03
Cross-Team Execution
Work across engineering, infrastructure, security, operations, and product boundaries to resolve dependencies and move initiatives from design to production without losing technical integrity.
04
Engineering Enablement
Scale impact through mentoring, reviews, documentation, reusable patterns, automation, and knowledge sharing, reducing dependency on individual experts and increasing team autonomy.
02 / APPROACH
From user problem to production.
I take responsibility across the full product loop, working with product, design, and engineering, from understanding the problem to learning from what we ship.
01
Frame the problem
Understand the user problem, question assumptions, and define the metric that will show whether the work succeeded.
02
Choose what to build
Prioritize the work that can change the result. Make product and technical trade-offs explicit, including what to leave out.
03
Build across the stack
Design and implement the complete solution. Break complexity into tractable work and coordinate dependencies without losing sight of the user problem.
04
Ship and own production
Deliver with testing, observability, resilience, and operational readiness built in. Own how the product behaves once people use it.
05
Measure and iterate
Shipping is a starting point. Use metrics and user feedback to decide what to refine, rethink, or stop, and share the learning with the team.
PRINCIPLES
Make trade-offs explicit.
There is rarely one universally correct architecture. Good decisions make constraints, costs, and consequences visible.
Stay close to the system.
Technical leadership is stronger when grounded in designing, coding, reviewing, debugging, testing, and operating real software, and accountable for what ships, whoever or whatever wrote the first draft or reviewed it.
Optimize the team, too.
A solution has more value when it improves how other engineers reason, execute, and operate independently.
03 / TOOLKIT
Product thinking. Engineering depth.
More than two decades building software across backend, mobile, frontend, cloud, and infrastructure. The work starts with the problem; technologies are implementation choices.
Product Engineering
Engineering organized around the problem being solved.
Problem discovery · Prioritization · Product and technical trade-offs · End-to-end delivery · Experimentation · Product metrics
Architecture & Backend
Design services and APIs with clear boundaries, pragmatic trade-offs, and room to evolve as the product grows.
Java · Kotlin · Spring Boot · APIs · distributed systems · asynchronous processing
Data & Integration
Model data and connect systems with attention to consistency, delivery guarantees, and recovery when dependencies fail.
PostgreSQL · Redis · MongoDB · RabbitMQ · Pub/Sub · event-driven architecture · system integration
Reliability & Platform
Understand system behavior, investigate bottlenecks, and build the delivery workflows that let teams operate production with confidence.
Observability · OpenTelemetry · Prometheus · performance · concurrency · resilience · Docker · Terraform · OpenShift · CI/CD
Engineering Quality
Verification that holds regardless of who or what wrote or reviewed the code: deterministic gates first, human and AI review on top.
Automated testing · Testcontainers · mutation testing · static analysis · code review · quality gates
AI-Native Engineering
Specify intent, delegate to agents, verify independently.
I shape codebases and pipelines that coding agents can work in safely: clear boundaries, machine-verifiable gates, scoped permissions. I decide what can run unattended, verify what comes back, and stay accountable for what ships.
Coding agents · Agent workflows · Context and prompt engineering · MCP and tool integration · Evals
Also worked with: Python · Go · TypeScript · React · native Android and iOS · AWS · GCP · Azure
Build software that works. Build systems that last. Build teams that can do both.
Let's connect
Complex systems deserve clear thinking.
Let's talk about product engineering, technical leadership, or making complex systems easier to build and operate. Connect with me on LinkedIn.