SRE DevOps Engineer Interview Experience at CRED – 2025
CRED
General SRE Pattern
No specific, verified real CRED SRE/DevOps candidate account was found (searches surfaced real CRED SDE/Android/BA accounts but nothing DevOps-specific). Built from generally reported real DevOps/SRE loop patterns at Indian fintech scale-ups, reflecting CRED's known emphasis on case-study-style evaluation seen across its other engineering roles. This entry is a reconstruction, not a first-hand transcript.
Application Story
Candidates for this role typically apply through a recruiter on LinkedIn and move through an assignment, two technical rounds, and a case-study-heavy round over about three weeks.
Preparation Journey
Given CRED's reputation for a case-study-driven evaluation style across engineering roles generally, preparation should cover not just technical answers but structured frameworks for reasoning through open-ended infrastructure problems out loud.
Why Selected / Rejected
The case-study round asks candidates to reason through an ambiguous reliability tradeoff with no clean answer. Leaning too heavily toward a textbook-safe answer rather than committing to a specific tradeoff and defending it is a common way candidates fall short, and several candidates in similar case-study-style loops describe that commitment as the actual bar being tested.
Resume Tips
For a case-study-heavy loop like CRED's, practice committing to a specific answer under ambiguity and defending the tradeoffs rather than hedging - hedging is read as a lack of conviction, not caution.
Technical
Covers Kubernetes deployment strategies for a payment-adjacent service where a bad rollout is unusually costly. Candidates are asked to argue for a specific deployment strategy (canary versus blue-green) for a hypothetical service handling reward redemptions, rather than describing both neutrally. The stronger position argues for canary with automated rollback on error-rate increase, since it limits blast radius more granularly than blue-green's all-or-nothing cutover.
Study References
Technical
AWS infrastructure questions focused on securing a service handling sensitive financial data - specifically how to structure IAM policies with least-privilege access for a service that only needs to read from one specific S3 bucket and write to one specific DynamoDB table, and how to rotate access keys or move to role-based access entirely to avoid long-lived credentials.
Study References
Other
A case-study round presenting an ambiguous reliability tradeoff: given a fixed infrastructure budget, whether to invest it in additional redundancy for the primary payment path or in better observability tooling to catch issues faster across the whole platform. Interviewers want a committed recommendation with clear reasoning, not a balanced overview of both options, and push hard on the follow-up 'what would change your mind' question.
Study References
Questions Asked at CRED in the SRE DevOps Engineer Interview
Technical Round
Covers Kubernetes deployment strategies for a payment-adjacent service where a bad rollout is unusually costly. Candidates are asked to argue for a specific deployment strategy (canary versus blue-green) for a hypothetical service handling reward redemptions, rather than describi …
Technical Round
AWS infrastructure questions focused on securing a service handling sensitive financial data - specifically how to structure IAM policies with least-privilege access for a service that only needs to read from one specific S3 bucket and write to one specific DynamoDB table, and ho …
Other Round
A case-study round presenting an ambiguous reliability tradeoff: given a fixed infrastructure budget, whether to invest it in additional redundancy for the primary payment path or in better observability tooling to catch issues faster across the whole platform. Interviewers want …
Prepare for this Role
At a Glance
SRE DevOps Engineer at Other Companies
Have your own story?
Share it and help the next candidate prepare.
Comments
Loading comments...