Skip to content
FrontendHaltFrontendHalt

COMPANY TRACK

Razorpay

Use this track to prepare for dashboard-heavy fintech UI, API integration, TypeScript, and edge-case rigor.

Razorpay logo

Razorpay preparation is useful for frontend candidates who need to think like builders of developer and merchant tools. The value is in API-consuming UI: tables, filters, forms, webhooks, payment states, analytics, error handling, and precise TypeScript models.

SOURCE-BACKED EVIDENCE

  • Razorpay jobsOfficial

    Official jobs page gives role context but does not publish a standardized frontend loop.

  • Frontend candidate reportCandidate report

    Candidate reports mention project deep dives, design systems, component libraries, machine coding, JavaScript, React, CORS, error boundaries, and storage.

Prep recommendations below are derived from these sources. Candidate reports are useful signals, but they can vary by level, team, recruiter, and date.

RESEARCH NOTE - REVIEWED 2026-09-03

Razorpay does not publish a standardized public frontend interview guide. Treat this as domain-oriented preparation and ask the recruiter for the current assessment format.

What sources report

  • Razorpay's official jobs page gives role context but does not publish a standardized frontend loop.
  • Candidate reports mention project deep dives, design systems, component libraries, machine coding, JavaScript, React, CORS, error boundaries, cookies, session storage, and web fundamentals.
  • Recent frontend reports describe JavaScript fundamentals, output questions, 60-90 minute React machine coding, web fundamentals, system design, and hiring-manager discussion.

Question patterns

  • Machine coding commonly focuses on reusable, scalable React components rather than visual polish alone.
  • Payment and dashboard contexts make slow network, failed states, partial data, CORS, storage, and API modeling more important.
  • Project deep dives matter; candidates should be ready to discuss design systems, component decisions, performance, and trade-offs.

Practice tasks

  • Build a reusable searchable dropdown with keyboard navigation, loading state, empty state, large-list performance, and controlled/uncontrolled modes.
  • Build a transaction dashboard with filters, status badges, pagination, failed/pending states, details drawer, and export action.
  • Prepare answers for CORS, OPTIONS requests, cookies vs session storage, error boundaries, API retries, and React render behavior.

What to do first

  • Build a merchant dashboard: transactions table, filters, status badges, export action, empty states, failed states, and details panel.
  • Review TypeScript narrowing, discriminated unions, API response modeling, form validation, and error boundaries.
  • Prepare to explain failed payments, pending states, refunds, retries, and partial data.

What interviewers should notice

  • You model API states precisely instead of using loose any-shaped data.
  • You handle dashboards as workflows, not only tables on a screen.
  • You make edge cases visible and recoverable for users.

Avoid this prep trap

  • Ignoring TypeScript details in a data-heavy product context.
  • Treating all errors as the same UI state.

INTERVIEW FORMAT GUIDANCE

  • No standardized frontend interview sequence is published on Razorpay's public jobs site.
  • Confirm whether the active role uses live coding, machine coding, take-home work, frontend system design, or project discussions.
  • Prepare against the actual job description and use fintech scenarios only as domain practice, not as predicted questions.

FOCUS AREAS

  • TypeScript
  • API state
  • Dashboards
  • Edge cases

PREP TIPS

  • Brush up on TypeScript specifics such as narrowing and generics.
  • Practice the analytics-dashboard system design case.
  • Be rigorous about edge cases out loud.

Sources used

Interview processes change by role, level, location, and hiring cycle. Always use instructions from your recruiter as the current source of truth.

Back to all companies