Night Before Your Automation Interview: 2-Hour Revision Plan
The Night Before Your Automation Interview isn't for learning anything new — it's for making what you already know easy to say out loud. This two-hour plan focuses on the four things that decide most automation and SDET interviews: your framework answer, your project stories, the most-asked questions, and the core coding patterns. Then you sleep.
What Not to Do Tonight
- Start a new tool, framework or course.
- Skim hundreds of interview questions — you'll remember none of them.
- Memorize answers word for word; interviewers can tell, and follow-ups break them.
- Stay up late. A rested brain answers better than a tired one that read ten more pages.
The Plan at a Glance
| Time | Focus |
|---|---|
| 0:00–0:30 | Your framework explanation — out loud ⭐ |
| 0:30–1:00 | Five STAR project stories |
| 1:00–1:45 | 15 highest-priority questions (quick-recall card below) |
| 1:45–2:00 | Coding patterns, then the morning checklist — and stop |
0:00–0:30 — Your Framework Explanation ⭐
For experienced candidates, the framework question often decides the interview. Say it out loud until it takes about 90 seconds and feels natural. Cover, in order:
- Type and stack — e.g. "a hybrid framework — Page Object Model with data-driven testing — in Selenium, Java, TestNG and Maven."
- Structure — base classes and driver factory, page objects, tests, utilities, data and configuration.
- Execution —
testng.xml, groups, parallel runs and environments. - Reporting and CI — reports with screenshots and Jenkins schedule.
- One real challenge and its result.
Likely Follow-Ups — One Line Each
| Question | Key point |
|---|---|
| Where is inheritance used? | Tests extend BaseTest; pages extend BasePage |
| Where is encapsulation used? | Private locators, public page methods |
| Where is polymorphism used? | WebDriver driver = new ChromeDriver(); overloaded utility methods |
| How do you run tests in parallel? | TestNG parallel settings + ThreadLocal WebDriver |
| How do you handle waits? | Explicit-wait helpers, implicit wait at 0, no sleeps |
| How do you switch environments? | Config per environment, chosen with -Denv=qa |
| What would you improve? | An honest, specific answer such as API setup, reporting or more coverage |
Full walkthrough: How to Explain Your Automation Framework · OOP in Your Framework
0:30–1:00 — Five STAR Stories
Write one short story for each — Situation, Task, Action, Result — with a number in the result wherever you can:
| Story | Include |
|---|---|
| A difficult production bug | How you investigated, the business impact, what you changed afterwards |
| A flaky test you fixed | The root cause and the fix |
| Faster regression | Execution time before and after |
| A disagreement with a developer | The evidence you used and how it was resolved |
| A process improvement | What you changed and the measurable effect |
These five cover most scenario and behavioral questions. More: Top 25 Scenario-Based Questions.
1:00–1:45 — The 15 Highest-Priority Questions
Read each question, say your answer out loud, then check it against the one-line version:
| Question | One-line answer |
|---|---|
| Implicit vs explicit vs fluent wait | Global lookup timeout vs condition on one element vs condition with custom polling; use explicit waits |
| Absolute vs relative XPath | /html/… breaks on layout changes; // anchors to attributes — use relative |
findElement vs findElements |
First match or NoSuchElementException vs a list, empty if none |
close() vs quit() |
Current window vs every window and the session |
StaleElementReferenceException |
The element was re-rendered; find it again, store By locators |
| Window handling | Save parent handle, loop getWindowHandles(), switch, switch back |
| List vs Set vs Map | Ordered with duplicates vs unique values vs key–value |
| StringBuilder vs StringBuffer | Both mutable; StringBuffer is synchronized and slower |
| Overloading vs overriding | Same name, different parameters (compile time) vs subclass redefines a method (runtime) |
| 401 vs 403 | Not authenticated vs authenticated but not allowed |
| PUT vs PATCH | Replace the whole resource vs update some fields |
| Common status codes | 200, 201, 204, 400, 401, 403, 404, 409, 500, 503 |
| INNER vs LEFT JOIN | Only matches vs all left rows with NULLs for no match |
| Second-highest salary | SELECT MAX(salary) FROM emp WHERE salary < (SELECT MAX(salary) FROM emp) |
| Severity vs priority | Technical impact (tester) vs business urgency (product owner) |
If an answer felt shaky, read just that one topic:
Waits · XPath · Stale elements · List vs Set vs Map · Status codes · SQL joins · Severity vs priority.
Then do one quick timed round in the Selenium Interview Simulator.
1:45–2:00 — Coding Patterns
Don't write full programs tonight — recall the approach for each:
| Program | Technique |
|---|---|
| Reverse a string | StringBuilder — or a two-pointer swap on a char array |
| Palindrome | Two pointers |
| Second largest | Single pass tracking first and second |
| Remove duplicates | LinkedHashSet (keeps order) |
| First non-repeating character | LinkedHashMap counts |
| Character frequency | HashMap with merge() |
| Missing number | n(n+1)/2 − sum |
| Pair with given sum | HashSet complement lookup |
More: Java Coding Programs Cheat Sheet.
Company-Specific Notes
| Company | Often focuses on | Guide |
|---|---|---|
| Wipro | Manual testing, Selenium, Java coding, API, HR | Wipro |
| Cognizant | Framework design, POM, waits, API testing | Cognizant & Infosys |
| Infosys | Project walkthrough, TestNG, screenshots, broken links | Cognizant & Infosys |
| Coforge | Core Java, thread safety, SQL, coding | Coforge |
| ValueLabs | Framework architecture, design patterns, Grid, Cucumber, Git | ValueLabs |
Skim only the guide for tomorrow's company — ten minutes, no more.
Tomorrow Morning Checklist
- Say your framework explanation once, out loud.
- Re-read your five STAR stories.
- Have your resume open — every line on it is fair game.
- GitHub profile and project links ready to share.
- Remote interview: test camera, microphone and screen sharing; close notifications; have an IDE or online editor ready for coding.
- Water, a notebook and a pen.
During the Interview
- Be honest. If you haven't used something, say so, and explain how you'd approach it.
- Think out loud when coding — the reasoning is scored, not just the result.
- Blank on a question? Ask to clarify, restate it in your own words, and start from what you do know. A calm partial answer beats silence.
- Use numbers when you describe your work.
- Ask one or two questions at the end — about their framework, CI setup or biggest quality challenge.
From Real Projects
In interviews for testing and automation roles, I've found the questions come back to real work: the application you tested, how you wrote and reviewed test cases, how you tracked execution and defects (for me, TestRail and Jira), and how your automation was structured (Selenium, Java, TestNG, POM and a business library). Prepare one short, honest example from your own projects for each topic on this page. On Apkope, prospect and customer data arrives from email, phone, social media and chatbots, so test scenarios had to cover every channel that feeds the same records. Rehearse your project explanation out loud; it's the answer you'll give first.
FAQs
What Should I Revise the Night Before an Automation Interview?
Your framework explanation, five project stories, the 15 most-asked questions and core coding patterns — nothing new.
How Long Should I Study the Night Before?
About two focused hours, finishing early enough to sleep well.
Should I Memorize Answers?
No — memorize the key points and practice saying them in your own words. Word-for-word answers fall apart at the first follow-up.
What If I Don't Know an Answer Tomorrow?
Say what you do know, explain how you'd find out or approach it, and stay calm. Honesty scores better than guessing.
What If I Have a Week Instead of a Night?
Follow the two-week plan in The Complete SDET Interview Guide.
