Ask what you are stuck on, and answer what you know. Other SDETs vote for the best answers.
14 questions in Test strategy about Test strategy
What strategies and code patterns should SDETs evaluate during developer PR reviews to enhance application testability?
How do I test AI/LLM-powered features where outputs are non-deterministic?
How do I push back when I'm told to "just test it quickly" before a release?
How do I test in production safely (feature flags, canaries, observability)?
What is shift-left testing in practice, and how do I get involved before code is written?
How do I do exploratory testing well, and how do I document it?
How do I write effective test cases and choose between boundary value analysis, equivalence partitioning and decision tables?
What quality gates should block a release, and who decides?
How should I manage test data: seeding, factories, synthetic data or production copies?
How do I cut a two-hour regression suite down to 15 minutes?
What test coverage number is actually meaningful, and is 100% a good goal?
How do I measure the ROI of test automation to justify it to management?
Is the test pyramid still valid, or should I use the testing trophy or honeycomb?
How do I decide what to automate and what to leave manual?