DETAILED MASTER INTERVIEW GUIDE

================================

INTRODUCTION QUESTIONS (EXPANDED)

----------------------------------
Q1. Tell me about yourself.
A: My name is Premsing Chavan. I have 3 years of experience in Manual Testing and strong skills
in SQL, Python, Excel, and Power BI. I naturally enjoy analyzing data, solving problems, and
improving accuracy. In my roles, I ensured data quality, validated datasets, wrote test cases, and
supported cross-functional teams. I believe in clarity, simplicity, and continuous improvement.

Q2. Tell me about your strengths.

A: My strengths are attention to detail, strong documentation, analytical thinking, and the ability to
stay calm under pressure. I also communicate well and like solving data problems.

Q3. Tell me about your weaknesses.

A: Sometimes I double-check my work more than required because I aim for accuracy, but I am
improving by balancing speed and quality.

Q4. Walk me through your resume.

A: I started with a Data Analyst internship at Rubixe where I learned data cleaning, Excel
automation, SQL validation, and EDA. I then worked as a Manual Test Engineer at Futurefold
Software, performing functional testing, regression testing, backend SQL validation, and data
reconciliation. I improved defect leakage by 20% and enhanced reporting accuracy. Now, I am
aiming for roles where I can combine both testing and data analytics.

JOB ROLE EXPLANATION (EXPANDED)

--------------------------------
Q1. What was your role in Retail Banking domain?
A: I validated customer data, verified account details, checked transaction logs, ensured correct
interest calculations, and validated backend data against UI. I also checked statements, fund
transfers, EMI schedules, and reconciled mismatched records.

Q2. What was your role in Ecommerce domain?

A: I tested product search, filtering, sorting, cart, checkout, offers, payment systems, refunds, and
backend order tracking. I validated SQL tables for orders, inventory, users, payments, and ensured
no data mismatch between frontend and backend.

Q3. How did you use SQL in both domains?

A: I performed count checks, duplicate checks, null checks, transformation checks, reconciliation
between modules, validated logs, and joined multiple tables to verify correct data flow.

Q4. How did you use Excel and Power BI?

A: I created dashboards, charts, KPIs, trend analysis, automation through formulas, pivot tables,
conditional formatting, and prepared clean reports for management.

Q5. How did you use Python?

A: I cleaned datasets with Pandas, removed duplicates, filled missing values, merged data sources,
performed EDA, and automated repetitive tasks.
HR BEHAVIORAL QUESTIONS (DETAILED)
----------------------------------
Q1. Describe a challenging situation.
A: In a banking module, loan repayment amounts were mismatched. I used SQL and logs to identify
the issue in transformation logic. After fixing, mismatches were resolved and recurrence was
prevented.

Q2. How do you work under deadlines?

A: I break tasks into smaller parts, prioritize high-impact work, and regularly communicate progress.
I stay calm and avoid rushing mistakes.

Q3. What motivates you?

A: Learning new skills, solving meaningful problems, and helping teams make decisions using
accurate data.

Q4. Why should we hire you?

A: I bring a unique combination of testing and data analytics skills. I validate data thoroughly, solve
problems logically, and communicate clearly. I am reliable, detail-oriented, and quick to learn.

Q5. What kind of work environment do you prefer?

A: Supportive, collaborative teams with clear communication and opportunities to grow.

CHEAT SHEET (QUICK REVISION)

------------------------------
SQL:
- Joins: INNER, LEFT, RIGHT, FULL
- WHERE vs HAVING
- GROUP BY, ORDER BY
- Window functions: ROW_NUMBER, RANK
- Duplicates, Null Check, Count Check

Python/Pandas:
- read_csv(), dropna(), fillna()
- merge(), concat()
- groupby(), apply()
- describe(), value_counts()

Excel:
- VLOOKUP, XLOOKUP
- Pivot Table, Conditional Formatting
- SUMIF, COUNTIF
- TRIM, TEXT functions

Power BI:
- DAX basics: SUM, CALCULATE, FILTER
- Relationships, Data Modeling
- Drill-down, Drill-through
- Import vs DirectQuery

Testing:
- Regression, Smoke, Sanity
- Test Cases, RTM, Defect Life Cycle
- STLC, SDLC, Agile

HR:
- Strengths, Weaknesses
- Why this role?
- Conflict handling
📘 EASY STUDY & PRACTICE VERSION — 125 Q&A
(Condensed • Clean • Quick Revision Style)

⭐ 1. BASIC INTRO QUESTIONS — FAST ANSWERS

1. Tell me about yourself.
3 years in Manual Testing + Data Analysis (SQL, Python, Excel, Power BI). Strong in validation, accuracy, and
reporting.

2. Walk me through your resume.

Manual Testing → SQL validation → Excel/Power BI reporting → strong data analysis skills.

3. Why Data Analysis?

I enjoy cleaning data, analyzing trends, and solving problems.

4. Why hybrid role?

I understand both quality and data accuracy.

5. Strengths: accuracy, detail, analysis.

6. Weakness: over-working earlier → improved prioritization.

7. Tools summary: SQL (validation), Python (EDA), Excel (dashboards), Power BI (reports).

8. Handling pressure: prioritize, break tasks.

9. Motivation: solving real data issues.

10. 3-year goal: senior data analyst.

⭐ 2. DATA ANALYSIS — QUICK ANSWERS

11. Data cleaning: remove errors, fix formats. 12. Data validation: ensure correctness. 13. EDA:
understand data using visuals. 14. Handling missing values: fill/remove. 15. Outliers: IQR, boxplot. 16.
Data profiling: structure + quality check. 17. Reconciliation: compare 2 datasets. 18. Reliability check:
nulls, duplicates. 19. KPIs: defects, leakage, sales trends. 20. Documentation: note every cleaning step.

1
⭐ 3. SQL — MOST ASKED QUICK ANSWERS
21. Primary key: unique row ID. 22. WHERE vs HAVING: rows vs groups. 23. JOIN difference: Inner =
match; Left = all + match. 24. Subquery: query inside query. 25. Find duplicates: GROUP BY + HAVING. 26.
2nd highest salary: MAX < MAX. 27. GROUP BY: aggregate groups. 28. UNION vs ALL: removes duplicates
vs keeps. 29. Window functions: aggregate without losing rows. 30. ROW_NUMBER/RANK: ordering tools.
31. Top 3 salary/department: ROW_NUMBER partition. 32. Update with join: UPDATE + JOIN. 33.
COALESCE: first non-null. 34. Percent contribution: value/SUM OVER. 35. Optimization: indexes + rewrite
queries. 36. Indexes: faster search. 37. CTE: temporary view. 38. Mismatches: EXCEPT/NOT IN. 39.
Execution plan: how DB runs query. 40. Handling NULL: COALESCE.

⭐ 4. PYTHON (NumPy/Pandas) — 1-LINE ANSWERS

41. Drop duplicates: df.drop_duplicates() 42. Missing values: [Link]().sum() 43. loc vs
iloc: label vs index. 44. Merge: [Link]() 45. Convert types: astype() 46. apply(): apply functions.
47. CSV: read_csv() / to_csv() 48. Vectorization: fast array ops. 49. Filter: df[[Link] > x] 50.
groupby(): apply aggregations.

⭐ 5. EXCEL — 1-LINE QUICK POINTS

51. Common functions: VLOOKUP, XLOOKUP, IF. 52. XLOOKUP: two-way lookup. 53. Pivot table:
summarize data. 54. Conditional formatting: highlight data. 55. Automation: formulas/macros. 56.
INDEX-MATCH: flexible lookup. 57. Remove duplicates: Data tab. 58. Cleaning: TRIM, CLEAN. 59.
Dashboards: pivots + slicers. 60. Advanced formulas: SUMPRODUCT.

⭐ 6. POWER BI — SHORT ANSWERS

61. Dashboard vs report: 1 page vs multipage. 62. Power Query: data cleaning. 63. DAX: formula
language. 64. SUMX/CALCULATE/FILTER: row sum, context change. 65. Relationships: link tables. 66.
Optimization: reduce visuals. 67. Query folding: push to source. 68. Refresh: scheduled. 69. Slow visuals:
heavy DAX. 70. Measures vs columns: dynamic vs stored.

⭐ 7. QA / TESTING — SHORT ANSWERS

71. STLC: complete testing flow. 72. SDLC: software life cycle. 73. Regression: re-test. 74. Functional:
validate features. 75. Verification/Validation: process/output. 76. Defect life cycle: new→close. 77.
Severity/Priority: impact/urgency. 78. Test case: steps + expected result. 79. Defect leakage: bug missed.

2
80. RCA: find why. 81. Tools: JIRA. 82. Traceability matrix: req→test. 83. Backend testing: SQL. 84. ETL
testing: validate movement. 85. Log analysis: error tracing.

⭐ 8. HYBRID DATA + QA
86. Validate API: compare DB. 87. UI vs DB: match logic. 88. SQL checks: counts, rules. 89. Dashboard
testing: totals + filters. 90. UI mismatch: distinct vs raw. 91. Pipelines: compare stages. 92. Data vs UI:
check DB first. 93. ETL: record-level checks. 94. Consistency: cross-system. 95. Reporting issues: show
samples.

⭐ 9. SCENARIO-BASED — EXAM STYLE CHEAT

SHEET
96. UI=1200, DB=1180: check filters & distinct. 97. Wrong totals: check DAX. 98. Duplicate data: clean + fix
root. 99. Slow SQL: add indexes. 100. Not reproducible bug: share logs. 101. Excel ≠ dashboard: filter
mismatch. 102. ETL fail: trace logs. 103. Upload crash: file size. 104. KPI drop: refresh check. 105. API
nulls: mapping issue. 106. Wrong dates: standardize. 107. Production defect: RCA. 108. Slow BI: reduce
visuals. 109. Join duplicates: wrong keys. 110. Recon mismatch: layer check. 111. Missing/outliers: clean.
112. Wrong filter totals: slicers. 113. Heavy model: remove fields. 114. API mapping: compare fields. 115.
Wrong aggregates: fix DAX.

⭐ 10. HR — SHORT & SAFE ANSWERS

116. Challenge solved: found mismatch early. 117. Conflict: clear communication. 118. Prevented issue:
wrong join fixed. 119. Unclear requirement: ask questions. 120. Why hire me: hybrid skills. 121. Leaving
job: growth. 122. Preferred environment: collaborative. 123. Mistakes: accept + learn. 124. Prioritization:
urgency-first. 125. Learning: always open.

✅ Ready for Revision

• All answers are short and fast to memorize.
• Perfect for last‑minute interview preparation.
• Ideal for printing as a cheat sheet.

If you want, I can also create: ✔ Flashcards version

✔ Multiple-choice practice set
✔ Mock interview practice

3
PREMIUM INTERVIEW PREPARATION BOOKLET
=====================================

PREM’S ULTIMATE INTERVIEW PREPARATION SYSTEM

--------------------------------------------

INTRODUCTION (60-second pitch)

------------------------------
Hi, I'm Premsing Chavan. I have 3 years of experience in Manual Testing and hands-on skills in
SQL, Python (Pandas), Excel, and Power BI. I have worked in retail banking and ecommerce
domains, performing backend data validation, reconciliation, functional testing, and quality analysis.
I enjoy solving data problems, improving accuracy, and creating reliable reports. I reduced defect
leakage by 20% and improved validation coverage. I want a role where I can use both my testing
and data skills to help teams make better decisions.

JOB ROLE SUMMARY

----------------
T – Testing
D – Data validation
V – Visualization
R – Reporting

RETAIL BANKING EXPERIENCE

-------------------------
- Validated account data, customer transactions.
- Verified EMI calculations and interest logic.
- Reconciled UI vs backend records.
- Ensured correct fund transfers and statements.

ECOMMERCE EXPERIENCE
--------------------
- Tested product, cart, checkout, payment.
- Validated backend order, user, and inventory tables.
- Ensured UI and database have consistent records.

HR BEHAVIORAL ANSWERS
---------------------
Strengths:
A – Analytical
D – Documentation
C – Communication
P – Precision

Weakness:
I double-check my work too much but improving.
Handling Pressure:
B – Break tasks
P – Prioritize
C – Communicate early

SCENARIO-BASED ANSWERS
----------------------
Dashboard mismatch:
F – Filters
D – Data source
M – Model
J – Joins

Developer says not a bug:

E – Evidence
E – Examples
S – Steps

SQL QUICK GUIDE

----------------
- Joins: INNER = match, LEFT = all left.
- WHERE = before grouping ; HAVING = after.
- Window functions: ROW_NUMBER(), RANK().
- Duplicates: GROUP BY with COUNT > 1.
- Second highest salary: salary < MAX.

PYTHON/PANDAS QUICK GUIDE

-------------------------
- dropna(): remove
- fillna(): replace
- merge(): combine data
- groupby(): summary table
- apply(): custom logic

EXCEL QUICK GUIDE

-----------------
- XLOOKUP = best lookup
- SUMIF/COUNTIF = conditional
- Pivot Table = summary
- Conditional Formatting = highlight issues

POWER BI QUICK GUIDE

--------------------
- Measure = dynamic
- Column = stored
- Key DAX: SUM, CALCULATE, FILTER

TESTING QUICK GUIDE

-------------------
- Smoke = basic test
- Sanity = fix validation
- Regression = re-testing
- RTM = requirements mapping
- Bug Life Cycle = New → Fixed → Closed

FINAL CHEAT SHEET (30 Seconds Revision)

---------------------------------------
- Profile: Testing + SQL + Data
- Strengths: Accuracy, Documentation
- Weakness: Overchecking
- SQL: Joins, Group By, Windows
- Python: merge, dropna
- Excel: Pivot, XLOOKUP
- Power BI: DAX basics
- Testing: Smoke/Sanity/Regression
- HR: Calm, problem solver
- Job Role: Testing + Data Validation
📘 ROLE-SPECIFIC Q&A — PRINTABLE PDF VERSION
(Data Analyst • SQL • QA/Testing • Power BI)

⭐ DATA ANALYST — QUESTIONS & ANSWERS

1. Common data quality issues?

Missing values, duplicates, inconsistent formats, incorrect types, and outliers.

2. Handling missing values?

Remove, fill with mean/median/mode, or forward/backward fill based on context.

3. Detecting outliers?

Using IQR, boxplots, Z-score, and distribution analysis.

4. Steps in EDA?

Check structure → missing values → distributions → correlations → visuals → insights.

5. What makes a good KPI?

Measurable, relevant, time-bound, and aligned with business goals.

6. Ensuring dashboard accuracy?

Validate SQL totals, visuals, sample records, filters, and refresh history.

7. Presenting insights to non-technical users?

Use simple visuals, avoid jargon, and explain business impact clearly.

⭐ SQL — QUESTIONS & ANSWERS

1. DELETE vs TRUNCATE vs DROP?

DELETE removes rows; TRUNCATE clears table; DROP removes table completely.

1
2. Find duplicates.

Group column and filter COUNT > 1.

3. Second highest salary.

Use MAX(salary) < MAX(salary) subquery.

4. UNION vs UNION ALL.

UNION removes duplicates; UNION ALL keeps them.

5. Window functions.

Perform calculations without reducing rows.

6. CTE purpose.

Simplify complex queries using WITH.

7. Optimizing slow SQL queries.

Use indexes, avoid SELECT *, optimize joins, check execution plan.

⭐ QA / MANUAL TESTING — QUESTIONS &

ANSWERS
1. Types of testing performed.

Functional, regression, integration, E2E, backend testing, data validation.

2. Severity vs Priority.

Severity = impact; Priority = urgency.

3. Defect leakage.

Bugs found in production after testing.

4. Backend testing using SQL.

Validate counts, UI-DB match, business rules.

2
5. Testing with incomplete requirements.

Ask clarifying questions, document assumptions.

6. Traceability matrix.

Maps requirements to test cases.

7. Handling non-reproducible bugs.

Use logs, screenshots, and test in multiple environments.

⭐ POWER BI — QUESTIONS & ANSWERS

1. What is Power BI used for?

Creating dashboards, insights, and analytics.

2. What is Power Query?

Tool for data cleaning and transformation.

3. Calculated column vs measure.

Column = stored; Measure = calculated dynamically.

4. CALCULATE() usage.

Changes filter context.

5. Why Power BI becomes slow?

Too many visuals, heavy DAX, large model.

6. What is query folding?

Pushing transformations to the source.

7. Optimizing Power BI reports.

Reduce visuals, optimize DAX, use star schema.

3
⭐ DATA ANALYST — SCENARIO ANSWERS
1. Dashboard totals incorrect.

Check refresh, filters, DAX, validate SQL, fix inconsistencies.

2. Too many missing values.

Analyze patterns → decide fill/remove → communicate impact.

3. Inconsistent data.

Inform team → clean → document → validate.

⭐ SQL — SCENARIO ANSWERS

1. Slow SQL query.

Check plan, add indexes, optimize joins.

2. Duplicate join results.

Check join keys and duplicate data.

3. Count mismatch.

Compare filters, distinct vs raw count.

⭐ QA — SCENARIO ANSWERS
1. Developer rejects bug.

Provide clear steps, logs, recording.

2. Critical defect on release day.

Escalate instantly with impact.

3. UI=100, DB=80.

Check filters, joins, and business logic.

4
⭐ POWER BI — SCENARIO ANSWERS
1. Slow dashboard.

Optimize visuals, reduce model size.

2. Relationship breaks.

Check key uniqueness and datatype.

3. Wrong measure total.

Rewrite using CALCULATE/SUMX.

📘 END OF PDF CONTENT

Let me know if you'd like: - A cover page - Page numbers - Corporate styling - A combined master PDF with
all sections