Experience & method

Quality engineering

I design quality practices around risk, feedback speed, and diagnosability. The goal is not simply to create more tests; it is to create trustworthy signals that help engineers make better release decisions. Areas I work across:

• Test strategy and risk-based validation
• Service, API, UI, and mobile automation
• Regression prevention and release confidence
• Failure analysis and actionable diagnostics
• Test framework design and long-term maintainability

Engineering strengths

Automation

I build automation that is readable, deterministic, and useful when it fails. Good automation should shorten the path from a failure to a clear fix.

Systems thinking

I work across application code, APIs, infrastructure, networking, and runtime operations instead of treating quality as a final-stage activity.

Developer productivity

I create practical tools and workflows that reduce repetitive work, improve feedback loops, and make complex systems easier to operate.

Reliability

I focus on timeouts, failure boundaries, observability, safe deployment paths, and operational behavior under real-world conditions.

AI agent engineering

I design agents as engineering systems rather than opaque chat experiences: clear tools, scoped instructions, reusable skills, operational rails, and evidence-driven outcomes.

Agent evaluation

I build deterministic evaluation around nondeterministic model behavior using curated ground truth, repeatable scenarios, structured verdicts, and explicit failure conditions.

Working principles

• Prefer fast, trustworthy feedback over noisy activity.
• Make failure output actionable for the person who has to fix it.
• Keep automation simple enough for the team to maintain.
• Treat deployment and operations as part of engineering quality.
• Generalize reusable patterns without hiding important edge cases.

At a glance