Skip to content

Candescent β€” SDET / Automation Engineer (BFSI) β€” Study Plan

This is the roadmap only. The actual Q&A / model-answer files (listed in Β§6) get generated next, once you approve this plan.

1. What this role is (decode the JD)

Candescent is the former NCR Voyix Digital Banking business β€” it builds digital banking + ATM/self-service software for banks and credit unions in the US. So "BFSI EXPERIENCE" is not a nice-to-have; it's the spine of the whole interview. Every framework/design answer you give should be framed in banking terms (accounts, transfers, payments, balances, statements, KYC/onboarding, fraud limits, real-time updates), not generic e-commerce.

The six JD pointers map to exactly five things they will test:

JD pointer What they're really checking
AUTOMATION Can you design a framework from a blank page (not just write tests in an existing one)?
FUNCTIONAL Can you enumerate test cases / a test plan with formal techniques (EP, BVA)?
REST ASSURED API automation depth β€” chained API + email + SMS validation, schema, status codes
SELENIUM Web UI automation depth β€” POM, waits, cross-browser, data-driven
PLAYWRIGHT Modern UI automation β€” when/why over Selenium, parallelism, trace, auto-wait
BFSI EXPERIENCE Domain framing + non-functional banking concerns (security, accuracy of money math, real-time, compliance)

The single mental shift they're grading: can you move from "I write test scripts" β†’ "I architect a scalable, maintainable, multi-environment automation framework and reason about what to test and why." The Round-1 sample questions are almost all open-ended design ("create a framework blueprint", "list major classes and hierarchy"). That's a whiteboard/talk-out-loud skill, separate from coding ability.

2. The Round-1 structure (from the JD) and how to beat each section

The interviewer's own script has 6 blocks. Sections 3–6 are scored:

  1. Instructions β€” they'll ask you to show the room (no second monitor / phone), keep video on, and they watch for slow question-repeating (anti-ChatGPT). β†’ Nothing to study; just be set up clean and answer in your own voice.
  2. Introduction β€” your pitch + they set expectations. β†’ Need a 60–90s BFSI-flavored intro.
  3. Functional & Automation β€” design a framework (ride-share / e-commerce / Netflix samples). β†’ Heaviest weight. Need a reusable framework-blueprint "template" you can adapt to any domain in 5 minutes.
  4. Test Case / Test Plan Enumeration β€” EP + BVA on a scenario (stock trading, hospital reg, discount codes, registration-form-with-API/email/SMS chain). β†’ Need the EP/BVA method cold + the integration-flow test-plan pattern.
  5. Software Development Methodologies β€” TDD vs BDD vs ATDD, Gherkin, step-def organization, ROI. β†’ Conceptual; ~8 known questions + follow-ups.
  6. Communication Skills β€” clear spoken English, no repetition, articulate. β†’ Practiced by reading model answers out loud / mock.

3. Gap analysis vs. what you already have

You already own the mechanics (Selenium/TestNG/RestAssured at B2BProjectTest + RestAssured_API, Playwright/TS at Morrie_automation, VAPT, LLM-eval). What this interview adds that your existing prep does not cover:

Gap Why it matters here
Framework design articulation Your prep proves you can use frameworks; this round asks you to design one on a whiteboard and name classes/hierarchy/components. Different skill.
BFSI domain fluency None of your six portfolio projects are banking. You need banking vocabulary + banking-specific test concerns (money rounding, idempotent transfers, real-time price/balance, audit trail, PCI/PII).
EP + BVA as a named technique You test by intuition; they want you to explicitly say "equivalence partitions are X, boundary values are Y" and produce a table.
TDD/BDD/ATDD theory You've used BDD/Cucumber in practice, but need crisp textbook differentiation + the follow-up answers (ROI, step-def org, test data across envs).
Playwright-vs-Selenium decision narrative Likely follow-up: "you listed both β€” when do you pick which?"

Strengths to lean on: real RestAssured chained-API experience (directly answers Q4's API→email→SMS scenario), real Playwright+TS, real Selenium+POM, and VAPT/security (great differentiator for a banking employer — bring it up unprompted).

4. The reusable assets to build (these win Section 3 & 4)

These are the "templates" you memorize once and adapt live:

  • A. The universal framework blueprint β€” a layered diagram + class list you can re-skin for ride-share, e-commerce, Netflix, or banking in minutes:
  • Layers: Tests β†’ Page/API objects β†’ Business actions β†’ Core utils β†’ Config/Env β†’ Data β†’ Reporting/CI.
  • Major classes: BasePage/BaseTest, DriverFactory/DriverManager, ConfigReader, WaitUtils, ApiClient/service classes, TestDataProvider, ReportManager, listeners.
  • Components: test runner (TestNG/JUnit/pytest), build (Maven/Gradle/npm), cross-browser (Selenium Grid/Playwright projects/cloud β€” BrowserStack), multi-env config (QA/dev/pre-prod/prod via profiles), data-driven (Excel/JSON/DB), reporting (Allure/Extent), CI (Jenkins/GitHub Actions), parallelization, secrets handling.
  • Cross-platform story (iOS/Android β†’ AppΠ ium; web β†’ Selenium/Playwright; smart-TV β†’ device farms).
  • B. The EP/BVA recipe β€” a 4-step method + a filled example table (e.g., transfer amount field: min 0.01, max daily limit, currency precision).
  • C. The integration-flow test-plan pattern β€” for the registrationβ†’APIβ†’emailβ†’SMS chain (Q4): how to test each hop, contracts between teams, what you test vs what another team executes.
  • D. A 90-second BFSI intro + 3 STAR stories re-pointed at banking-relevant work (an API framework story, a flaky-UI/waits story, a security/VAPT story).

5. Study schedule (5 focused days)

  • Day 1 β€” Framework design (Section 3). Build asset A. Practice adapting it out loud to all three sample domains and to a "digital banking portal" of your own. Drill: name the classes & hierarchy in under 5 min.
  • Day 2 β€” Test design (Section 4). Build assets B and C. Do all 4 sample enumeration questions on paper (EP/BVA tables).
  • Day 3 β€” Tool depth. Selenium (waits, POM, cross-browser) + RestAssured (the APIβ†’emailβ†’SMS chain, schema/status) + Playwright (auto-wait, trace, parallel, vs Selenium narrative). Tie each to banking examples.
  • Day 4 β€” Methodologies + BFSI domain. TDD/BDD/ATDD 8-question set with follow-ups; banking vocabulary + non-functional concerns (money math, real-time, security/PCI/PII, compliance/audit).
  • Day 5 β€” Mock + communication. Full timed mock of Sections 2–5, recorded; refine the intro; practice clear, non-repetitive spoken delivery.

6. Files to generate next (proposed manifest)

Mirrors your BCE kit layout. On your go-ahead I'll create:

File Contents
README.md Role decode, interview map, night-before cheat sheet
01-framework-design.md The universal blueprint + worked answers to all 3 sample design questions, re-skinned for digital banking
02-test-plan-ep-bva.md EP/BVA method + worked tables for all 4 enumeration questions (incl. the API→email→SMS chain)
03-selenium-restassured-playwright.md Tool-by-tool depth Q&A + the Playwright-vs-Selenium decision narrative, banking-flavored
04-methodologies-tdd-bdd-atdd.md All 8 JD questions with their follow-ups, model answers + Gherkin examples
05-bfsi-domain.md Banking vocabulary, money-math/real-time/security/compliance test concerns, why-it-matters-to-Candescent
06-behavioral-and-intro.md 90s intro + STAR stories re-pointed to BFSI
07-mock-interview.md Full timed mock (Sections 2–5) + self-scoring rubric

7. Open questions before I generate the files

  1. Language for code samples β€” Java/TestNG (matches your B2BProjectTest) as primary, with Playwright in TS? Or all-Java?
  2. Depth β€” same comprehensive depth as the BCE kit (long model answers), or tighter cheat-sheet style?
  3. Round scope β€” JD only shows Round 1. Want me to also prep a likely Round 2 (live coding / deeper system design / managerial), or keep strictly to Round 1 for now?