Whether you target TCS, Infosys, a Series A startup in Bengaluru, or a remote-first product company, web developer interviews follow predictable pillars: aptitude and DSA, core CS fundamentals, JavaScript/TypeScript depth, framework knowledge (usually React), practical coding, and behavioral fit. Missing any pillar can end an otherwise strong candidacy.
This guide is written for frontend-focused, full-stack-leaning, and junior web developers preparing in India’s 2026 hiring market. Adjust timelines if you have six months instead of six weeks—we include both.
Interview Round Breakdown (What to Expect)
- Online assessment (OA): 2–4 coding or MCQ problems, often on HackerRank, Codility, or company platforms.
- Technical phone/video: 45–60 minutes, one DSA problem plus resume discussion.
- Machine coding: Build a UI component or mini-app in 90–120 minutes (React common).
- DSA + problem solving: Arrays, strings, trees, graphs, dynamic programming (varies by company tier).
- Hiring manager / culture: Motivation, past projects, salary expectations, notice period.
- System design (mid-senior): Design URL shortener, news feed, autocomplete, or “design Instagram stories UI architecture.”
6-Week Intensive Preparation Plan
- Week 1: Audit resume + GitHub. Revise HTML semantics, CSS Flexbox/Grid, accessibility basics (WCAG awareness).
- Week 2: JavaScript: closures, event loop, promises/async-await, prototypes, ES6+ features. 30 LeetCode easy/medium.
- Week 3: React: hooks, state management, performance (memo, useMemo), keys, controlled forms. Build one machine-coding-style component library.
- Week 4: DSA focus: arrays, hash maps, two pointers, sliding window, BFS/DFS. 40 medium problems with pattern notes.
- Week 5: Mock interviews, timed machine coding (Todo, pagination, debounced search). Record yourself explaining aloud.
- Week 6: Company-specific prep, revise weak areas, rest 1 day before onsite.
JavaScript Questions You Must Know
- Explain event loop, microtasks vs macrotasks.
- Difference between == and ===; typeof quirks.
- Implement debounce and throttle from scratch.
- Shallow vs deep copy; spread vs Object.assign.
- Promise.all vs Promise.allSettled use cases.
- What is closure? Give a real UI example (e.g. private counter in a hook).
- How does `this` work in arrow vs regular functions?
- Explain CORS and how you solved a cross-origin issue in a project.
React & Frontend Topics (High Frequency)
- Virtual DOM and reconciliation (conceptual—no need to memorize source code).
- useEffect pitfalls: missing dependencies, infinite loops, cleanup.
- When to lift state up vs Context vs Zustand/Redux.
- Optimizing re-renders in lists with hundreds of items.
- SSR vs CSR vs SSG (Next.js vocabulary helps even for CRA developers).
- Security: XSS prevention, sanitizing user HTML, env variables for API keys.
DSA Patterns for Web Developer Roles
Product companies expect more mediums; many service companies accept strong easy/medium performance with clean code. Prioritize these patterns:
- Arrays & strings: two sum, anagram groups, longest substring without repeat.
- Trees: level order traversal, max depth, validate BST.
- Graphs: number of islands, BFS shortest path (grid).
- Dynamic programming: climbing stairs, coin change (intro level), kadane’s algorithm.
- Stacks/queues: valid parentheses, implement queue using stacks.
System Design for Frontend Engineers
You may not design a global CDN on day one, but you should discuss component architecture, API contracts, caching, pagination, WebSockets for live data, and error boundaries. Practice explaining how you would build:
- Infinite scroll feed (Intersection Observer + cursor pagination).
- Typeahead search with debouncing and cancellation (AbortController).
- Multi-step form wizard with validation and draft save (localStorage/backend).
- Real-time notification bell (polling vs WebSocket tradeoffs).
Resume & Project Talking Points
For each project on your resume, prepare a 2-minute story: problem, your role, tech stack, hardest bug, metric (performance, users, load time). Interviewers probe one project deeply. MERN stack projects are common—be ready to explain API design, auth (JWT), and database schema.
Day-Before & Interview-Day Checklist
- Test camera, mic, and internet; have backup mobile hotspot.
- Keep IDE familiar (VS Code) with extensions you know—do not experiment.
- Clarify requirements before coding; state assumptions.
- Think aloud; write pseudocode for hard problems.
- Ask thoughtful questions at the end about team stack and mentorship.
- Send a thank-you email within 24 hours if you have recruiter contact.
Consistent preparation beats cramming. Use ConnectByTech’s Jobs Board to apply in parallel with studying—real deadlines motivate discipline. Track every application and tailor your resume keywords to each JD’s stack (React, Vue, Angular, Node).