Zuora Interview Experience – Senior SDET | 7 YoE
Anonymous User
107
Quality AssuranceInterview

Zuora Interview Experience – Senior SDET | 7 YoE

Current Role: Lead Automation QA Engineer

I received the interview call around 10 days after getting a referral.

Round 1 – Technical + Coding Round

Duration: 1 Hour
Panel:

  • Senior SDET
  • SDET 3

Questions Asked

  1. Explain your automation framework in detail.

  2. Playwright vs Selenium – differences, advantages, and use cases.

  3. Several questions based on my resume and previous project experience.

  4. Coding Question:

    • Rotate Image (LeetCode #48)

  5. Coding Question:

    • Reverse Only Letters (LeetCode #917)

  6. Coding Question:

    • Group Anagrams (LeetCode #49)

Experience

The discussion started with framework design and automation concepts, followed by coding questions. The interviewers were interactive and asked relevant follow-up questions throughout the session.

Verdict

✅ Cleared

I received positive feedback approximately 3 days later.

Round 2 – Manual Testing + Automation Discussion

Duration: 1 Hour
Panel:

  • 2 Senior SDETs

Scheduled: Approximately 1 week after Round 1

Part 1 – Manual Testing (30 Minutes)

The interviewer shared a document describing a Zuora business flow involving integrations and asked me to identify and write critical end-to-end test scenarios.

Discussion Points

  • E2E business flow validation
  • Critical test coverage identification
  • Integration testing scenarios
  • Follow-up questions on prioritization and edge cases

This section was straightforward, and the follow-up questions were clear and relevant.

Part 2 – Automation & CI/CD Discussion (30 Minutes)

Questions Asked

  1. Explain your automation framework architecture.
  2. Design a typical automation framework structure.
  3. CI/CD-related discussions.
  4. Jenkins-related scenarios.
  5. Different Jenkins job parameters and configurations.
  6. Explain the various options used in Jenkins jobs in your current project.
  7. How would you automate a payment flow?
  8. How would you design a framework specifically for payment flow automation?

Experience

This round felt inconsistent compared to the first one.

Several questions lacked context, and when I requested clarification or rephrasing, the interviewer often repeated the same question without providing additional details. One Jenkins-related scenario was particularly unclear, and even after asking for clarification, I could not fully understand the intended problem statement.

The discussion around framework design for payment automation also felt vague, making it difficult to determine what level of detail was expected.

Overall, it seemed either the interview was not well prepared or the interviewer was not fully engaged in the discussion.

Post Interview Experience

I did not receive any update within 3 days after the interview.

I:

  • Sent a follow-up email.
  • Sent another follow-up after a week.
  • Attempted a phone call (unanswered).
  • Sent a text message requesting an update.

Later that day, I received a rejection email.

Overall Experience

Difficulty Level

Medium

Topics Covered

  • Automation Framework Design
  • Playwright vs Selenium
  • Manual Testing Scenarios
  • CI/CD
  • Jenkins
  • Payment Flow Automation
  • DSA

LeetCode Questions

  • Rotate Image (#48)
  • Reverse Only Letters (#917)
  • Group Anagrams (#49)

Final Verdict

❌ Rejected

While the first round was well-structured and professional, the second round felt inconsistent due to unclear questioning and lack of effective communication. The post-interview communication could also have been better, as multiple follow-ups were required before receiving a final decision.

Comments (0)