Senior QA Automation Engineer · SDET · Williamsburg, OH
I help teams build reliable software by embedding quality into the development process—not just testing it at the end.
Extensive experience building automated testing solutions for complex software systems. Expert in UI and API automation with deep experience integrating automation into CI/CD pipelines — and increasingly, using AI-assisted workflows to accelerate everything.
I’m currently exploring part-time and freelance opportunities, where I can help teams improve test coverage, reduce manual testing, and speed up releases.
The projects in my Github are personal and sample projects created to demonstrate my approach to automation and framework design.
// 01 — core competencies
// tools & technologies
// 02 — professional experience
Built early Selenium frameworks, introduced BDD practices, reduced regression suites from weeks to days, and implemented keyword-driven automation strategies.
// 03 — how i can help
I'm especially interested in working with small teams or startups that need a few hours of QA support per week. I can come in for just a few hours and make a meaningful improvement
// 04 — my qa philosophy
I believe software quality assurance is more than just executing test cases or verifying expected outputs. Quality starts with people—how we collaborate, communicate, design our processes, and continuously learn from both success and failure. When these elements are strong, quality becomes a natural outcome rather than a final checkpoint.
Throughout my experience across multiple teams, the most successful environments have been small, autonomous teams practicing true Agile principles. In these teams, everyone contributes to requirements gathering, design, estimation, and architectural decisions. This shared ownership creates clarity around the problem we are solving and alignment on how we plan to solve it.
During implementation, the team works iteratively in small, testable increments. QA stays closely aligned with development, often preparing test scenarios and automation alongside feature design. When issues arise, collaboration with developers is immediate, allowing for rapid clarification and resolution—often within minutes or hours rather than days.
I strongly advocate for a grey-box testing approach, where QA goes beyond the user interface to understand the underlying architecture, APIs, and system behavior. This approach helps identify risks earlier, ensures the right tools and patterns are being used, and improves overall system reliability as the software evolves.
As features progress toward completion, validation continues through user acceptance testing, demos, and stakeholder feedback. I view this as a continuous refinement process—what I refer to as the "Quality Filter." At each stage of the development lifecycle, assumptions are validated, requirements are clarified, and the solution is improved through feedback.
By the time software reaches production, it has been shaped and verified through multiple layers of collaboration and validation. While no system is ever completely free of defects, this approach significantly reduces risk and leads to more stable, reliable, and maintainable products.
This philosophy guides how I approach both full-time and part-time engagements, focusing on delivering meaningful quality improvements even in small increments.
// 05 — let's connect
Interested in part-time or project-based QA automation help?
Feel free to reach out — I'm happy to chat or take a look at your current setup.