Interview practice plan

P

Sr Software Engineer (Full Stack – React / Node.js / Java)

PayPal · Bengaluru

EngineeringSenior25 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.

ReactNode.jsJavaSpring BootGraphQLJavaScriptTypeScriptHTML & CSSREST APIsMicroservicesNoSQLKafkaCI/CD

Also named in the description, not covered below: NoSQL. 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 25 questions practised

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

01Required 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.

02Required skill0/3

JavaScript

This role asks for Node.js, JavaScript and HTML & CSS. These JavaScript questions cover the ground they share.

  • What is a closure? Give a practical use and a bug closures can cause.

    What good looks like

    A function remembering its lexical scope; uses include private state and factories; classic bug is var in a loop or a stale value captured in a callback.

  • How do you handle errors in async code? What happens to an unhandled promise rejection?

    What good looks like

    try/catch around await, .catch on chains, Promise.allSettled when partial failure is fine, and a global handler for logging unhandled rejections.

  • 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.

03Required skill0/3

Java

This role asks for Java and Spring Boot. These Java questions cover the ground they share.

  • 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.

  • How does Spring Boot auto-configuration decide which beans to create, and how do you override it?

    What good looks like

    Conditional annotations on classpath, properties and missing beans; override by defining your own bean, properties or exclusions, and debug with the conditions report.

  • Explain @Transactional: propagation, self-invocation and which exceptions trigger a rollback.

    What good looks like

    It is proxy-based, so calls within the same class bypass it; by default only unchecked exceptions roll back; know REQUIRED versus REQUIRES_NEW.

04Required 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.

05Required skill0/3

Kafka

This role asks for Kafka.

  • A consumer group is lagging badly. How do you diagnose and fix it?

    What good looks like

    Check lag per partition, slow processing versus too few partitions or consumers, rebalancing storms, and batching or scaling out.

  • How would you choose the number of partitions for a new topic?

    What good looks like

    Target throughput per partition, consumer parallelism, key distribution, and the cost of too many partitions; increasing later changes key-to-partition mapping.

  • How do you evolve message schemas without breaking consumers?

    What good looks like

    A schema registry with compatibility rules, optional fields with defaults, never changing a field's meaning, and versioned topics for breaking changes.

06Required skill0/3

CI/CD & IaC

This role asks for CI/CD.

  • Design a CI/CD pipeline for a service with many contributors. Which gates would you put before production?

    What good looks like

    Fast unit tests on every PR, integration and security scans, build once and promote the same artifact, staged environments, and automated rollback.

  • 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.

07Design round0/3

System design

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

  • Design a payment service that must never charge a customer twice.

    What good looks like

    Idempotency keys, a payment state machine, reconciliation with the provider, and at-least-once delivery with de-duplication rather than hoping for exactly-once.

  • 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 the REST API for a multi-tenant SaaS product.

    What good looks like

    Resource modelling, versioning, pagination, authentication and tenant isolation, idempotent writes, and a consistent error contract.

08Every loop0/4

Behavioural

Every interview loop has a behavioural round. For senior roles, expect probing on influence without authority, judgement under pressure and raising the bar for others. Use the STAR structure.

  • 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.

  • Tell me about a time you worked with unclear or changing requirements.

    What good looks like

    Show how you reduced ambiguity: clarifying questions, writing down assumptions, small experiments and getting explicit sign-off.

  • Tell me about a time you worked closely with a team in another time zone or culture.

    What good looks like

    Mention concrete practices (async updates, overlap hours, written decisions) and a moment where a misunderstanding was caught and fixed.

  • Describe a time you had to deliver bad news to a stakeholder.

    What good looks like

    Show that you told them early, came with options and a recommendation rather than just the problem, and kept their trust.

Company research brief: PayPal

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

14

open roles

8

added in 30 days

6

in Engineering

Banking & Financial ServicesGCC

Hiring most for

  • Engineering6
  • Other3
  • Data & AI3
  • Product1

Cities

Bengaluru · 13Chennai · 1
See all 14 roles at PayPal →

Read before the interview

Questions to ask them

  • ›There are several open Engineering roles at PayPal right now. How is the team growing, and where does this role fit?
  • ›The company hires in Bengaluru, Chennai. How do teams across locations work together day to day?
  • ›How does the team use React and Node.js 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: Sr Software Engineer (Full Stack – React / Node.js / Java) at PayPal | LYDJ