Meet Our Team

Avery started writing troubleshooting notes while working in IT support, where 'it works on my machine' rarely meant the issue was gone. That job turned into a long-running habit: reproduce the failure, isolate the layer, and write down the exact steps that make the result change.

After moving into web engineering and performance work, Avery kept running into the same problem from a different angle. Teams built great products, but basic device and browser signals were hard to explain when something failed in the field. A GPU path can fall back, a permission can be denied once and stick, or a policy can block an API with no visible error.

TestYourBrowser was created to make those signals visible. Avery focuses on tools and guides that you can verify in under a minute, with clear 'before/after' checks and links to primary documentation.

Dana has spent most of her career in the space between 'support ticket' and 'engineering fix.' She started on a help desk, moved into QA, and then owned internal runbooks for diagnosing browser and device issues across a wide range of machines.

That background shapes how Dana edits. Every guide must work when you follow it on a locked-down work laptop, a personal Mac, or a phone on hotel Wi-Fi. If a step depends on a specific browser UI label, Dana rewrites it until it matches what people see today.

Dana also maintains the 'checklist' style guides. These are written for speed. You match the symptom, run the test, apply the smallest change, and verify the result immediately.

Noah writes the guides that sit at the intersection of privacy settings and day-to-day usability. Many browser 'breakages' are side effects of a privacy control working as designed. Third-party cookies get blocked, storage becomes partitioned, and permission prompts get suppressed after repeated denials.

Before joining the editorial team, Noah worked on internal security reviews for web apps and helped support teams triage login, SSO, and embedded-widget failures. The patterns repeat across vendors, which makes them good candidates for clear, test-driven guides.

Noah's goal is to keep fixes scoped and safe. When a setting can be changed per site instead of globally, the guide will recommend the scoped option and show you how to verify it with a quick re-test.