The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~70–90 min | Timed coding + fundamentals |
| Recruiter Screen | ~20–30 min | Fit, motivation, logistics |
| Technical Interview(s) | ~45–60 min each | DS/algorithms + CS fundamentals |
| Behavioral / Values | ~30–45 min | Ownership, collaboration, values fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~70–90 minA proctored set of coding problems (commonly on CodeSignal or HackerRank), usually three to four questions scaling from easy to medium-hard. Some sittings mix in short multiple-choice on core CS. You are typically expected to fully solve the majority, not just pass sample cases.
- Array and hash-map problems with tight time limits
- Sliding-window or two-pointer string manipulation
- Frequency counting and grouping over transaction-like records
- A single harder dynamic-programming or greedy question
- Matrix or grid traversal
- Drill NeetCode's core 75 list, prioritizing arrays, hashing, and two pointers
- Take timed CodeSignal/HackerRank practice sets to build speed under a clock
- Practice writing clean, fully-passing solutions rather than partial ones
- Review Big-O so you can pick the right structure quickly
- Chasing an elegant answer and running out of time on easy points
- Ignoring edge cases (empty input, duplicates, overflow) that hidden tests catch
- Most or all test cases passing with efficient complexity
- Readable code that would survive a hidden-test suite
Recruiter Screen
~20–30 minA conversational call covering your background, why Visa, location and role preferences, and rough timeline. Light technical probing may confirm your resume claims. This round is mostly about mutual fit and setting expectations.
- Why payments and why Visa specifically
- Walking through one project end to end
- Preferred tech stack and team type
- Availability and relocation flexibility
- Write a crisp two-minute background pitch
- Prepare one concrete reason tied to Visa's scale or mission (free: Visa newsroom and engineering blog)
- Have thoughtful questions about the team and tech ready
- Know your own resume projects cold
- Generic 'I want to grow' answers with no Visa-specific hook
- Being vague about your actual contribution on team projects
- Clear, specific motivation and communication
- Realistic expectations on role and location
Technical Interview(s)
~45–60 min eachOne or two live coding rounds where you solve medium-level problems while narrating your approach. Interviewers also probe OOP, data structures, complexity, and sometimes basics of operating systems, databases, or networking. Expect follow-ups that push you to optimize or handle new constraints.
- Trees and graph traversal (BFS/DFS)
- Designing and reasoning about hash-based lookups
- String and interval problems with optimization follow-ups
- OOP modeling of a small real-world entity
- Complexity trade-off discussion for two approaches
- Practice thinking aloud on a whiteboard or shared editor
- Refresh trees, graphs, and recursion with NeetCode/LeetCode medium sets
- Revise OOP principles and one database + one networking basic (free: GeeksforGeeks CS notes)
- Rehearse stating brute force first, then optimizing
- Coding silently instead of explaining your reasoning
- Freezing on optimization follow-ups instead of talking through trade-offs
- Structured problem breakdown before coding
- Comfort refactoring toward a better complexity
Behavioral / Values
~30–45 minA conversation on teamwork, conflict, failure, and how you handle ownership of critical systems. Given the payments domain, expect at least one question touching reliability, accountability, or ethical handling of sensitive data. Answers are best framed with concrete stories.
- A time you owned a mistake and fixed it
- Handling disagreement with a teammate or reviewer
- Delivering under a tight or shifting deadline
- Balancing speed against correctness on important code
- Prepare five STAR stories spanning conflict, failure, leadership, and impact
- Tie one story to reliability or careful handling of sensitive work
- Practice keeping answers to two minutes
- Read Visa's stated values to mirror their language honestly
- Rambling stories with no clear result or lesson
- Blaming others instead of showing ownership
- Specific, outcome-driven stories
- Genuine sense of accountability and teamwork
What to master
- Arrays, strings, and hash maps
- Two pointers and sliding window
- Trees, graphs, and recursion
- Dynamic programming basics
- Time and space complexity analysis
- Object-oriented design fundamentals
- Databases and SQL basics
- Operating systems and networking essentials
Eligibility
Role-based: new-grad and intern SWE roles typically target CS or related degrees with strong coding fundamentals; specific GPA or graduation-year cutoffs vary by campus posting and region.
Visa salary & compensation (2026)
Fintech GCC in India (Bengaluru) pays competitively; US pays strong base + RSUs + solid bonus, stable non-volatile equity.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SWE (new grad) | 0–2 yrs | ₹18–28 LPA | $130K–165K | base + RSUs + ~10% bonus |
| Software Engineer | 2–4 yrs | ₹28–42 LPA | $165K–210K | RSU refreshers begin |
| Senior SWE | 4–8 yrs | ₹45–70 LPA | $230K–300K | equity share grows |
| Staff/Lead SWE | 8–12 yrs | ₹75 LPA–1.1 Cr | $320K–410K | scope-driven |
| Distinguished Engineer | 12+ yrs | ₹1.2–1.8 Cr | $450K–600K | rare; org-wide impact |
How the package is structured
- Stable public equity (RSUs) plus a dependable annual bonus (~10–20%) make total comp predictable.
- India comp is base-weighted with smaller RSU grants than US bands.
- Promotions and moves into payments-core/crypto/AI orgs drive the biggest raises.
- Refreshers stack yearly and are the main lever for growing total comp.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1–3: rebuild arrays, hashing, and two-pointer fluency with timed sets
- Days 4–6: trees, graphs, and recursion mediums, explaining aloud
- Days 7–9: dynamic programming and greedy patterns, one hard per day
- Days 10–11: OOP, SQL, OS, and networking quick revision
- Day 12: two full mock OAs under strict time
- Days 13–14: prepare five STAR stories and Visa-specific motivation
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
How hard is the Visa OA compared to top tech companies?
Generally easier than FAANG bar-raisers but not trivial; solid command of arrays, hashing, and one medium DP or graph question usually carries you through.
Does Visa ask system design for new grads?
Full system design is uncommon at the new-grad level; expect small OOP modeling and reliability discussion instead of large-scale design.
How much does the behavioral round matter?
It matters. Visa weights ownership and careful handling of critical systems, so weak or blame-shifting stories can sink an otherwise strong technical showing.