Interview practice plan

GS

The Core Engineering-L2-Hyderabad-Vice President-Software Engineering

Goldman Sachs · Hyderabad

EngineeringLead / Manager26 practice questions

Practice content written by LYDJ for interview preparation. These are common questions for this kind of role, not this employer's actual interview questions.

What this role asks for

Skills we found in the job description. The plan below is built around them.

GitSystem designDistributed systemsCI/CDJavaTypeScriptJavaScriptReactPythonMicroservicesKubernetesNoSQLData modelingMachine LearningRAGObservability

Also named in the description, not covered below: Kubernetes, NoSQL, Data modeling, Machine Learning, RAG, Observability, Elasticsearch, Kafka. Review these on your own.

Sign in to see your gap areas first. We compare this role with the skills on your profile.

0 of 26 questions practised

Answer each one out loud, then tick it. Progress is saved in this browser only.

01Required skill0/3

CI/CD & IaC

This role asks for Git and CI/CD. These CI/CD & IaC questions cover the ground they share.

  • Blue-green, canary or rolling deployment: how do you choose?

    What good looks like

    Blast radius, rollback speed, infrastructure cost and how good your metrics are for judging a canary. Give a case for each.

  • How do you manage infrastructure as code safely across environments and a team?

    What good looks like

    Remote state with locking, reusable modules, plans reviewed in pull requests, separate state per environment, drift detection and least-privilege CI credentials.

  • The build takes 40 minutes. How do you bring it down?

    What good looks like

    Measure where time goes, cache dependencies, parallelise and shard tests, only build what changed, and fix or quarantine the slowest tests.

02Required skill0/3

Java

This role asks for Java.

  • Explain the Java Memory Model. What do volatile and synchronized actually guarantee?

    What good looks like

    Visibility versus atomicity, happens-before, and why a volatile counter++ is still not thread-safe (use atomics or locks).

  • When would you use CompletableFuture, a bounded ExecutorService, or virtual threads?

    What good looks like

    Virtual threads for blocking I/O-heavy code, CompletableFuture for composing async steps, bounded pools for CPU-bound work, and the pinning caveats of virtual threads.

  • Your Java service throws OutOfMemoryError in production about once a week. How do you investigate?

    What good looks like

    Heap dump on OOM, analyse retained sizes and dominators, check caches and unbounded collections, and correlate with traffic or batch jobs.

03Required skill0/3

TypeScript

This role asks for TypeScript.

  • What are discriminated unions, and how do they help with exhaustive checks?

    What good looks like

    A shared literal field narrows the type in a switch; assigning the default case to never makes the compiler flag any unhandled variant.

  • When is using any or a type assertion acceptable, and how do you keep a large codebase strictly typed?

    What good looks like

    Prefer unknown plus narrowing, enable strict mode, validate external data at the boundary, and tighten gradually with lint rules.

  • How would you keep frontend API types in sync with the backend?

    What good looks like

    Generate types from an OpenAPI or GraphQL schema, share a contracts package, and validate responses at runtime where data crosses a trust boundary.

04Required skill0/1

JavaScript

This role asks for JavaScript.

  • How would you find and fix a memory leak in a single-page app?

    What good looks like

    Heap snapshots in browser DevTools, detached DOM nodes, listeners and intervals not cleaned up, and caches that grow with every navigation.

05Required skill0/3

React

This role asks for React.

  • How do you decide between local state, context and a global store in a large app?

    What good looks like

    Keep state as local as possible, use context for low-frequency shared values, a store for complex shared client state, and a data-fetching cache for server state.

  • Server components versus client components: what runs where, and what can a server component not do?

    What good looks like

    Server components render on the server with direct data access and no client JS; they cannot use state, effects or browser APIs, so interactivity lives in client components.

  • A list of 10,000 rows is slow to render and scroll. How do you fix it?

    What good looks like

    Measure with the Profiler, virtualise the list, use stable keys and memoised rows, and consider pagination or server-side filtering.

06Required skill0/3

Python

This role asks for Python, FastAPI and Flask. These Python questions cover the ground they share.

  • How does Python manage memory, and why might a long-running process keep growing?

    What good looks like

    Reference counting plus a cyclic garbage collector, fragmentation, unbounded caches or globals, and using tracemalloc to find the growth.

  • How do you structure a Python codebase so a team can work on it safely?

    What good looks like

    Locked dependencies, pyproject-based packaging, type hints checked in CI, pytest with fixtures, linting and formatting, and clear module boundaries.

  • A Python data-processing script takes hours. How do you speed it up?

    What good looks like

    Profile first, replace row-by-row loops with vectorised NumPy or pandas operations, process in chunks, then consider multiprocessing or a distributed engine.

07Design round0/3

System design

This role asks for System design, Distributed systems, Microservices, REST APIs and GraphQL, so expect an architecture round. State requirements and numbers first, then trade-offs.

  • How would you break a monolith into microservices? Where would you start?

    What good looks like

    Start from domain boundaries and the parts that change most, use a strangler approach, plan for shared data and distributed transactions, and invest in observability first.

  • Design a distributed cache. How do you handle node failures and hot keys?

    What good looks like

    Consistent hashing, replication, eviction policy, protection against cache stampedes, and the consistency guarantees callers can actually live with.

  • Design a real-time chat system with one-to-one and group messages.

    What good looks like

    Connection handling (WebSockets), ordering and delivery receipts, offline storage and sync, fan-out for groups, and presence.

08Every loop0/4

Behavioural

Every interview loop has a behavioural round. For lead and manager roles, the focus is on people decisions, prioritisation and leading through change. Use the STAR structure.

  • Describe a piece of feedback that changed how you work.

    What good looks like

    State the feedback, your honest first reaction and the concrete behaviour you changed. Close with evidence that the change stuck.

  • Tell me about a mistake you made at work and what happened next.

    What good looks like

    Own it without blaming others, explain how you contained the impact, and what you changed so it would not happen again.

  • Describe the most complex technical or analytical problem you have solved.

    What good looks like

    Explain why it was hard, the options you considered, how you de-risked the chosen approach, and what you would do differently now.

  • Why do you want this role, and why now?

    What good looks like

    Connect two or three specific requirements of the role to your experience and to a direction you are deliberately moving in. Generic praise of the company scores poorly.

09Leadership0/3

Leadership

The title marks this as a senior leadership role. Expect questions on hiring, developing people and setting priorities.

  • How do you handle a team member who is consistently underperforming?

    What good looks like

    Diagnose first (skills, motivation or context), set clear written expectations, support with a time-boxed plan, and be ready to make a fair hard call.

  • Tell me about a time you resolved a conflict between two people on your team.

    What good looks like

    Show you addressed it early and privately, focused on behaviours and shared goals rather than personalities, and followed up afterwards.

  • How do you balance delivery pressure against technical debt or quality?

    What good looks like

    Give a concrete mechanism (a capacity budget, a debt register, quality gates) and an example where you made the trade-off explicit to stakeholders.

Company research brief: Goldman Sachs

From the roles we track on LYDJ, refreshed daily from the official careers page.

49

open roles

49

added in 30 days

11

in Engineering

Banking & Financial ServicesGCC

Hiring most for

  • Other19
  • Engineering11
  • Operations9
  • Finance & Legal8

Cities

Bengaluru · 37Hyderabad · 12
See all 49 roles at Goldman Sachs →

Read before the interview

Questions to ask them

  • ›There are several open Engineering roles at Goldman Sachs right now. How is the team growing, and where does this role fit?
  • ›The company hires in Bengaluru, Hyderabad. How do teams across locations work together day to day?
  • ›How does the team use Git and System design today, and what would you like to change?
  • ›What does success look like in this role after six months?
  • ›What is the biggest challenge the team is facing this year?

Preparation checklist

0/8 done

Saved in this browser only.

Interview prep: The Core Engineering-L2-Hyderabad-Vice President-Software Engineering at Goldman Sachs | LYDJ