Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · CRED

CRED Data Engineer Interview Questions India 2026

CRED's data-engineering rounds probe reproducible feature pipelines, statement-history SQL, and governance-aware design, reflecting a credit-focused fintech handling sensitive financial data.

By the HireStepX editorial team · How we source and label this

Questions6
Rounds4
Intense2 of 6
FrameworkReproducible and governed
Try it · CRED question 1 of 6
Standard

Given a list of credit-card transactions, detect duplicate charges within a short time window. Optimise it and state your complexity.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect a pipeline round on computing per-user creditworthiness features from bureau data, transaction history, and app behaviour with point-in-time correctness for model training, a SQL round on trailing on-time payment ratios over recent statements with careful partial-window handling, and a governance round on enabling analytics and model training while respecting strict PII and financial-data controls. Interviewers reward reasoning about feature reproducibility, point-in-time correctness, tokenisation, and lineage over generic pipelines. Ground answers in real credit-ML and compliance workflows.

Practice questions

  1. 01

    Given a list of credit-card transactions, detect duplicate charges within a short time window. Optimise it and state your complexity.

    StandardCRED technical rounds favour clean, correct code with a product-quality bar. Expect DSA framed around payments, rewards, and card data.
    Practise
  2. 02

    Design an in-memory cache with expiry (TTL) and an eviction policy. Which data structures give O(1) get and put?

    Standard
    Practise
  3. 03

    Given reward points earned across many transactions, compute the maximum points redeemable under a set of constraints. Explain your approach.

    IntenseCRED interviewers pair DSA with a product framing. Strong candidates model the constraints cleanly and reason about the greedy-vs-DP trade-off.
    Practise
  4. 04

    Design a pipeline that computes per-user creditworthiness features from bureau data, transaction history, and app behaviour, ensuring feature reproducibility for model training.

    IntenseCRED data-engineer rounds probe feature pipelines with point-in-time correctness and reproducibility for credit ML models.
    Practise
  5. 05

    Write SQL to compute each user's on-time payment ratio over the trailing 6 statements, handling users with fewer than 6 statements gracefully.

    StandardCRED tests window-function SQL over statement history with careful handling of partial windows.
    Practise
  6. 06

    How would you design a data pipeline that respects strict PII and financial-data governance while still enabling analytics and model training?

    StandardCRED probes governance-aware data engineering: tokenisation, access controls, and lineage for sensitive financial data.
    Practise
Prep notes

How to walk in ready.

The typical CRED recruitment process has 4 stages: Recruiter screen and technical pre-screen → SQL and data-manipulation round → Feature pipeline and governance design round → Hiring-manager and behavioural round, then offer.

CRED typically conducts 4 interview rounds: Round 1 (45-60 min): SQL round on statement-history window functions; Round 2 (60 min): feature-pipeline round with point-in-time correctness; Round 3 (45-60 min): data-governance and platform design round; Round 4 (45 min): behavioural and hiring-manager round.

HireStepX recommends the Reproducible and governed framework for this type of interview: Build point-in-time-correct, reproducible feature pipelines for credit ML, write statement-history SQL, and design with PII tokenisation and lineage from the start.

CRED technical rounds favour clean, correct code with a product-quality bar. Expect DSA framed around payments, rewards, and card data.

CRED interviewers pair DSA with a product framing. Strong candidates model the constraints cleanly and reason about the greedy-vs-DP trade-off.

CRED data-engineer rounds probe feature pipelines with point-in-time correctness and reproducibility for credit ML models.

CRED tests window-function SQL over statement history with careful handling of partial windows.

CRED probes governance-aware data engineering: tokenisation, access controls, and lineage for sensitive financial data.

Practice

Rehearse the room before you enter it.

Run a mock CRED interview and get scored feedback on every answer.