Candescent — SDET / Automation Engineer (BFSI) — Interview Prep Kit¶
A complete study kit for an SDET / Automation Engineer interview at Candescent — the BFSI / digital-banking software company (the former NCR Voyix Digital Banking business; builds online & mobile banking, account opening, payments, and ATM/self-service software for US banks and credit unions).
Built directly against the company's documented Round 1 interview script and its sample questions. Stack used throughout: Java + TestNG + RestAssured (primary) and Playwright + TypeScript.
Start with 00-STUDY-PLAN.md — it decodes the JD, maps the rounds, does the gap analysis, and gives the 5-day schedule. This README is the file index + the night-before list.
Easiest way to learn: read 09-simple-notes-with-examples.md first to get every idea in plain words with a memorable example, then go to the deep files (01–05) for detail. Train your spoken English daily with 08-communication-skills.md.
The role in one line¶
Strip the buzzwords and it's: can you design an automation framework on a whiteboard, enumerate tests with formal techniques (EP/BVA), prove tool depth (Selenium/RestAssured/Playwright), discuss methodologies (TDD/BDD/ATDD), and frame all of it in banking terms — spoken in clear English. That's exactly the six sections of Round 1.
The JD's six pointers — AUTOMATION, FUNCTIONAL, REST ASSURED, SELENIUM, PLAYWRIGHT, BFSI EXPERIENCE — collapse into five tested skills. The differentiator is BFSI domain framing: answer every design/test question in banking language (accounts, transfers, balances, money precision, real-time, security/PII), not generic e-commerce.
Round 1 structure → where to study¶
| # | Section (from the interview script) | Study file |
|---|---|---|
| 1 | Instructions (show the room, video on, anti-AI checks) | 07-mock-interview.md |
| 2 | Introduction (self-intro, expectations) | 06-behavioral-and-intro.md |
| 3 | Functional & Automation — design a framework (heaviest) | 01-framework-design.md |
| 4 | Test Case / Test Plan Enumeration — EP & BVA | 02-test-plan-ep-bva.md |
| 5 | Software Development Methodologies (TDD/BDD/ATDD) | 04-methodologies-tdd-bdd-atdd.md |
| 6 | Communication Skills | 08-communication-skills.md (training) + 06-behavioral-and-intro.md |
| — | Tool depth (Selenium / RestAssured / Playwright) — supports §3 follow-ups | 03-selenium-restassured-playwright.md |
| — | BFSI domain fluency — supports every section | 05-bfsi-domain.md |
Files in this kit¶
| File | What it covers |
|---|---|
| 00-STUDY-PLAN.md | JD decode, gap analysis vs your portfolio, the reusable assets to build, 5-day schedule |
| 01-framework-design.md | The universal framework blueprint (layers, class hierarchy, components) + full worked answers to all 3 JD design questions (ride-share, e-commerce, Netflix) + a digital-banking blueprint |
| 02-test-plan-ep-bva.md | EP & BVA from scratch + a 4-step recipe + worked partition/boundary tables for all 4 JD scenarios (stock-trading, hospital reg, discount codes, the registration→API→email→SMS chain incl. "what you test vs other teams") |
| 03-selenium-restassured-playwright.md | Tool-by-tool depth + Q&A: Selenium (waits/POM/grid/flakiness), RestAssured (CRUD/auth/schema/chained+async integration), Playwright (auto-wait/fixtures/trace/storageState), and the Selenium-vs-Playwright decision narrative |
| 04-methodologies-tdd-bdd-atdd.md | TDD/BDD/ATDD from scratch + model answers to all 8 JD questions with their follow-ups + a banking Gherkin feature & step-defs |
| 05-bfsi-domain.md | Banking vocabulary, the 8 banking-specific test concerns, 5 worked end-to-end banking scenarios, test-data/env strategy, and 15 domain Q&A |
| 06-behavioral-and-intro.md | 75s + 30s self-intro scripts, communication-delivery guidance, 12 STAR stories (truthful, banking-bridged), HR/behavioral answers |
| 07-mock-interview.md | Two full timed Round-1 mocks (banking + the JD's alt scenarios), 30-question rapid-fire, a 1–5 self-scoring rubric, and a night-before cheat sheet |
| 08-communication-skills.md | Spoken-English training plan (simple words): the 5 common problems + fixes, answer frameworks (BLUF/PREP/STAR/signposting), a phrase bank, pronunciation guide, daily drills, a 2-week plan, video etiquette, and ❌weak→✅strong examples |
| 09-simple-notes-with-examples.md | Plain-English memory companion to 01–05: every concept as a flashcard (plain meaning → think of it like → example → remember) with a sticky analogy each, + "10 analogies to remember cold" |
The 10 things to know cold (night-before list)¶
- Open every design answer with a layered blueprint: Tests → Page/API objects → Business actions → Core utils → Config/Env → Data → Reporting/CI. Then name classes:
BaseTest/BasePage,DriverFactory(ThreadLocal),ConfigReader,WaitUtils,ApiClient,TestDataProvider,ReportManager, listeners. - Multi-environment = config/Maven profiles (QA/dev/pre-prod/prod); cross-browser = Selenium Grid / Playwright projects / BrowserStack; parallel = TestNG + ThreadLocal driver.
- Say the technique names out loud: "I'll use Equivalence Partitioning to group inputs, then Boundary Value Analysis on the edges (min−1, min, min+1, max−1, max, max+1) because bugs cluster at boundaries (
<vs<=)." - Always test invalid + boundary + non-functional, not just the happy path. For BFSI add: money precision, real-time accuracy, security/PII, audit.
- For the registration→API→email→SMS chain: test each hop (UI validation → API contract/status/schema/idempotency → DB persistence → email service → SMS service → async timing). Be explicit about what you test vs what another team/service owns.
- Money is special: never
float/double→ use BigDecimal; banker's rounding; the "sum of rounded line items vs rounded total" reconciliation bug; idempotency keys so a retried transfer never double-debits. - TDD = dev, unit, red-green-refactor. BDD = behavior, Given-When-Then, collaboration (Cucumber). ATDD = acceptance criteria agreed by the three amigos before coding. Know who drives each and when it's written.
- Selenium vs Playwright: Playwright auto-waits → less flaky, faster, built-in parallelism/trace; Selenium = mature, widest language/grid/legacy support. Pick per team skill + existing stack.
- Lead with your differentiators for a bank: real RestAssured chained-API work (answers the integration question) and VAPT/security (PCI/PII, auth/entitlements, injection) — banks care deeply.
- Communication: signpost answers ("three things — first… second…"), don't ramble, don't repeat the question slowly (reads as AI-assistant use). Show the room, video on, answer in your own words.