Explain your SDLC, code review, release and regression handling
Filed under Goldman Sachs
Free read 2 of 3Describe your team's actual model, for example Scrum sprints: planning, stories with acceptance criteria, branches per feature, and definition of done.
The question
Explain your software development process end to end: the development model, code review and merge, build and release, testing (unit, regression, load), how customers receive changes, and how regressions are handled. It assesses practical engineering maturity.
Approach
Describe your team's actual model, for example Scrum sprints: planning, stories with acceptance criteria, branches per feature, and definition of done.
A pull request needs reviewer approval and passing CI checks, then merges to the main branch (squash or rebase). Say what reviewers look for: correctness, tests, readability, security.
A CI pipeline compiles, runs tests and static checks, builds an artifact, deploys to staging and then production, using canary or blue-green releases and feature flags so changes reach customers gradually and can be rolled back.
Unit tests for logic, integration tests for services, a regression suite on each build, and load tests before significant releases to check throughput and latency.
Detect through tests, monitoring and alerts. Roll back or disable the feature flag first, then find the root cause, add a test that would have caught it, and write a short post-mortem.
Tips
- What they are testing: Tests whether you have lived through the full pipeline and can say what happens when something goes wrong.
- Common mistake: Describing an ideal textbook process that does not match your real team, which collapses under follow-up questions.
Related Goldman Sachs questions
Collected from public candidate posts and coding forums. Updated Nov 2026.