Companies / Microsoft
Microsoft practice pack
Product company. Engineering-led testing: code, design, and quality for scale.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
Skills this role is usually tested on
- Coding
- Test design
- API and service testing
- Debugging
- Collaboration
Business areas used for scenarios
- cloud
- productivity software
- developer tools
- gaming
6 questions
Answer out loud first, then open the guide. Most people read the guide too early.
- 1
How would you test a text editor's find and replace feature?
mediumTest designA strong answer covers
Case, whole word, regex, multiline, special characters, very large files, undo, selection scope, performance, accessibility and keyboard use.
- 2
Implement an LRU cache and describe how you would test it.
mediumCodingA strong answer covers
Hash map plus doubly linked list for O(1). Tests: capacity one, eviction order, update refreshes recency, get on missing, concurrency if shared.
- 3
A service passes in staging and fails in production under load. Where do you look?
hardDebuggingA strong answer covers
Config and data differences, resource limits, timeouts and retries, connection pools, race conditions, and telemetry. Reproduce with a load test that matches production shape.
- 4
How do you design tests for an API versioning change?
mediumAPI testingA strong answer covers
Compatibility tests for old clients, contract tests, deprecation behaviour, default version handling, and a rollout plan with usage telemetry.
- 5
What would you check to say a new screen is accessible?
mediumAccessibilityA strong answer covers
Keyboard only, focus order, labels and roles, contrast, screen reader flow, zoom and reflow, error messages, and an automated scan plus manual checks.
- 6
How do you work with a developer who treats tests as your job only?
easyCollaborationA strong answer covers
Share the cost of defects, pair on a failing area, agree who writes unit and integration tests, and show data on where escapes came from.
Now say it to an interviewer
Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.