What motivates you to be a Cypress Ambassador?
I see being an Ambassador as the ultimate form of asynchronous collaboration. My goal is to share things that move the needle for other engineers. By comparing how different teams solve the same testing problems, we can turn isolated project victories into shared wins.
How do you currently help others that are either using Cypress or interested in using Cypress?
I'm the person teammates ping when a test goes flaky or they're not sure how to approach a complex scenario. I always try to answer with a reusable pattern rather than a one-off fix so the knowledge scales past me. A lot of that is helping people pick selectors that survive a redesign, semantic and stable, over cosmetic and brittle.
What is your favorite Cypress feature?
cy.intercept(). It's the ultimate tool for eliminating flake caused by unstable backend environments or slow APIs. Being able to intercept, modify, or stub network traffic means you can test frontend behavior under any condition imaginable, instantly. It guarantees your tests are deterministic, isolated, and entirely repeatable.
What is your favorite "Cypress Best Practice" and why?
Never using arbitrary cy.wait(ms). Hard waits are a confession that you don't trust your tooling. They either slow every run down or paper over a real race condition. Leaning on retry-ability and cy.intercept() aliases instead means the suite waits exactly as long as it needs to, no more, no less.
Outside of work, what are your favorite things to do (hobbies, passions, etc.)?
Catching FIFA World Cup matches with friends. It's the perfect way to unwind and watch a defensive line get tested for a change, instead of my own automation suite.
What is one professional milestone you are proud of?
Building stable automation frameworks from scratch and successfully scaling that knowledge across large, cross-functional teams. Throughout my career, my favorite milestones haven't just been writing clean architectural patterns, but leading training sessions for 20+ engineers and clients to get them comfortable with test automation. Demystifying complex testing concepts and giving teams the leverage to confidently own their builds is exactly what drives me.
For new users - what is the best way to "get started" with Cypress?
Skip the boring configuration routines. Just run npm install cypress, open the runner, and write a real test against your actual app: visit a page, fill a form, submit, and assert the result. Letting the native retry-ability handle the async waiting while watching it interact with your live, real-world codebase is the absolute fastest way to make the framework click.
What is your favorite quote or saying?
"It works on my machine."