Highlights
Positioning
- Role: senior full-stack (front-end + back-end), platform/infra-leading when needed
- Strength: fast ramp-up in unfamiliar systems and messy legacy code
- Style: pragmatic, ship-focused, with a bias for boring reliability
How I work
- Turn “it’s random” into a repro: logs → traces → hypotheses → minimal fix
- Design for operability: monitoring, sane defaults, and clear failure modes
- Prefer small steps and good feedback loops (CI/CD, previews, quick rollbacks)
Proof (replace with your numbers)
- Example: Reduced a critical workflow from X steps to Y and cut time-on-task by Z%
- Example: Improved API p95 from Ams to Bms by fixing …
- Example: Built CI/CD for N services, enabling daily deploys with safe rollbacks
- Example: Untangled legacy subsystem … and removed … production incidents