About

Background

I’m a software engineer with a frontend focus, working across React, TypeScript, and modern web tooling, with experience spanning full-stack development and internal product work.

Much of my work has been on internal tools and early-stage systems—places where requirements are fuzzy, constraints matter, and design decisions need to hold up under change.

I’m most interested in work that sits at the intersection of engineering and product: building software that’s useful, understandable, and maintainable over time.

How I like to work

I value clarity over cleverness. I try to make decisions explicit, surface tradeoffs early, and leave systems easier to understand than I found them.

I work best in collaborative environments where engineers have ownership and are trusted to make judgment calls, not just execute tickets.

When things go wrong, I’m biased toward understanding the system and improving it—not assigning blame.

What I care about

• Quality: code that’s readable, testable, and durable
• Usability: interfaces that reduce cognitive load and explain themselves
• Integrity: honest communication about risks and tradeoffs
• Learning: improving systems and skills over time, not chasing novelty

What I’m drawn to

I’m most engaged by teams that care about maintainability, product clarity, and long-term outcomes.

I do my best work in environments with real constraints, open discussion of tradeoffs, and shared ownership of systems.