Prophecy AI Interview Experience – Senior SDET | 7 YoE

Experience: 7 Years
Current Designation: Lead Automation QA Engineer
Role Applied: Senior SDET

---

Round 1 - Technical Interview

Duration: 1 Hour

Panel:

• Director of QA

Introduction

The interview started with a brief introduction and discussion about my background and current responsibilities.

---

Coding Question

Problem Statement

Design a simple text editor that processes a list of commands and outputs the final text.

Supported commands:

• type x → Append character x
• undo → Remove the last typed character
• redo → Reapply the last undone character

Note: Typing a new character after an undo clears the redo history.

Examples

Input:

["type a", "type b", "undo", "redo", "type c"]

Output:

abc

Input:

["type a", "type b", "type c", "undo", "undo", "type d"]

Output:

ad

Experience

I implemented a working solution and verified it using the sample inputs provided during the interview.

The interviewer then asked me to identify and test additional edge cases. I discussed multiple scenarios, updated the tests accordingly, and the implementation worked correctly for the cases we reviewed.

The discussion around the coding problem was straightforward and focused on correctness, handling edge cases, and validating the solution.

---

Testing & Automation Discussion

Questions Asked

1. How would you test a scheduler system similar to Jenkins?
2. What test scenarios would you consider for such a system?
3. How would you approach automation planning for a scheduler platform?
4. What challenges have you faced while building and maintaining automation frameworks?
5. How do you handle reliability and scalability concerns in automation?

Topics Covered

• Scheduler testing
• Automation strategy
• Framework design
• Test planning
• Real-world automation challenges
• Reliability considerations

Experience

The discussion primarily focused on testing strategy and automation architecture.

Questions were centered around practical testing approaches, automation planning, and challenges encountered while building automation solutions in production environments.

The conversation was technical and scenario‑based rather than focused on theoretical concepts.

---

Verdict

Rejected

Feedback

I received an automated rejection email stating that the company had decided to move forward with other candidates. No detailed feedback or specific explanation was provided regarding the decision.