SECTION 01
30–45 Day Interview Roadmap
Focused plan for 3–5 LPA frontend / full-stack roles. No fluff — only what actually gets asked.
★ You already know Strings + Arrays in Java. That's a head start. This roadmap builds on that.
Days 1–10 · Phase 1
DSA Core + JavaScript Fundamentals
Complete DSA topics: Hashing, Two Pointers, Sliding Window, Stack, Queue, LinkedList. Simultaneously revise JS core: closures, promises, event loop, ES6+ features.
HashMap
Two Pointers
Sliding Window
Stack/Queue
JS Core
Days 11–20 · Phase 2
Trees + React Deep Dive
Binary Trees, Binary Search, Recursion basics. React: hooks, lifecycle, state management, rendering. This is the most-tested combo at 3–5 LPA companies.
Binary Trees
Binary Search
React Hooks
State Mgmt
Days 21–30 · Phase 3
CS Fundamentals + Backend Basics
OS, DBMS, CN (only the 30 most-asked concepts). REST API design, JWT, MongoDB basics. Go through your projects and prepare answers for every design decision you made.
OS/DBMS/CN
REST APIs
JWT Auth
Project Q&A
Days 31–45 · Phase 4
Mock Interviews + Revision + Applications
Full mock interviews (DSA + HR + Technical). Revise all weak spots. Apply actively on Wellfound, Cutshort, Instahyre. This phase is 50% prep, 50% applications.
Mock Rounds
HR Prep
Applications
What to skip at 3–5 LPA level
❌ Skip These
Dynamic Programming (advanced)
Graph algorithms (BFS/DFS unless basic)
System Design (not asked at fresher level)
Segment Trees, Tries
Kubernetes, Docker (unless specifically asked)
Microservices architecture patterns
Graph algorithms (BFS/DFS unless basic)
System Design (not asked at fresher level)
Segment Trees, Tries
Kubernetes, Docker (unless specifically asked)
Microservices architecture patterns
✓ Focus On These
Arrays, Strings, HashMap, LinkedList
Stack, Queue, Trees, Binary Search
React hooks, JS closures, async/await
REST API + JWT + MongoDB basics
OS/DBMS/CN fundamentals (top 30 topics)
Your 3 projects — deeply
Stack, Queue, Trees, Binary Search
React hooks, JS closures, async/await
REST API + JWT + MongoDB basics
OS/DBMS/CN fundamentals (top 30 topics)
Your 3 projects — deeply
SECTION 02
DSA Plan (Java)
60–70 problems. Patterns over memorization. Timed practice every Sunday.
| Week | Topics | Daily Target | Key Patterns |
|---|---|---|---|
| Week 1 | Hashing, Two Pointers, Sliding Window | 2–3 problems | Frequency map, window shrink, fast-slow ptr |
| Week 2 | Stack, Queue, Linked List, Recursion | 2–3 problems | Monotonic stack, dummy node, base case first |
| Week 3 | Binary Trees, Binary Search | 2–3 problems | DFS (pre/in/post), BFS level order, search space |
| Week 4 | Revision + Mixed mocks | 3–4 problems | Timed practice — 3 problems in 60 mins |
Must-know problem list
Arrays & Strings Already Started
Two Sum · Best Time to Buy Stock · Maximum Subarray (Kadane's) · Move Zeros · Rotate Array · Valid Anagram · Longest Substring Without Repeat · Group Anagrams · Product of Array Except Self
HashMap + Two Pointers + Sliding Window
First Non-Repeating Character · Subarray Sum Equals K · Pair with Given Sum · Container with Most Water · 3Sum · Trapping Rain Water (medium) · Minimum Window Substring · Longest Repeating Character Replacement
Stack, Queue, Linked List
Valid Parentheses · Next Greater Element · Min Stack · Reverse Linked List · Detect Cycle (Floyd's algorithm) · Merge Two Sorted Lists · Remove Nth Node From End · Implement Queue Using Stacks
Trees + Binary Search
Inorder / Preorder / Postorder Traversal · Height of Tree · Diameter of Tree · Level Order Traversal (BFS) · Lowest Common Ancestor · Validate BST · Classic Binary Search · First & Last Position · Search Rotated Array
Java template to use in every solution
// Pattern: Two Pointers
public int[] twoSum(int[] nums, int target) {
Map<Integer, Integer> map = new HashMap<>();
for (int i = 0; i < nums.length; i++) {
int complement = target - nums[i];
if (map.containsKey(complement)) {
return new int[]{map.get(complement), i};
}
map.put(nums[i], i);
}
return new int[]{}; // never reached
}
// Always: 1. Understand 2. Brute force 3. Optimize 4. Edge cases
★ Interview tip: Talk while you code. Say "I'm using a HashMap here because lookups are O(1)". This shows you understand WHY, not just HOW.
SECTION 03
Frontend Interview Prep
React + JavaScript. Only what actually gets asked at 3–5 LPA companies.
JavaScript — Must Know Concepts
What is a closure?
A closure is a function that remembers variables from its outer scope even after the outer function has returned.
function counter() {
let count = 0;
return function() { count++; return count; };
}
const inc = counter();
inc(); // 1
inc(); // 2 — count is "remembered" via closure
Real use: data privacy, event handlers, setTimeout loops, memoization
What is event delegation?
Instead of adding event listeners to each child element, add one listener to the parent. It uses event bubbling — events bubble up to the parent automatically.
document.getElementById('list').addEventListener('click', (e) => {
if (e.target.tagName === 'LI') {
console.log(e.target.textContent); // works for all li children
}
});
Promise vs async/await — what's the difference?
Same thing underneath. async/await is cleaner syntax for Promises — it makes async code look synchronous. Always use try/catch with async/await for error handling.
// Promise way
fetchData().then(data => use(data)).catch(err => handle(err));
// async/await — cleaner, same result
async function load() {
try {
const data = await fetchData();
use(data);
} catch (err) { handle(err); }
}
React — Most Frequently Asked Topics
| Topic | What to Know | Depth Needed |
|---|---|---|
| useState / useEffect | State updates, dependency array, cleanup | Deep — always asked |
| useRef | DOM access, persist values without re-render | Medium |
| useMemo / useCallback | Prevent unnecessary re-renders, when to use each | Medium — know the difference |
| useContext | Global state without prop drilling | Medium |
| Custom Hooks | Extracting reusable logic (e.g., useFetch) | Medium — build one example |
| Virtual DOM | What it is, how reconciliation works, why React is fast | Conceptual |
| Key prop | Why keys matter in lists, what happens without them | Know the reason |
| Controlled vs Uncontrolled | Forms — React state vs DOM state | Light |
| Redux Toolkit | Slice, createAsyncThunk, useSelector, useDispatch | Medium (you already used it) |
useEffect — explain the dependency array
useEffect(() => { ... }); // runs after EVERY render
useEffect(() => { ... }, []); // runs ONCE on mount
useEffect(() => { ... }, [count]); // runs when count changes
// Cleanup example (important for subscriptions/timers)
useEffect(() => {
const id = setInterval(tick, 1000);
return () => clearInterval(id); // cleanup on unmount
}, []);
Next.js — What Freshers Get Asked
SSR vs CSR vs SSG
SSR: HTML generated on server per request. Good for dynamic, SEO-heavy pages.
CSR: JavaScript runs in browser. Fast after load, poor initial SEO.
SSG: HTML generated at build time. Fastest — use for blogs, docs, marketing pages.
CSR: JavaScript runs in browser. Fast after load, poor initial SEO.
SSG: HTML generated at build time. Fastest — use for blogs, docs, marketing pages.
App Router basics
File-based routing:
Server Components by default. Use
API routes:
app/about/page.tsx = /aboutServer Components by default. Use
'use client' only when you need interactivity or browser APIs.API routes:
app/api/route.ts
TypeScript — Fresher-level concepts asked
// Utility types — frequently asked
type Partial<User> = { name?: string; age?: number } // all fields optional
type Pick<User, 'name'> = { name: string } // pick fields
type Omit<User, 'age'> = { name: string } // exclude fields
type Record<string, number> = { [key: string]: number } // key-value map
// Interface vs Type — both work; prefer interface for objects
interface User { name: string; age: number; }
type Status = 'active' | 'inactive'; // type for unions
SECTION 04
Backend & Full Stack Basics
Only what freshers actually get asked. Keep it practical.
REST API — Must Know
| Concept | Simple Explanation |
|---|---|
| HTTP Methods | GET (read), POST (create), PUT (replace), PATCH (partial update), DELETE (remove) |
| Status Codes | 200 OK, 201 Created, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Server Error |
| REST principles | Stateless, client-server, uniform interface, resource-based URLs |
| CORS | Browser security — server must allow cross-origin requests via headers |
| JSON vs XML | JSON is lighter, easier to parse. REST APIs use JSON. XML is legacy. |
JWT Authentication — How to Explain It
How JWT works (explain this as a story):
1. User logs in with email + password
2. Server verifies credentials and creates a JWT token (3 parts: header.payload.signature)
3. Server sends token to client — client stores it (usually localStorage or cookie)
4. Every future request includes this token in the Authorization header
5. Server verifies the token's signature — if valid, grants access
Why JWT? Stateless — server doesn't need to store session data. Scales well.
1. User logs in with email + password
2. Server verifies credentials and creates a JWT token (3 parts: header.payload.signature)
3. Server sends token to client — client stores it (usually localStorage or cookie)
4. Every future request includes this token in the Authorization header
5. Server verifies the token's signature — if valid, grants access
Why JWT? Stateless — server doesn't need to store session data. Scales well.
MongoDB — Key Concepts
// CRUD operations — know these cold
db.users.insertOne({ name: "Pruthvi", role: "dev" });
db.users.find({ role: "dev" });
db.users.updateOne({ name: "Pruthvi" }, { $set: { role: "senior" } });
db.users.deleteOne({ name: "Pruthvi" });
// Aggregation (often asked)
db.orders.aggregate([
{ $group: { _id: "$userId", total: { $sum: "$amount" } } }
]);
CS Fundamentals — Top 20 Topics to Know
OS (8 topics)
Process vs Thread · Context Switching
Deadlock + Coffman conditions
CPU Scheduling: FCFS, SJF, Round Robin
Paging vs Segmentation
Virtual Memory + Page Faults
Mutex vs Semaphore
Deadlock + Coffman conditions
CPU Scheduling: FCFS, SJF, Round Robin
Paging vs Segmentation
Virtual Memory + Page Faults
Mutex vs Semaphore
DBMS (7 topics)
ACID properties (must know by heart)
Normalization: 1NF, 2NF, 3NF
Types of Joins (inner, outer, self)
Indexing — why it speeds up queries
Transactions and Rollback
SQL: GROUP BY, HAVING, subqueries
Normalization: 1NF, 2NF, 3NF
Types of Joins (inner, outer, self)
Indexing — why it speeds up queries
Transactions and Rollback
SQL: GROUP BY, HAVING, subqueries
Computer Networks (5 topics)
OSI Model — all 7 layers, simplified
TCP vs UDP (connection vs connectionless)
HTTP vs HTTPS (SSL/TLS)
DNS — how domain resolves to IP
Cookies vs Sessions vs JWT
TCP vs UDP (connection vs connectionless)
HTTP vs HTTPS (SSL/TLS)
DNS — how domain resolves to IP
Cookies vs Sessions vs JWT
OOP Concepts (always asked)
4 pillars: Encapsulation, Abstraction,
Inheritance, Polymorphism
Abstract class vs Interface (Java)
Method overloading vs overriding
SOLID principles — just S and O
Inheritance, Polymorphism
Abstract class vs Interface (Java)
Method overloading vs overriding
SOLID principles — just S and O
SECTION 05
Project-Based Interview Questions
Questions you will actually be asked about Agentix, SmartSupport, and JobConnect.
Strategy: For every project answer, follow this format → Problem → Tech choice → Challenge → Outcome. Never just describe what the project does. Explain WHY you made the decisions you made.
Agentix – AI Agent Creation Platform
Walk me through your Agentix project.
"Agentix is an AI agent builder where users can visually design multi-step AI workflows using a drag-and-drop canvas. I built it with Next.js and TypeScript for the frontend, Convex for the real-time database, Clerk for authentication, and the Google Gemini API for AI responses. The visual canvas is built with React Flow. The biggest challenge was managing real-time state synchronization between the canvas and the database — Convex's reactive queries solved that cleanly. Users can build, publish, and run AI agents without writing code."
Keep this under 90 seconds. Practice it out loud.
Why did you choose Convex over a traditional database like MongoDB?
"Convex provides real-time reactivity out of the box — any change in the database instantly reflects on the UI without polling. For an agent builder where multiple state changes happen rapidly, this was a much better fit than MongoDB with manual refresh logic. Convex also handles server functions securely which reduced the need for a separate Express backend."
How did you handle authentication and authorization in Agentix?
"I used Clerk for authentication — it provides pre-built UI components for login/signup, handles JWT token generation, and integrates directly with Convex. On every Convex function, I validate the user's identity using the Clerk user ID from the token. For rate limiting and bot protection, I used Arcjet — it checks each request before it hits my application logic."
What was the hardest bug you fixed in this project?
"The hardest bug was a TypeScript type error where Convex's Id type wasn't being inferred correctly in my schema, causing build failures on Vercel. The error was in how I was referencing the user table ID — I had to explicitly type it as Id<'UserTable'> instead of a generic string. This taught me the importance of strict TypeScript generics with ORM-like tools."
Honest, specific, shows debugging skills. Perfect answer.
SmartSupport – AI Business Chat Assistant
What is multi-tenancy and how did you implement it?
"Multi-tenancy means multiple businesses (tenants) use the same application, but their data is completely isolated. In SmartSupport, each business gets their own AI chat widget with a unique API key. When an end user sends a message, the request includes that business's API key. On the backend, I validate the key, fetch that business's trained data (their FAQs, product info), and pass it as context to the Gemini API. This way each business gets a personalized AI assistant without any data leaking between tenants."
How does the embeddable widget work technically?
"The widget is a small JavaScript snippet — similar to how Google Analytics works. Business owners add a script tag to their website with their unique business ID. The script dynamically loads the chat widget, which is a React component hosted on my server. The widget communicates with my Next.js API routes to get AI responses. This approach keeps the widget lightweight and doesn't require businesses to install any packages."
JobConnect – Full Stack Job Portal
How did you implement role-based access control (RBAC)?
"I defined three roles: Admin, Employer, and Candidate — stored in the user's MongoDB document. After login, the JWT token includes the user's role. On protected routes, middleware checks this role before allowing access. For example, only employers can post jobs, and only admins can manage all users. On the frontend, I conditionally render UI elements based on the role stored in Redux state."
How is JWT authentication different from session-based auth?
"Session-based auth stores the session on the server — the server must look up every request. JWT is stateless — the token itself contains the user info. The server just verifies the signature. JWTs scale better because any server instance can validate the token without a shared database. The tradeoff is that you can't instantly invalidate a JWT — for that, you'd use a token blacklist or short expiry times."
SECTION 06
HR & Behavioural Questions
Sample answers tailored to your background. Customize the details, keep the structure.
Formula: Most HR answers work best with this structure — Situation → Action → Result (SAR). Keep each answer under 90 seconds.
Tell me about yourself.
"I'm Pruthviraj Gaikwad, a 2024 BE IT graduate from Dr. D. Y. Patil Institute of Technology, Pune. Over the past year, I've focused on frontend and full-stack development — primarily using React, Next.js, and TypeScript. I've built three full production-grade projects: Agentix, an AI agent builder; SmartSupport, a multi-tenant AI chat assistant; and JobConnect, a full-stack job portal with role-based access control. I'm comfortable working across the stack but my strongest interest is in frontend — building interfaces that are both functional and well-designed. I'm currently looking for my first full-time role where I can contribute real value while continuing to grow as an engineer."
Practice this until it sounds natural. This is your first impression.
Why do you want to join our company?
Template — research the company first and fill in the blank:
"I've been following [Company] because [specific reason — product, tech stack, growth stage]. What specifically attracted me is [something concrete — their tech, mission, product]. As a fresher who has already built [reference a project], I think I can contribute to [something specific about their work] from day one, while learning from the team around me."
"I've been following [Company] because [specific reason — product, tech stack, growth stage]. What specifically attracted me is [something concrete — their tech, mission, product]. As a fresher who has already built [reference a project], I think I can contribute to [something specific about their work] from day one, while learning from the team around me."
Never say "good salary" or "good culture" without being specific. Startups want someone who cares about their actual product.
What is your biggest weakness?
"I sometimes spend too much time perfecting the frontend details — polishing UI components beyond what's required for the MVP. I've been working on this by setting a time box for UI work and consciously asking myself whether something is 'good enough to ship' before going deeper. It's getting better, and I've learned to separate 'production-ready' from 'perfect'."
Real weakness + active fix = great answer. Don't say "I work too hard."
Describe a challenge you faced in a project and how you solved it.
"During Agentix, I had a persistent Vercel build failure that was blocking deployment for two days. The error was a TypeScript type mismatch with Convex's Id generic type — it wasn't obvious from the error message. I systematically isolated the error by commenting out sections, read the Convex documentation more carefully, and realized I needed to explicitly type the reference as Id<'UserTable'>. After fixing it, I also added a pre-commit TypeScript check to catch similar issues earlier. The lesson was to read error messages carefully and read the source documentation rather than guessing."
Where do you see yourself in 3 years?
"In 3 years, I want to be a confident mid-level frontend or full-stack engineer who has shipped features that real users love. I want to have strong experience with production systems — performance, scaling, edge cases — the things you only learn on real projects with real users. If the company grows, I'd love to grow with it and eventually mentor newer engineers joining the team."
Why should we hire you over other freshers?
"Most freshers can show classroom projects. I've built and deployed three full-stack applications that are live on Vercel and Render. I've faced real production bugs — TypeScript type errors in Convex, JWT auth issues, Vercel build failures — and debugged them independently. I understand not just what to build but why to make certain technical choices. I'm practical, I learn fast, and I'm already thinking like an engineer who has to ship, not just complete assignments."
SECTION 07
Mock Interview Strategy
How to practice effectively so you're ready when it actually counts.
Mock DSA Round
Pick 2 random LeetCode Easy/Medium problems
Set a 45-min timer
Write the solution in Java — no hints
Talk out loud as you write
Review after: what took too long? Why?
Set a 45-min timer
Write the solution in Java — no hints
Talk out loud as you write
Review after: what took too long? Why?
Mock Technical Round
Ask a friend to interview you — or record yourself
Answer React/JS/CS questions out loud
Use a blank doc — no notes
Questions to cover: 5 React, 3 JS, 3 CS fundamentals
Time limit: 30 mins
Answer React/JS/CS questions out loud
Use a blank doc — no notes
Questions to cover: 5 React, 3 JS, 3 CS fundamentals
Time limit: 30 mins
Mock HR Round
Record yourself on your phone
Answer all 6 HR questions in Section 06
Watch the recording — check pace, clarity, confidence
Fix one thing each time you do it
Goal: 90 seconds per answer, no filler words
Answer all 6 HR questions in Section 06
Watch the recording — check pace, clarity, confidence
Fix one thing each time you do it
Goal: 90 seconds per answer, no filler words
Full Mock Interview
Once a week from Week 3 onward
DSA (30 min) → Technical (20 min) → HR (15 min)
With a friend OR on Pramp / Interviewing.io
Treat it exactly like a real interview
Review + fix one weak area after each
DSA (30 min) → Technical (20 min) → HR (15 min)
With a friend OR on Pramp / Interviewing.io
Treat it exactly like a real interview
Review + fix one weak area after each
How to explain your answer clearly in an interview
For DSA problems:
1. "I understand the problem — I need to find..."
2. "My first thought is brute force — that's O(n²)"
3. "Can I do better? Yes — using a HashMap..."
4. "Time complexity: O(n). Space: O(n)."
5. "Edge cases: empty array, single element, duplicates."
For concept questions:
1. Define it simply in one sentence
2. Give a real-world example or code example
3. Mention when you'd use it (context)
1. "I understand the problem — I need to find..."
2. "My first thought is brute force — that's O(n²)"
3. "Can I do better? Yes — using a HashMap..."
4. "Time complexity: O(n). Space: O(n)."
5. "Edge cases: empty array, single element, duplicates."
For concept questions:
1. Define it simply in one sentence
2. Give a real-world example or code example
3. Mention when you'd use it (context)
Resources to use
| Resource | What For | How Much |
|---|---|---|
| LeetCode | DSA practice (Easy + Medium only) | 60–70 problems total |
| Striver's A2Z Sheet | Curated problem order for DSA | Follow the order |
| Gate Smashers (YouTube) | OS, DBMS, CN in simple Hindi/English | 1–2 videos/day |
| JavaScript.info | JS deep dive — closures, prototypes, async | Read relevant chapters |
| Pramp / Interviewing.io | Free mock interviews with real peers | 1/week from Week 3 |
| IndiaBix / PrepInsta | Aptitude tests for campus-style companies | 1 test/day in Week 6 |
SECTION 08
Resume Improvement
ATS-optimized. Frontend-focused. Recruiters spend 8 seconds — make it count.
✓ Must Include
Skills section at the top — not buried at the bottom
Each project: tech stack + live link + GitHub link
Bullet points with numbers: "Reduced load time by 40%"
Deployed links (Vercel / Render) — shows real shipping
GitHub profile link — with pinned repos
Education: CGPA 7.72 — include, it's decent
1 page only — strict rule for freshers
Each project: tech stack + live link + GitHub link
Bullet points with numbers: "Reduced load time by 40%"
Deployed links (Vercel / Render) — shows real shipping
GitHub profile link — with pinned repos
Education: CGPA 7.72 — include, it's decent
1 page only — strict rule for freshers
✗ Remove These
Objective statement ("I am seeking a role...")
"References available on request"
Skills you can't answer questions about
Projects without deployed links
Responsibilities framing ("Was responsible for...")
Course certificates (unless from top platforms)
Photo / date of birth / address (unnecessary)
Full-stack label if targeting frontend roles
"References available on request"
Skills you can't answer questions about
Projects without deployed links
Responsibilities framing ("Was responsible for...")
Course certificates (unless from top platforms)
Photo / date of birth / address (unnecessary)
Full-stack label if targeting frontend roles
Project bullet point formula
Bad: "Built a job portal with React and Node.js"
Good: "Built JobConnect, a full-stack job portal using MERN stack with JWT authentication and RBAC, supporting 3 distinct user roles (Admin, Employer, Candidate) — deployed on Render and Vercel"
Good: "Built JobConnect, a full-stack job portal using MERN stack with JWT authentication and RBAC, supporting 3 distinct user roles (Admin, Employer, Candidate) — deployed on Render and Vercel"
Skills section — how to list yours
// Your resume skills section — ordered by relevance to frontend roles
Languages: JavaScript (ES6+), TypeScript, Java
Frontend: React.js, Next.js, Tailwind CSS, ShadCN UI, HTML5, CSS3
State Mgmt: Redux Toolkit, React Context, React Hooks
Backend: Node.js, REST APIs, JWT Authentication
Database: MongoDB, Firebase, Convex
AI/APIs: Google Gemini API, Clerk, Arcjet, Vercel AI SDK
Tools: Git, GitHub, VS Code, Postman, Vercel, Render
ATS Tips
• Use keywords from the job description — mirror their language
• Section headings must be standard: "Work Experience", "Projects", "Education", "Skills" — ATS won't parse custom headings
• Avoid tables and columns in resume — ATS reads left to right, line by line
• File format: PDF (from LaTeX or Overleaf — not Google Docs export)
• Font: readable, 10–11pt body. Don't use multiple fonts.
• File name:
• Section headings must be standard: "Work Experience", "Projects", "Education", "Skills" — ATS won't parse custom headings
• Avoid tables and columns in resume — ATS reads left to right, line by line
• File format: PDF (from LaTeX or Overleaf — not Google Docs export)
• Font: readable, 10–11pt body. Don't use multiple fonts.
• File name:
Pruthviraj_Gaikwad_Frontend_Developer.pdf
SECTION 09
Daily Schedule
5–6 hours/day. Structured. Realistic. No burnout.
Daily Time Blocks
9:00 – 11:00 AM
DSA Practice
2 LeetCode problems. Write solution, analyze complexity, check edge cases. No peeking at solutions until 20+ mins of genuine effort.
11:00 – 1:00 PM
Frontend / React + CS Fundamentals
Alternate daily — Mon/Wed/Fri: React+JS concepts. Tue/Thu/Sat: OS/DBMS/CN (Gate Smashers + make notes).
1:00 – 2:00 PM
Break + Lunch
Actually rest. Don't scroll prep content during this time.
2:00 – 3:30 PM
Project prep + Revision
Work through project-based Q&A (Section 05). Practice explaining your projects out loud. Polish GitHub READMEs. Fix any broken deployed links.
3:30 – 4:30 PM
HR + Aptitude
Mon/Wed/Fri: Practice HR answers out loud (record yourself). Tue/Thu/Sat: Aptitude — quant, logical reasoning (IndiaBix).
4:30 – 5:30 PM
Applications + Notes
Apply on Wellfound, Cutshort, Instahyre — 3–5 quality applications/day. Review what you learned today and write 5 key points in a notebook.
Sunday
Full Mock Interview Day
Morning: Timed DSA mock (3 problems, 60 mins). Afternoon: Technical + HR mock with a friend or recorded. Evening: Review what went wrong, plan next week.
Weekly Focus Summary
| Week | Primary Focus | DSA Target | Applications |
|---|---|---|---|
| Week 1 | Hashing, Two Pointers, Sliding Window + JS Core | 12–15 problems | Start building list |
| Week 2 | Stack, Queue, Linked List + React Hooks | 12–15 problems | Finalize resume |
| Week 3 | Trees, Binary Search + CS Fundamentals | 12–15 problems | 5/day on Wellfound |
| Week 4 | Backend basics + Project Q&A + HR prep | 10 revision | 5/day aggressive |
| Week 5–6 | Revision + Full mocks + Aptitude | Mixed practice | Keep applying daily |
Key rule: Apply while you prepare — don't wait until you feel "ready". You'll never feel 100% ready. Week 3 onwards, applications run in parallel every single day.