JavaScript & React Interview Questions for Frontend Developers

Frontend Interview Experience – A Small but Interesting Redux Debate Recently attended a frontend interview where the discussion covered HTML, CSS, JavaScript, React, GraphQL, and Microfrontends. During the React round, I was asked about the core pillars of Redux. I explained: • Store – holds the application state • Actions – plain JavaScript objects describing what happened • Reducers – pure functions that return the new state • Dispatch – sends actions to the store • Selectors – used to read data from the store Then came an interesting moment The interviewer mentioned that "Actions are functions, not objects." I respectfully shared my understanding that: In Redux, an Action is a plain JavaScript object with a mandatory type field. After the interview, I double-checked — and yes, Redux defines actions as plain objects. The likely confusion: What the interviewer referred to was Action Creators, which are functions that return action objects. Example: const addTodo = (text) => ({ type: "ADD_TODO", payload: text }); Key takeaway: • Action = Object • Action Creator = Function 🎯 Interviews are not just about right or wrong — they’re about clarity of concepts and communication. Curious to know — have you ever faced a situation where both perspectives were technically correct but misunderstood in interviews? #Frontend #React #Redux #JavaScript #InterviewExperience #Learning

🚀 React Interview Question Breakdown – Can You Spot the Issues? Recently, I came across some interesting React interview questions focused on debugging and code optimization. Sharing them here 👇 🔍 Question 1: Find the issues and fix them const items = useSelector(state => state.items); const [filtered, setFiltered] = useState(items); useEffect(() => { setFiltered(items.filter(i => i.name.includes(search))); }, []); 🔍 Question 2: Find the issues and fix them const handleLike = async () => { const newCount = likes + 1; setLikes(newCount); await api.updateLikes(newCount); if (condition) { setLikes(likes + 1); // Review point } }; #ReactJS #FrontendDevelopment #JavaScript #WebDevelopment #InterviewQuestions #ReactHooks

I asked this JavaScript question in a frontend interview… and many developers got it wrong. 👀 Question: What will be the output? console.log([] + []); Take a moment and think. Most developers expect an array as output. But the actual output is: "" Yes — an empty string. Why does this happen? In JavaScript, when we use the + operator with arrays, they are converted to strings first. [] → "" So internally JavaScript does this: "" + "" = "" That’s why the result is an empty string. Now it gets more interesting: console.log([] + {}); Output: "[object Object]" Because the object converts to a string representation. Why interviewers ask this They want to check your understanding of: Type coercion JavaScript internal conversions How the + operator works JavaScript can look simple… but its behavior can surprise even experienced developers. Frontend interviews don’t just test frameworks — they test JavaScript fundamentals. #JavaScript #FrontendDevelopment #CodingInterview #WebDevelopment #Developers #Programming

If you're a JS interviewer testing developers, please never ask questions like this: "What will be the output? console.log([] + []);" There's one simple correct answer - nothing Because it's unusual code we should never see in any project. Code review should reject it and replace it with something more readable and maintainable. If you need "[] + []" results, ask yourself: will your team understand what it solves? It's unreadable, hard-to-maintain code they'll strugle with. Even the author will struggle to maintain it after a month, let alone the team. As developers, we should care not just that code works, but that it's readable, maintainable, and team-friendly. So, if I highly don't recomend asking code review question like this, what better instead? Ask practical questions, for example: 1) what problem does the callback returned from useEffect solve, and when is it called? useEffect(() => { return => () => {} // this one }) 2) should we use"==" or "===" and why? 3) What happens if you use await inside a try/catch block versus returning the promise directly? 4) etc... To recap: If you're an interviewer, ask about JS code used in common projects (or your project specifically). Don't hurt people with unusual theoretical questions like 'what happens with 3 + "3" - it makes no sense to memorize info we'll never use.

I asked this JavaScript question in a frontend interview… and many developers got it wrong. 👀 Question: What will be the output? console.log([] + []); Take a moment and think. Most developers expect an array as output. But the actual output is: "" Yes — an empty string. Why does this happen? In JavaScript, when we use the + operator with arrays, they are converted to strings first. [] → "" So internally JavaScript does this: "" + "" = "" That’s why the result is an empty string. Now it gets more interesting: console.log([] + {}); Output: "[object Object]" Because the object converts to a string representation. Why interviewers ask this They want to check your understanding of: Type coercion JavaScript internal conversions How the + operator works JavaScript can look simple… but its behavior can surprise even experienced developers. Frontend interviews don’t just test frameworks they test JavaScript fundamentals. #JavaScript #FrontendDevelopment #CodingInterview #WebDevelopment #Developers #Programming

JavaScript question in a frontend interview… and many developers dont know answer👀 Question: What will be the output? console.log([] + []); Take a moment and think. Most developers expect an array as output. But the actual output is: "" Yes — an empty string. Why does this happen? In JavaScript, when we use the + operator with arrays, they are converted to strings first. [] → "" So internally JavaScript does this: "" + "" = "" That’s why the result is an empty string. Now it gets more interesting: console.log([] + {}); Output: "[object Object]" Because the object converts to a string representation. Why interviewers ask this They want to check your understanding of: Type coercion JavaScript internal conversions How the + operator works JavaScript can look simple… but its behavior can surprise even experienced developers. Frontend interviews don’t just test frameworks — they test JavaScript fundamentals. #JavaScript #FrontendDevelopment #CodingInterview #WebDevelopment #Developers #Programming

𝐑𝐞𝐚𝐜𝐭 𝐮𝐬𝐞𝐄𝐟𝐟𝐞𝐜𝐭 𝐈𝐧𝐟𝐢𝐧𝐢𝐭𝐞 𝐋𝐨𝐨𝐩 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧 🚨 Many React developers face this problem… but can’t explain why it happens in interview. Question: Why does useEffect cause infinite loop sometimes? Example ❌ const [count, setCount] = useState(0); useEffect(() => { setCount(count + 1); }, [count]); What happens here? ➡ count changes ➡ useEffect runs ➡ setCount updates state ➡ state change triggers useEffect again ➡ loop continues forever This creates an infinite re-render loop. Correct way ✅ useEffect(() => { setCount(prev => prev + 1); }, []); Why this works? Because empty dependency array runs useEffect only once. Tip for React Interviews: Always check dependency array carefully. Most infinite loop bugs come from wrong dependencies. More React interview questions coming 🚀 #ReactJS #useEffect #FrontendDeveloper #JavaScript #WebDevelopment #CodingInterview #ReactInterview #NextJS #SoftwareDeveloper

🧠 JavaScript Interview Question Here’s a small but tricky one that often comes up in interviews 👇 👉 Given an array: let array = [1, 2, 3, 4, 5]; 🚨 Step 1: Add extra properties to the array array.name = "Code"; array.role = "Frontend Developer"; for (let key in array) { console.log(key, ":", array[key]); } 👉 Output: 0 : 1 1 : 2 2 : 3 3 : 4 4 : 5 name : Code role : Frontend Developer 😮 Notice how for...in also loops through custom properties! ✅ Step 2: Print only original array values using hasOwnProperty for (let key in array) { if (array.hasOwnProperty(key) && !isNaN(key)) { console.log(array[key]); } } 👉 Output: 1 2 3 4 5 #JavaScript #FrontendDeveloper #ReactJS #CodingInterview #WebDevelopment

𝗧𝗼𝗽 𝟮𝟱 𝗥𝗲𝗮𝗰𝘁 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗔𝗻𝘀𝘄𝗲𝗿𝘀 | 𝗥𝗲𝗮𝗰𝘁𝗝𝗦 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗣𝗿𝗲𝗽𝗮𝗿𝗮𝘁𝗶𝗼𝗻 In this video, we cover the most frequently asked React Interview Questions that are commonly asked in product-based and service-based companies. If you are preparing for Frontend Developer or React Developer interviews, this video will help you understand important React concepts clearly. Topics covered in this video: React Virtual DOM React Hooks (useState, useEffect) Functional vs Class Components React Lifecycle Methods React Performance Optimization Controlled vs Uncontrolled Components Props vs State React Context API React Memo, useMemo, useCallback React Rendering and Reconciliation These questions are very helpful for developers with 1–5 years of experience preparing for React interviews. #ReactJS #ReactInterviewQuestions #FrontendDeveloper #JavaScript #WebDevelopment #ReactDeveloper #CodingInterview #Programming

Stop memorizing JavaScript. Start understanding it. I see too many React developers struggle in interviews — not because they lack talent, but because they skip the foundations. So I put together a comprehensive guide covering the 11 JavaScript concepts that interviewers test the most: 𝟬𝟭. Execution Context 𝟬𝟮. Hoisting 𝟬𝟯. Scope (Block vs Function) 𝟬𝟰. Closures 𝟬𝟱. Event Loop 𝟬𝟲. Call Stack 𝟬𝟳. Promises & Async/Await 𝟬𝟴. Prototype 𝟬𝟵. The this Keyword 𝟭𝟬. Debounce & Throttle 𝟭𝟭. Shallow vs Deep Copy This isn't just theory. Every topic includes: → Clear conceptual explanations → Real code examples with comments → Common pitfalls interviewers love to test → Actual interview Q&A pairs → A one-page cheat sheet for quick revision Whether you're preparing for your next React role or levelling up as a mid-senior developer — this is the JavaScript foundation that makes everything else click. 📄 Download the free PDF below — and share it with someone who needs it. #JavaScript #ReactJS #FrontendDevelopment #WebDevelopment #InterviewPreparation #React #Chennai #HiringNow #TechJobs #CodingInterview