Curriculum Vitae

Professional ResumeOpen to Work

Here's my journey as a Senior Software Engineer and Engineering Lead. I've tackled complex technical challenges, mentored people, and built supportive, and healthy teams that deliver.

What drives me is the mix of problem-solving and collaboration, writing reliable code while creating an environment where people can do their best work. This resume brings together the skills, projects, and experiences that have shaped my career so far.

Last updated: September 2025 • PDF format • 3 pages

Download PDFView Online

Looking for an engineering leader?

I'm open to new opportunities — let's talk about what you're building.

Email me

Best Practices

I try to run my work like a system: clear outcomes, predictable execution, and a culture that makes quality the default.

Product and delivery

I start by aligning on the problem and success criteria before we build. I push for a clear definition of "what good looks like," a tight scope, and explicit trade-offs so the team isn't guessing. I prefer small, safe increments with short feedback loops, so we learn early and avoid shipping "technically correct but conceptually wrong" solutions.

Team and leadership

I rely on consistency: regular 1:1s, written context, and clear ownership. I invest in psychological safety and direct, yet kind and honest, feedback because it's the fastest way to build high-trust teams with standards. I'm intentional about growth: turning expectations into observable behaviors, creating opportunities, and sponsoring people so development isn't left to chance.

Engineering practices

I focus on maintainability and operational readiness. That means keeping changes small and reviewable, documenting important decisions, building guardrails that prevent common errors, and treating incidents as learning opportunities rather than blame. I also watch team health as a first-class signal: sustainable pace, reasonable WIP, and visible priorities—because long-term performance depends on energy, not heroics.

Overall, the best practice I care about most is clarity: clarity of intent, clarity of ownership, and clarity of what success means—for users, for the business, and for the team.

Leadership Style

I lead with people-first clarity and technical depth. Over the years, I've learned that high performance comes from psychological safety, ownership, and well-understood systems. My style blends inclusive, servant leadership with pragmatic engineering: set context, co-create standards, remove friction, and let great people do their best work.

What this looks like in practice

Intentional remote leadership

  • Clear goals, written context, and transparent decisions so no one is blocked by time zones.
  • Rituals that reinforce alignment: roadmap reviews, architecture forums, and predictable delivery cadences.

Coaching and growth

  • 1:1s as a safe space for development: career paths, feedback, and early signals of burnout or friction.
  • Fair distribution of high-impact work and sponsorship that makes talent visible.

Pragmatic technical leadership

  • Architectures that favor reliability, observability, and maintainability over accidental complexity.
  • Guardrails and standards (ADRs, code review norms, incident/postmortem quality) that balance speed and quality.

Outcome-driven delivery

  • Tight partnership with Product and Design to solve real user problems.
  • Focus on lead time, reliability, and execution clarity, not vanity metrics.

Inclusive by design

  • Diversity as a transversal practice: how we collaborate, give credit, assign projects, and honor different realities.
  • Accessible communication: agendas in advance, notes/recordings, clear language, and organized documentation.

Principles I live by

  • Clarity over control: Set context and constraints; empower teams to decide.
  • Fewer, better systems: Reduce complexity to make reliability repeatable.
  • Feedback as a habit: Make it frequent, specific, and growth-oriented.
  • Consistency > heroics: Reliable processes beat last-minute pushes.
  • Inclusion is operational: Design rituals and communication that welcome, hear, and reflect every voice in decisions.
  • Psychological safety: Enable candid debate, asking for help, and thoughtful risk-taking without fear of blame.

Favorite quote

"Culture eats strategy for breakfast." — Peter Drucker
Great strategies endure only when everyday behaviors make them real.

Experience

  • Over 15 years in software engineering
  • Led and scaled remote teams
  • Specialized in Elixir, Phoenix, and distributed systems
  • Built and scaled HR and EdTech platforms from scratch
  • Eng. leadership at Remote, Factorial HR & Lingokids

Education & Community