What This Posting Is Actually Asking For
This Deloitte Quality Engineer Hyderabad opening is, once you get past a requisition code as dense as “USI-EH27-Tax-GESTC-Quality-Engineer-with-Data-analytics-L25-BTA-Hyderabad,” a straightforward entry-level QA role sitting inside Deloitte’s Analytics Horizontal team — a group that exists specifically to keep analytics deliverables like reports, dashboards, and data pipelines reliable before they reach the people who depend on them.
The Actual Day-to-Day
- Requirement-to-test translation: converting business requirements into structured, written test scenarios rather than testing ad hoc.
- Manual functional and regression testing: run specifically on reports, dashboards, and data pipelines, not general application UI testing.
- Source-to-target validation: confirming data landing in a target system genuinely matches what left the source system — this is where the SQL requirement actually gets used, typically writing queries to compare row counts, values, and transformations between two systems.
- ETL/ELT and file integration testing: validating the pipelines that move and transform data before it reaches a dashboard, plus cloud-based data processes.
- Defect documentation: writing up issues with clear reproduction steps and business impact so a developer can fix them without a follow-up meeting.
- Agile participation: sitting in on sprint ceremonies and release-readiness reviews as a working part of a delivery team, not a QA function bolted on at the end.
Snapshot
| Job Title | BTA – Quality Engineer with Data Analytics |
|---|---|
| Company | Deloitte (USI — US India Offices) |
| Location | Hyderabad, Telangana, India |
| Job Type | Full-Time, Entry-Level |
| Work Mode | Onsite (Hyderabad) — shift timing 11:00 AM – 8:00 PM |
| Experience Required | None specified — genuinely entry-level/fresher-friendly |
| Education | Bachelor’s degree in Computer Science or related field |
| Application Deadline | Not specified in the posting |
| Estimated Salary/CTC | Deloitte’s Business Technology Analyst (BTA) track — which this role sits under — has been reported around ₹9 LPA for freshers in India. |
Required vs. Desired — Where To Focus Your Prep
- Required (genuinely entry-level): Bachelor’s degree in Computer Science or a related field; foundational software testing knowledge and SDLC understanding; basic SQL for querying and validation; familiarity with data-quality concepts; strong analytical thinking and attention to detail; clear written/verbal communication; working knowledge of Excel. None of this demands prior job experience — a strong final-year project or coursework can demonstrate it.
- Desired, not mandatory — test-management tools: Azure DevOps, Jira.
- Desired, not mandatory — scripting: Python, C#, or JavaScript.
- Desired, not mandatory — automation frameworks: Playwright, Selenium.
- Desired, not mandatory — BI/visualization tools: Power BI, QlikView, SSRS.
- Desired, not mandatory — broader technical awareness: ETL/ELT concepts, relational databases, cloud services (AWS, Databricks), Agile methodology, ISTQB Foundation Level certification.
- Where to actually spend limited prep time: basic SQL fluency and one BI tool — Power BI is the most commonly asked-about in Deloitte interviews — will do more for you than trying to learn every item on the desired list.
Shift Timing — A Detail Worth Flagging
- Deloitte’s own posting lists shift timings as 11:00 AM to 8:00 PM — later than a typical 9-to-6 office day.
- Likely reason: overlap with US-based Deloitte Tax and Analytics teams, given the “USI” (US-India offices) framing of the requisition.
- If your daily routine assumes standard office hours, confirm this directly with the recruiter before committing to interview rounds.
FAQs
1. Is this role really open to freshers with no prior work experience?
Yes — Deloitte’s own posting labels this “Entry-Level” and lists no minimum years of experience. The required qualifications are educational and foundational (a CS-related degree, basic SQL, testing fundamentals), not prior job history.
2. Is this a tax or accounting job because of “Tax” and “GESTC” in the title?
No — those terms refer to the internal Deloitte business unit (Tax / Global Employer Services technology group) this quality engineering role is aligned to. The actual work is technical QA on analytics systems, not tax preparation or accounting.
3. Do I need automation testing experience (Selenium, Playwright) to apply?
No — automation frameworks are listed under “Desired Skills,” not required qualifications. The role’s core responsibilities center on manual testing and SQL-based data validation; automation exposure is a bonus, not a gate.
4. What are the work hours for this role?
Deloitte’s posting lists shift timings of 11:00 AM to 8:00 PM, which is later than a standard 9-to-6 office day — likely to overlap with US-based teams. Confirm this directly with the recruiter if shift timing affects your decision to apply.
About Deloitte
Deloitte is a British-headquartered multinational professional services network. As one of the "Big Four" accounting firms alongside EY, KPMG, and PwC, it is the largest professional services network in the world by revenue and employee count.
View Company Profile →Top Interview Questions
Prepare with commonly asked questions for this role
I'd use ORDER BY with OFFSET and FETCH — sorting the column descending, skipping the first row, and fetching the next one. Alternatively, a subquery using MAX() with a WHERE clause excluding the overall maximum works too, and I'd mention that the OFFSET/FETCH approach handles ties more predictably.
I'd start with row-count reconciliation between source and target to catch obvious drops, then move to value-level comparison on key columns using SQL joins or checksums for larger tables. I'd also test the transformation logic itself — if a field is supposed to be aggregated or reformatted, I'd verify the output against a manually calculated expected value for a sample of records.
Functional testing checks whether a specific feature or report behaves as intended against its requirements — I'd run this on new or changed functionality. Regression testing re-runs a broader existing test set after a change to confirm nothing that used to work has broken, which I'd run before a release even if the change itself seemed unrelated to those areas.
I'd trace the number back to its source — first checking if the raw data in the underlying table is correct, then checking if any transformation or aggregation logic between the source and the report is where the discrepancy is introduced. Isolating which layer owns the bug before reporting it saves the developer time and makes the defect report far more useful.
I like the analytical, detail-oriented side of technology work — thinking through edge cases and how something could break is genuinely interesting to me, not just a step before the "real" work. I also see QA as a strong foundation for understanding full systems end-to-end, which I think makes for a stronger long-term technologist either way.