I Bombed My Tech Mahindra Interview (Here's What They Actually Asked)

Three years Selenium automation testing.

Custom framework. TestNG. POM.
Failed first round.
Not because I didn't know Selenium. Because I couldn't explain why I made design choices.
This TestLeaf guide - Tech Mahindra selenium interview questions showed what I missed.

Questions That Killed Me
"What framework?"
Me: "Hybrid with POM and TestNG."
Them: "Why hybrid? Why not pure data-driven?"
Silence.
"Multiple TestNG suites?"
Me: "Yes, testng.xml."
Them: "Configure smoke, sanity, regression in parallel for CI/CD. Show me."
More silence.
The Pattern
Software testing with Selenium isn't about tools.
It's design decisions.
Every question: What → Why → How → Trade-offs
Not "Know TestNG?"
But "Why @BeforeMethod instead of @BeforeClass here?"
Real Questions
Framework: Why hybrid over data-driven? POM structure? Test data handling?
TestNG: Multiple suites, grouping, DataProvider vs Excel, parallel execution
Java: Overloading vs overriding, interface vs abstract, collections, OOPS
Scenarios:

500 tests, need smoke after builds. How?
Login fails. Thread.sleep or explicit wait?
Validate dropdown duplicates. Which collection?

What Changed
Found Selenium training in Chennai teaching architecture, not syntax.
Learned:

Design patterns (why POM)
Framework trade-offs
Real project structure
CI/CD integration

Now I Ace
Hybrid vs Data-Driven: Hybrid = POM + data + utilities + reporting. Data-driven = only data separation.
Multiple Suites: with tags, or Maven Surefire triggers.
Grouping: @test(groups={"smoke"}) runs specific packs.
Overloading/Overriding: Overloading = same method, different params (compile). Overriding = child redefines parent (runtime).
New Answer
Question: "Explain framework."
Before: "Hybrid with POM."
Now: "Hybrid combining POM for maintainability, DataProvider for data separation, custom utilities for WebDriver wrappers, Extent Reports for visibility, Maven for CI/CD. Chose hybrid for scalability and flexibility—pure data-driven wouldn't handle complex page interactions."
The Gap
Most know Selenium.
Few explain:

Why you chose this
Trade-offs made
How to scale
When to change

That's "knows tools" vs "engineers systems."

TestLeaf.
What caught you? 🤔

selenium #testing #interview