01 / THE DAY JOB

Good work makes a difference.

My favorite kind of testing helps a team see clearly, move faster, and feel confident about what they ship.

2 weeksmanual release-testing cycle before automation
8 hoursautomated run after the change
2018the year I started in software quality

SELECTED EXAMPLES

How I show up at work.

These examples come from my résumé. Screenshots can join them later.

01 — AUTOMATE THE REPEATABLE

Give people time back.

I designed C# automation suites that turned a two-week manual release-testing cycle into an eight-hour automated run. I used FlaUInspect and Visual Studio to build and maintain the tests.

That created more room for careful investigation and the testing that needs a human eye.

C#FlaUInspectVisual Studio
02 — INVESTIGATE TOGETHER

Find the thing that matters.

Detailed UI testing and close work with developers helped identify and resolve high-impact defects before release.

I bring clear reproduction steps and product context to the conversation, so the team can move from “something feels off” to a useful fix.

UI TestingDefect AnalysisTeamwork
03 — MAKE WORK EASIER TO FOLLOW

Bring the team along.

I led a migration from TFS to Jira and created test sets that made planning and tracking clearer for the team.

I also mentored QA teammates moving into Software Engineer in Test roles and built onboarding programs to improve test consistency.

JiraTFSMentoring

MY APPROACH

Ask. Explore.
Make it useful.

I like a good test plan, but I also like the question nobody has asked yet. My work blends automation, product knowledge, and conversations with the people building the software.

Recently, I’ve also used AI-assisted workflows and reusable Codex skills to prototype tools and speed up documentation and test planning, with human review along the way.

More about my background

LET'S TALK QUALITY

Have a problem worth solving?

Get in touch