What motivates you to be a Cypress Ambassador?
What motivates me is the impact Cypress can have on how engineering teams think about quality. I have seen teams move from slow, fragile testing workflows into fast, reliable, developer-driven automation using Cypress. In my experience leading adoption in a large production environment, Cypress was not just a tool change, it helped create a cultural shift where testing became part of everyday development, feedback loops became faster, and teams gained more confidence in shipping. Being a Cypress Ambassador gives me a way to share those real-world lessons, help teams adopt Cypress effectively, and contribute to a community that is actively shaping the future of modern testing.
How do you currently help others that are either using Cypress or interested in using Cypress?
I help others by sharing practical experience from implementing Cypress in large applications and scaling it across teams. This includes mentoring engineers, running internal sessions, helping teams bootstrap Cypress, and sharing patterns for writing maintainable and reliable tests. Beyond that, I actively contribute through technical writing on platforms like DZone, HackerNoon, SitePoint, Medium, and Dev.to. Speaking at conferences and participate in the developer community is something I enjoy. Additionally, I build open source projects and npm libraries around testing, developer tooling, AI-assisted workflows, and modern TypeScript systems. For me, it is not just about teaching Cypress, it is about helping engineers build confidence in testing and making automation a natural part of their daily workflow.
What is your favorite Cypress feature?
Debugging is still my favorite part of Cypress. The ability to visually step through tests, inspect application state, and understand failures without guesswork is one of the reasons Cypress stands out. It makes testing feel much closer to how developers actually debug applications. Cypress Cloud and Test Replay make this even more powerful. Being able to debug CI failures with clear visibility into what happened during the run is incredibly valuable for teams working at scale. I am also excited about the newer AI and agentic debugging direction in Cypress, because it connects very well with how modern teams are starting to use AI to understand failures, improve tests, and speed up feedback loops.
What is your favorite "Cypress Best Practice" and why?
My favorite best practice is focusing on user-centric, isolated tests with stable selectors. In large applications, the biggest challenge is not just writing tests, it is maintaining them over time. Tests should reflect how users interact with the system, not internal implementation details. Using stable selectors, like data attributes, and keeping tests independent makes the suite more reliable, easier to debug, and easier to scale. This reduces flakiness and builds trust in the test suite, which is critical for continuous delivery.
Outside of work, what are your favorite things to do (hobbies, passions, etc.)?
Outside of work, I enjoy staying active through tennis, ping pong, running, and hiking. I also spend a lot of time building side projects and exploring ideas in web, mobile, AI, and developer tooling, contributing to open source, and mentoring engineers. For me, learning and building are continuous; whether it is experimenting with a new tool, creating a small application, or contributing back to the community, I enjoy staying hands-on.
What is one professional milestone you are proud of?
One milestone I am particularly proud of is introducing Cypress as a proof of concept around 2021 and helping it grow into a core part of automated testing and CI/CD workflows. What started as an experiment became a scalable automation strategy that reduced manual testing effort, improved developer productivity, and strengthened release confidence. Seeing that transformation, from early adoption to real engineering impact, has been one of the most meaningful experiences in my career.
For new users - what is the best way to "get started" with Cypress?
Start by building something small and learn by doing. Install Cypress, pick a simple application, and write a few basic tests. Focus on understanding how Cypress works: commands, assertions, selectors, network handling, and how it interacts with the browser. From there, keep experimenting: build small side projects, try different scenarios, break things, and learn how to debug. Today, AI can also help you learn faster by generating test ideas, explaining failures, or suggesting improvements, but treat it as a learning assistant, not a replacement for understanding. Consistency matters more than complexity.
What is your favorite quote or saying?
Keep building, keep learning, and don't stop when it gets hard. That is where real growth happens.