NVIDIA roles split: software DSA tracks vs CUDA/systems tracks. Match prep to the JD. Coding quality is non-negotiable either way.
What actually rejects people
Applying to GPU/systems roles with only web-dev prep.
First round: NVIDIA coding + domain interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
DSA 50%
CS + projects 25%
Behavioral 15%
Mocks 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA / screen
timed
Coding
Tech interviews
multiple
DSA and/or systems/GPU
DSA & Algorithms (40% time) - Focus on arrays, strings, trees, graphs, dynamic programming
Computer Architecture (25%) - CPU/GPU architecture, parallel computing, CUDA basics
System Design (20%) - Scalability, distributed systems
Coding Practice (10%) - Solve 300+ problems on LeetCode
Interview Prep (5%) - Prepare for technical and HR interviews
One timed block that matches NVIDIA’s first round (coding OA)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
Core DSA (arrays, hashing, strings)
Timed easy→medium comfort
3-4
Trees, graphs, recursion
Explain traversals + complexity
5-6
DP + company-flavored mocks
2-problem mock passes
7
Projects + CS fundamentals
Resume bullets defended
8
Behavioral + polish
No new topics; only closure
Order problems by confidence after a 3-4 minute skim
Passing test cases beats a brilliant half-solution
Invent edge cases before submit; watch timeboxes
Restate → brute force → optimize → code → test
Defend edge cases and code clarity.
Tie CS answers to a project when it strengthens the point
Why NVIDIA, why this team/role, location flexibility
STAR with a metric; pick 2-3 real company values and prepare proof
Strong DSA for SWE
Computer architecture / parallelism basics for many teams
Medium DSA fluency
Clean code + edge cases
OOPs + DBMS basics
Measurable project stories
Domain scenarios for this product
API/design intuition at fresher depth
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Applying to GPU/systems roles with only web-dev prep - fix this first
Preparing only interviews while failing NVIDIA’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Domain buzzwords without engineering reasoning
Intel · Qualcomm · Cisco · Google · Microsoft · Samsung
Next step: Run one timed mock this week that matches NVIDIA’s first round (coding OA), then build the weeks around your weakest section - not around what is most fun to study.