Interview practice plan

P

Sr Software Engineer

PayPal · Bengaluru

EngineeringSenior22 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 BootREST APIsGraphQLNoSQLKafkaCI/CDJavaScript

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 22 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 and JavaScript. 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.

  • Implement debounce, and explain when you would use debounce versus throttle.

    What good looks like

    Debounce waits for a pause (search input), throttle limits the rate (scroll handlers). Handle this, arguments and clearing the timer.

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

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

  • 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

Kafka

This role asks for Kafka.

  • Explain at-most-once, at-least-once and exactly-once delivery. How would you get effectively-once processing?

    What good looks like

    Idempotent producers and transactions, committing offsets after processing, and idempotent consumers keyed on a business id.

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

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

06Design round0/3

System design

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

  • Design a rate limiter for a public API.

    What good looks like

    Compare token bucket, fixed and sliding windows; decide where it lives (gateway or service), how counters are shared across nodes, and how clients learn they are limited.

  • Design an upload and processing pipeline for large documents such as resumes.

    What good looks like

    Direct-to-storage uploads with signed URLs, async processing through a queue, retries and a dead-letter queue, malware scanning, and status updates for the user.

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

07Every 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.

  • Describe a time you had several urgent priorities at once. How did you decide what to do first?

    What good looks like

    Explain your criteria (impact, deadlines, dependencies), how you communicated the trade-offs, and what you deliberately dropped or delayed.

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

  • Tell me about a time a project you owned was at risk of missing its date.

    What good looks like

    Show early detection, honest escalation and the scope, sequencing or resourcing levers you pulled. Avoid stories that end with "we all worked weekends".

  • 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 at PayPal | LYDJ