Framework design and strategy questions
The key middle-level differentiator — moving from "can write tests" to "can build systems". Typical design questions:
- "Build a framework from scratch — how?"
- "How would you manage a 1000-test suite?"
- "How do you measure automation success?"
- "How would you bring automation to a manual team?"
A universal answer framework:
- Context questions (always start!): product, team, current state, pain points
- Principles: the pyramid, lowest-level verification, CI-first, simple before complex
- A concrete plan: staged (smoke → regression → expansion)
- Measurement: which metrics will confirm success
- Risks: name what could go wrong yourself
Be careful with "coverage %" on metric questions — code coverage doesn't measure automation value. Better metrics: escaped defects (bugs reaching production), regression execution time (manual vs auto), flaky rate, real bugs caught by the suite, PR feedback time.