Understanding Promise.resolve() in JavaScript

JavaScript Interview Question: What does Promise.reject() do? Answer: Promise.reject() creates a rejected Promise. Example: 𝘗𝘳𝘰𝘮𝘪𝘴𝘦.𝘳𝘦𝘫𝘦𝘤𝘵("𝘌𝘳𝘳𝘰𝘳") Explanation: It is useful when immediately returning an error in async flows. Follow-up Interview Question: How can rejected promises be handled? Answer: Using .catch(). #javascript #promises #ErrorHandling #WebDevelopment

🚨 JavaScript Interview Question What will be the output? console.log([] + []); console.log([] + {}); console.log({} + []); At first glance it looks simple. But the results are surprising because of JavaScript type coercion and how objects convert to strings. Understanding how JavaScript converts types internally is something that appears very often in frontend interviews. Many tricky bugs also come from this behavior. What output do you think this will produce?

Interesting JavaScript interview question that really highlights how important it is to understand the core behavior of the language, not just syntax. At first glance, it looks like different objects are being used as keys, so many developers expect different values. But JavaScript converts object keys to strings internally, which leads to an unexpected result. Internally, JavaScript treats it like this a["[object Object]"] = 123 a["[object Object]"] = 456 The second assignment overwrites the first one, so when we log a[b], the output becomes 456. This reminded me that strong JavaScript fundamentals — like type coercion, object key behavior, and implicit conversions — often appear in interviews through simple-looking questions. Sometimes the trickiest interview questions are not complex algorithms, but small snippets that test your understanding of how JavaScript actually works under the hood. Definitely a good reminder to keep strengthening core concepts while preparing for technical interviews. #JavaScript #WebDevelopment #FrontendInterview #CodingInterview #MERNStack #Learning

I recently faced a JavaScript interview, and the interviewer asked a small question that confused many candidates 🧠 let a = {} let b = { key: "b" } let c = { key: "c" } a[b] = 123 a[c] = 456 console.log(a[b]) The interviewer asked: “What will be the output?” Looks simple. But it tests a deep JavaScript concept. 🧠 What they were really testing: • How JavaScript handles object keys • Type coercion in objects • Understanding of implicit string conversion Many developers assume that different objects create different keys. But JavaScript behaves differently. 🚀 Sometimes interviews are not about complex code. They are about understanding the language deeply. #JavaScript #FrontendInterview #MERNStack #WebDevelopment #CodingInterview #ProblemSolving #JavaScriptConcepts

🎯 JavaScript Interview Prep — Let’s See Where You Stand If you’re preparing for a JS interview… Don’t just read. Answer these without Googling. Let’s test real understanding 👇 🧠 𝟭. 𝗪𝗵𝗮𝘁 𝘄𝗶𝗹𝗹 𝘁𝗵𝗶𝘀 𝗹𝗼𝗴 — 𝗮𝗻𝗱 𝘄𝗵𝘆? 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨(𝘢); 𝘷𝘢𝘳 𝘢 = 10; Bonus: Would the answer change with `let`? ⚡ 𝟮. 𝗪𝗵𝗮𝘁’𝘀 𝘁𝗵𝗲 𝗼𝘂𝘁𝗽𝘂𝘁 𝗼𝗿𝗱𝗲𝗿? 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨("𝘚𝘵𝘢𝘳𝘵"); 𝘴𝘦𝘵𝘛𝘪𝘮𝘦𝘰𝘶𝘵(() => 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨("𝘛𝘪𝘮𝘦𝘰𝘶𝘵"), 0); 𝘗𝘳𝘰𝘮𝘪𝘴𝘦.𝘳𝘦𝘴𝘰𝘭𝘷𝘦().𝘵𝘩𝘦𝘯(() => 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨("𝘗𝘳𝘰𝘮𝘪𝘴𝘦")); 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨("𝘌𝘯𝘥"); If you can’t confidently explain this, revise the Event Loop. 🔥 𝟯. 𝗪𝗵𝗮𝘁’𝘀 𝘄𝗿𝗼𝗻𝗴 𝗵𝗲𝗿𝗲? 𝘧𝘰𝘳 (𝘷𝘢𝘳 𝘪 = 0; 𝘪 < 3; 𝘪++) {  𝘴𝘦𝘵𝘛𝘪𝘮𝘦𝘰𝘶𝘵(() => 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨(𝘪), 100); } Why does it print what it prints? How would you fix it? 🧩 𝟰. 𝗘𝘅𝗽𝗹𝗮𝗶𝗻 𝘁𝗵𝗶𝘀 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝘄𝗼𝗿𝗱𝘀: What’s the difference between: 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯 𝘵𝘦𝘴𝘵() {} 𝘤𝘰𝘯𝘴𝘵 𝘵𝘦𝘴𝘵 = () => {}; Not syntax. Think: `this`, hoisting, constructors. 🚀 𝟱. 𝗪𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝗵𝗲𝗿𝗲? 𝘤𝘰𝘯𝘴𝘵 𝘰𝘣𝘫 = { 𝘯𝘢𝘮𝘦: "𝘑𝘚" }; 𝘤𝘰𝘯𝘴𝘵 𝘯𝘦𝘸𝘖𝘣𝘫 = 𝘰𝘣𝘫; 𝘯𝘦𝘸𝘖𝘣𝘫.𝘯𝘢𝘮𝘦 = "𝘑𝘢𝘷𝘢𝘚𝘤𝘳𝘪𝘱𝘵"; 𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨(𝘰𝘣𝘫.𝘯𝘢𝘮𝘦); 📌 Be honest — how many did you answer confidently without guessing? Drop your answers in the comments 👇 Let’s see who actually understands JavaScript… and who just uses it. #javascript #frontend #techinterview #webdevelopment #codingchallenge #DAY72

🚀 Day 13 of My Frontend Developer Interview Preparation Today I focused on understanding the “this” keyword in JavaScript along with revising some core basics. 🔹 Learned how this behaves differently based on context: In global scope Inside objects Inside regular functions vs arrow functions In event handlers 🔹 Understood that this is not fixed — it depends on how a function is called, which makes it a very important (and sometimes tricky) concept in interviews. 🔹 Also revised key JavaScript fundamentals: Arrays & Objects Shallow vs Deep Copy Destructuring Spread & Rest Operators 💡 The more I learn, the more I realize that strong fundamentals are the real game changer for cracking interviews. Tomorrow’s plan: Practice tricky questions on these topics and strengthen my problem-solving 🚀 #JavaScript #FrontendDevelopment #WebDevelopment #CodingJourney #InterviewPreparation #LearningEveryday

Excited to share my latest blog post: 𝗦𝘁𝗿𝗶𝗻𝗴 𝗣𝗼𝗹𝘆𝗳𝗶𝗹𝗹𝘀 𝗮𝗻𝗱 𝗖𝗼𝗺𝗺𝗼𝗻 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 𝗶𝗻 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 I’ve broken down the most important string polyfills along with the frequently asked methods that keep showing up in technical interviews. Whether you’re prepping for your next round or just want to strengthen your JS fundamentals, this should help! Read it here: https://lnkd.in/gWkfu766 Hitesh Choudhary Piyush Garg Anirudh J. Akash Kadlag Chai Aur Code Jay Kadlag Nikhil Rathore Suraj Kumar Jha Would love to hear your feedback or any other interview tips you swear by! Drop them in the comments 👇 #JavaScript #WebDevelopment #CodingInterviews #Polyfills #ChaiCode #Cohort

💻 JavaScript Interview Question What will be the output of the following code? for (var i = 1; i <= 3; i++) { setTimeout(function() { console.log(i); }, 1000); } 🤔 Think before you answer! Options: A) 1 2 3 B) 3 3 3 C) 4 4 4 D) Error 💡 Bonus Question: How would you modify the code so it prints 1 2 3 instead? 👇 Comment your answer. If you are preparing for JavaScript or frontend interviews, I regularly share interview questions and also conduct mock interview sessions through devCareer mentor to help candidates gain confidence. #JavaScript #FrontendInterview #CodingInterview #CareerGrowth #MockInterview

JavaScript Interview Question: What is Promise.all()? Answer: Promise.all() runs multiple promises in parallel and resolves when all succeed. Example: 𝘗𝘳𝘰𝘮𝘪𝘴𝘦.𝘢𝘭𝘭([𝘧𝘦𝘵𝘤𝘩𝘜𝘴𝘦𝘳𝘴(), 𝘧𝘦𝘵𝘤𝘩𝘗𝘰𝘴𝘵𝘴()])  .𝘵𝘩𝘦𝘯(([𝘶𝘴𝘦𝘳𝘴, 𝘱𝘰𝘴𝘵𝘴]) => {   𝘤𝘰𝘯𝘴𝘰𝘭𝘦.𝘭𝘰𝘨(𝘶𝘴𝘦𝘳𝘴, 𝘱𝘰𝘴𝘵𝘴)  }) Explanation: If any Promise fails, Promise.all() immediately rejects. Follow-up Interview Question: When should you use Promise.all()? Answer: When multiple independent async tasks can run simultaneously. #javascript #promises #AsyncProgramming #FrontendDevelopment

𝗣𝗿𝗲𝗽𝗮𝗿𝗶𝗻𝗴 𝗙𝗼𝗿 𝗝𝗮𝘃𝗮𝘀𝗰𝗿𝗶𝗽𝘁 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 You need help preparing for your Javascript interview. You search online for sample questions. But most articles are old or require a premium subscription. There is a better way. A GitHub Repo has 450+ Javascript interview questions. These questions are updated by real devs who have attended interviews. They add new questions all the time. You can use this resource to prepare for your interview. It is free and updated frequently. Source: https://lnkd.in/gNdxfdy2