diff --git a/app/api/seed-experiences/route.ts b/app/api/seed-experiences/route.ts index 4258a1f..9857159 100644 --- a/app/api/seed-experiences/route.ts +++ b/app/api/seed-experiences/route.ts @@ -3,15 +3,13 @@ import { createClient } from '@supabase/supabase-js'; import seedData from '@/data/seed-experiences.json'; /** - * One-time seed endpoint to insert 29 fully complete interview experiences. - * Each entry has title, author, tags, summary, AND formatted_content (full article body). + * One-time seed endpoint — 50 complete interview experiences with full content. + * Each entry has: title, author, tags, summary, formatted_content (full HTML article body). * - * Requires CRON_SECRET auth and SUPABASE_SERVICE_ROLE_KEY. - * - * Usage: POST /api/seed-experiences + * POST /api/seed-experiences * Header: Authorization: Bearer * - * After running successfully, delete this route + data/seed-experiences.json. + * After seeding, delete this route + data/seed-experiences.json. */ export async function POST(request: Request) { const authHeader = request.headers.get('authorization'); diff --git a/data/seed-experiences.json b/data/seed-experiences.json index 44800e6..6efc264 100644 --- a/data/seed-experiences.json +++ b/data/seed-experiences.json @@ -463,5 +463,291 @@ "slug": "5-my-frontend-developer-interview-experience-at-redisolve-technologies-23062025", "status": "approved", "formatted_content": "

Hi Friends!!

\n\n
\n

On 23rd June 2025, I attended an interview for the position of Frontend Developer at Redisolve Technologies. It was a good learning experience where I was asked important frontend concepts.

\n\n

In this blog, I am going to explain all the questions asked in detail with simple words and real examples, so even beginners can understand and learn easily. Let's dive in!

\n
\n\n

1.How to Optimize Webpage for Performance?

\n\n

A website must load fast and smoothly for a good user experience.
\nTo optimize performance, we can compress images (like WebP), minify JS/CSS/HTML, and use lazy loading for images and videos. We can also use a CDN to serve content faster and enable browser caching.

\n\n

Example: Lazy Loading Image
\n

\n\n
\n
<img src=\"image.webp\" loading=\"lazy\" alt=\"Sample Image\">\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

2.How to Handle CORS in JavaScript?

\n\n

CORS (Cross-Origin Resource Sharing) is a browser rule that blocks access to resources from a different origin (domain) unless the server allows it. If the server allows it, it sends this header:
\n

\n\n
\n
Access-Control-Allow-Origin:\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

Example Using fetch:
\n

\n\n
\n
fetch('https://api.example.com/data', { mode: 'cors' })\n  .then(res => res.json())\n  .then(data => console.log(data));\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

3.What is Closure? How does it Work?

\n\n

A closure means an inner function can access variables from the outer function even after the outer function has finished running.
\nClosures are useful to create private variables or remember previous data.

\n\n

Example:
\n

\n\n
\n
function outer() {\n  let count = 0;\n  return function inner() {\n    count++;\n    console.log(count);\n  };\n}\nconst counter = outer();\ncounter(); // 1\ncounter(); // 2\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

4.Client Side Rendering vs Server Side Rendering

\n\n

-Client Side Rendering (CSR): JS builds the page in the browser.
\n-Server Side Rendering (SSR): Page built on server, ready HTML sent to browser.

\n\n

Example:
\n

\n\n
\n
CSR \u2013 React App using Vite.\nSSR \u2013 Next.js App that sends ready HTML.\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

5.How to Manage Version and Collaborate in Git?

\n\n

Git allows teams to work on the same project using branches.
\nDevelopers create branches, commit changes, then merge to main branch.

\n\n

Example:
\n

\n\n
\n
git checkout -b feature-login\ngit add .\ngit commit -m \"Added login feature\"\ngit push origin feature-login\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

6.Explain NPM and Yarn

\n\n

Both are package managers for JavaScript projects.
\nnpm is default with Node.js, while Yarn was made for speed and security.
\nYou can install libraries, update or remove them easily.

\n\n

Example:
\n

\n\n
\n
npm install react\nyarn add react\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

7.How to Debug Frontend Applications?

\n\n

Debugging finds and fixes errors.
\nYou can use console.log(), browser DevTools (Elements, Network, Sources), and breakpoints to check code flow.

\n\n

Example:
\n

\n\n
\n
console.log(\"Debugging here\");\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

8.Synchronous vs Asynchronous in JS

\n\n

Synchronous: Code runs line by line, blocking the next line.
\nAsynchronous: Runs in background (API calls, setTimeout).

\n\n

Example:
\n

\n\n
\n
console.log(\"Start\");\nsetTimeout(() => console.log(\"Async\"), 1000);\nconsole.log(\"End\");\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

9.How Does Event Loop Work in JavaScript?

\n\n

The event loop lets JS handle async operations like setTimeout, promises.
\nSynchronous code runs first; then event loop runs callbacks from queue.

\n\n

Example:
\n

\n\n
\n
console.log('1');\nsetTimeout(() => console.log('2'), 0);\nconsole.log('3');\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

10.Explain CSS Positions: relative, absolute, fixed

\n\n

CSS positions decide how an element is placed in a page.

\n\n

-relative: Moves based on its original place.
\n-absolute: Moves based on the nearest ancestor with position set.
\n-fixed: Stays fixed to the window even during scroll.

\n\n

Example:
\n

\n\n
\n
.relative { position: relative; top: 10px; }\n.absolute { position: absolute; top: 10px; left: 10px; }\n.fixed { position: fixed; bottom: 0; right: 0; }\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

11.What is Media Query?

\n\n

Media queries make your website responsive \u2014 looking good on all devices (mobiles, tablets, desktops).
\nIt changes styles based on screen width or height.

\n\n

Example:
\n

\n\n
\n
@media (max-width: 600px) {\n  body { background: lightblue; }\n}\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

12.What is SPA?

\n\n

SPA (Single Page Application) loads one HTML file and updates content using JavaScript without refreshing the entire page.
\nReact, Angular, Vue are frameworks for SPA.

\n\n

Example: Gmail, Facebook \u2014 no page reloads when you switch tabs or open mails.

\n\n

13.Build Tools: Webpack and Vite

\n\n

Build tools bundle JS, CSS into fewer files to load faster.
\nWebpack is older, heavy but powerful; Vite is faster with modern features.

\n\n

Vite Example:
\n

\n\n
\n
npm create vite@latest\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

14.Difference Between Development and Production

\n\n

Development: Unminified code, full error logs, easy debugging.

\n\n

Production: Minified, optimized, fast loading, errors hidden from users.

\n\n

Example:
\n

\n\n
\n
npm run dev   # Development Mode\nnpm run build # Production Mode\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

15.Difference Between ID and Class in HTML.

\n\n

-ID: Unique, used once (#id).
\n-Class: Can be reused for multiple elements (.class).Example:

\n\n

Example:
\n

\n\n
\n
<div id=\"header\"></div>\n<div class=\"box\"></div>\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

16.How to Use Box Model in CSS?

\n\n

The box model shows how content, padding, border, and margin create space around elements.
\nAdjusting padding/margin controls spacing and layout.

\n\n

Example:
\n

\n\n
\n
div {\n  padding: 10px;\n  border: 1px solid black;\n  margin: 20px;\n}\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

17.Difference: Arrow Function vs Traditional Function

\n\n

Arrow functions are short and do not have their own this.
\nTraditional functions have their own this and can be hoisted.

\n\n

Example:
\n

\n\n
\n
const greet = () => console.log(\"Hello\");\nfunction greetOld() { console.log(\"Hello\"); }\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

18.Explain em, rem, px in CSS

\n\n

-px: Fixed size.
\n-em: Relative to parent element\u2019s font size.
\n-rem: Relative to root (html) font size.

\n\n

Example:
\n

\n\n
\n
html { font-size: 16px; }\np { font-size: 2rem; } /* 32px */\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

19.What are Template Literals?

\n\n

Template literals help write multi-line strings and use variables easily.
\nUse backticks () and ${} to embed expressions.

\n\n

Example:
\n

\n\n
\n
const name = \"Sathish\";\nconsole.log(`Welcome, ${name}!`);\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

20.var, let, const in JavaScript

\n\n

var: Function-scoped, can redeclare.

\n\n

let/const: Block-scoped; const can\u2019t be reassigned.

\n\n

Example:
\n

\n\n
\n
var x = 5; let y = 10; const z = 15;\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

[(https://redisolve.com/)]

\n\n

The End!!

\n\n

This interview helped me revise important frontend concepts like closures, event loop, git, CSS box model, and build tools. These are must-know topics for every frontend developer. I suggest every learner practice these deeply with examples to build strong confidence.

\n\n

Learning never exhausts the mind. Every interview is a new lesson!!.

\n\n" + }, + { + "title": "Amazon SDE I (6 months) 2026 Interview Experience (Off Campus)", + "original_url": "https://dev.to/saloni_jain_aba5e8c508f8a/amazon-sde-i-6-months-2026-interview-experience-off-campus-4ago", + "source": "dev.to", + "author": "Saloni Jain", + "published_at": "2026-05-30T13:09:01Z", + "tags": [ + "amazon", + "interview", + "softwaredevelopment", + "amazoninterviewexperience" + ], + "summary": "This is a breakdown of my interview experience for the Amazon SDE I Intern (July\u2013Dec 2026) role. The...", + "formatted_content": "

This is a breakdown of my interview experience for the Amazon SDE I Intern (July\u2013Dec 2026) role. The process spanned a few months and tested both my technical depth and patience.

\n\n

\n \n \n HIRING INTEREST FORM 1 (Feb 19, 2026)\n

\n\n

I received a Hiring Interest Form from Amazon University Talent Acquisition.

\n\n

\n \n \n HIRING INTEREST FORM 2 (Feb 26, 2026)\n

\n\n

A few days later, I received another Hiring Interest Form from Amazon University Talent Acquisition.

\n\n

\"Screenshot

\n\n

\n \n \n ONLINE ASSESSMENT (April 6, 2026)\n

\n\n

The OA consisted of:

\n\n\n\n

\n \n \n THE INTERVIEWS\n

\n\n

This is where the most stressful part began \u2014 the scheduling maze.

\n\n

\"Screenshot

\n\n\n\n

My first interview took place successfully on April 22. However, the other round underwent another reschedule and was eventually shifted to May 4.

\n\n

\"Screenshot

\n\n

\n \n \n Interview 1 (April 22, 2026)\n

\n\n

A standard 1-hour session on Amazon\u2019s live code platform.

\n\n\n\n

\n \n \n Interview 2 (May 4, 2026)\n

\n\n

A significantly more intense 1-hour session.

\n\n\n\n

\"Screenshot

\n\n

\n \n \n THE OUTCOME\n

\n\n

A week after my final round, I received an update that I was not selected for the internship. Regardless of the final outcome, the preparation and experience gained through this process will carry forward.

\n\n

\n \n \n KEY TAKEAWAYS\n

\n\n\n\n

Feel free to connect with me on LinkedIn.

\n\n", + "slug": "amazon-sde-i-6-months-2026-interview-experience-off-campus", + "status": "approved" + }, + { + "title": "Fullstack (Nodejs + Reactjs) interview experience at Nutanix", + "original_url": "https://dev.to/learnersbucket/fullstack-nodejs-reactjs-interview-experience-at-nutanix-403i", + "source": "dev.to", + "author": "Prashant Yadav", + "published_at": "2021-08-10T05:50:40Z", + "tags": [ + "beginners", + "javascript", + "webdev", + "react" + ], + "summary": "Fullstack interview experience at Nutanix", + "formatted_content": "

\"Fullstack

\n\n
\n

Visit learnersbucket.com If you are preparing for your JavaScript interview. You will find DSA, System Design and JavaScript Questions.

\n
\n\n

I had applied for the MTS-3 Fullstack \u2013 SAAS (Nodejs + Reactjs) on Nutanix\u2019s career section and got the shortlisting email on 21\u2019st April 2021. It was for the Bangalore location.

\n\n

\"Shortlisting

\n\n

After the email, the recruiter called me and we had brief introduction about myself, my experience, etc and what are they looking for in the candidate and about the Nutanix and role.

\n\n

\n \n \n 1st Round: Phone screen (SDE2 \u2013 Full Stack)\n

\n\n

I was asked what I do on a daily basis, followed by some JavaScript questions and some Rest API questions.

\n\n

It went well.

\n\n

\n \n \n 2nd Round: JavaScript Platform & DSA. (SDE3 \u2013 Full Stack)\n

\n\n

Don\u2019t remember about the interviewer.

\n\n

In this round I was asked to implement programs based on Closure, Promise and Objects.

\n\n\n\n

This was a good round, and I learned lots of things. Went good.

\n\n

\n \n \n 3rd Round: System Design (Frontend + Backend) (Team lead \u2013 Full Stack)\n

\n\n

The interviewer had around 9 years of experience and was leading the team which I was being hired for, we exchanged introductions and started the interview.

\n\n

As I was being hired for the Payment & Pricing team.

\n\n

This round was mainly focused towards creating dynamic form and handling the payment and pricing based on the features selected.

\n\n

Security, CORs, XSS.

\n\n

How to secure your API, Server side vs Client Side, which to use for security purposes?. What if the same has to be achieved on the alternate side & vice versa.

\n\n

Lots of discussion of form handling and uncontrolled and controlled form components. Select box, etc.

\n\n

I haven\u2019t read about security still it went well.

\n\n

\n \n \n 4th round: System Design (Javascript) (Manager \u2013 Pricing & Payment Team)\n

\n\n

The interviewer was quite nice, he first introduced himself and what they are looking for in a candidate who will join this team, what type of work will be there, etc.

\n\n

I was asked to implement a Number increment counter in JS.

\n\n

In this round, I came up with a solution using setTimeout and setInterval, even though it was not perfect he pushed me to the next round.

\n\n

\n \n \n 5th round: DSA (VP \u2013 Pricing & Payment Team)\n

\n\n

The interviewer was from San Jose and he was a little strange.

\n\n

He asked me to introduce myself and when I was done, after a pause he unmuted and asked that\u2019s it?. Please elaborate a little. I thought he was doing something else simultaneously and not concentrating towards the interview.

\n\n

Later he asked me to implement an algorithm to count all possible subarrays in an array with sum k. (Note:- They are not consecutive).

\n\n

As I had to find all the possible sub arrays, I thought of using Dynamic Programming first.

\n\n

But the interviewer asked me to implement an O(N ^ 2) algorithm.

\n\n

Failed in this. He showed me the solution using the bitwise operator.

\n\n

At the end he was constantly asking me from where I come?, where I am living. In Spite of repeatedly telling him that I live in Mumbai and having been born and brought up here. He was not ready to accept it. I was getting a feeling that he has some personal issue with name.

\n\n

\n \n \n Verdict.\n

\n\n

NOT SELECTED.

\n\n

I guess because my 4th round went okay and 5th round went bad they dropped me. Interviewer asked me to apply in different verticals, but I lost my interest and so I left it.

\n\n", + "slug": "fullstack-nodejs-reactjs-interview-experience-at-nutanix", + "status": "approved" + }, + { + "title": "My first SDE internship interview experience", + "original_url": "https://dev.to/vedantjain03/my-first-sde-internship-interview-experience-1k8e", + "source": "dev.to", + "author": "vedant-jain03", + "published_at": "2022-01-08T16:00:57Z", + "tags": "dsa, ", + "summary": "Company: Lido Learning I applied at Lido Learning via linkedin. I don't remember the exact date...", + "formatted_content": "
\n

Company: Lido Learning

\n
\n\n

I applied at Lido Learning via linkedin. I don't remember the exact date when I applied. But my overall experience was awesome though got rejected due to rolling criteria.

\n\n

The process contain 3 round:

\n\n

\n \n \n First Round (Telephonic Round)\n

\n\n

HR called me and told me that my resume is shortlisted for this role and they want to interview me. I was glad as this was my first time I am going to give interview for SDE role with good stipend and they were also providing me PPO (Pre Placement Offer) if satisfied with my work.
\nHR told me that my first technical interview will be after 5 days and I can expect easy-medium DSA questions and some questions related to Javascript, OOPS.

\n\n

I revise my concept, I do leetcode.

\n\n

\n \n \n Second Round (Technical Round)\n

\n\n

Interviewer was SDE-2 at Lido. He first asked me to introduce myself. Then he ask me question related to javascript. I was able to give answer but I was not confident about it. He asked me the difference between '==' and '==='. I told him that both are conditional operator and '===' is advancement of '==', it was not fully correct. Then he asked me what is reduce function, I told him it is used in array scope. He was satisfied but not fully. He started asking me about OOPS, he asked me difference between private, protected, public.
\nThen he request me to share the screen and ask me 2 DSA question.

\n\n
    \n

  1. Next Greater Element
    \nI started with brute force and show it to him. He asked me to optimize it, I did it using stack data structure.

    2. \n

  2. Based on hash map.
    \nI started with brute force and he asked me to optimize it, I did it and he was satisfied.

    3. \n
\n\n
\n

After 2 days I got call that I am selected for next round.

\n
\n\n

\n \n \n Third Interview(Technical Round)\n

\n\n

Interviewer was VPE at Lido. He started with my introduction, I prepared for DP, graphs and other higher concepts but he deep dive into hashmap, he not ask my to code, he just give me different conditions for mapping. It was pretty tough.

\n\n

As it was my first experience, I learned so many things and gain knowledge. Unfortunately, I was not selected as per rolling basis. But it was nice experience and I hope it helps you as well.

\n\n

All the Best!!!

\n\n", + "slug": "my-first-sde-internship-interview-experience", + "status": "approved" + }, + { + "title": "My Amazon SDE Interview Experience \u2013 May 2024", + "original_url": "https://dev.to/naweli_verma/my-amazon-sde-interview-experience-may-2024-3nf6", + "source": "dev.to", + "author": "Naweli Verma", + "published_at": "2024-09-17T08:59:19Z", + "tags": "inter", + "summary": "My Amazon SDE Interview Experience \u2013 May 2024 In May 2024, I had the opportunity to...", + "formatted_content": "

\n \n \n My Amazon SDE Interview Experience \u2013 May 2024\n

\n\n

In May 2024, I had the opportunity to interview for a Software Development Engineer (SDE) role at Amazon. It all started when a recruiter reached out to me via LinkedIn. I was pleasantly surprised, as it\u2019s always exciting.

\n\n

\n \n \n How It All Started\n

\n\n

The recruiter was professional and clear, giving me all the necessary details about the process and the role. After exchanging a few messages, I received a test link for the first round of the interview, which was a coding assessment. The assessment was hosted on HackerRank and comprised two coding questions.

\n\n

\n \n \n First Round - The Coding Test\n

\n\n

The questions were straightforward but slightly lengthy. Here's a breakdown:

\n\n

1. First Question: Barcode Generation
\nThe task was to generate a barcode based on some predefined parameters. While the question wasn't inherently complex, it required attention to detail to ensure all conditions were met. I approached this problem methodically, breaking it down into smaller parts and implementing a solution in JavaScript. The focus was on efficiency and clarity, ensuring that the generated barcode met the expected format and constraints.

\n\n

2. Second Question: Array Processing with Deployment Status

\n\n

This was more of a data manipulation task. The input consisted of objects, each with a deployment ID and a deployment status. My goal was to return an array based on these inputs. While the problem seemed simple, it came with its share of edge cases. For instance, some objects were missing keys, which wasn\u2019t apparent at first glance. However, after submitting my initial solution, I realized that such edge cases needed to be accounted for. I quickly revised my code to handle these scenarios, ensuring that the missing keys wouldn\u2019t lead to errors or incomplete results.

\n\n

\"Cat
\nI solved both questions using JavaScript and was confident that my solutions passed all the test cases, including the hidden ones.

\n\n
\n

Amazon tends to move candidates forward in the process if they solve all the coding questions with all test cases passing.

\n
\n\n

After that got a call from recruiter saying that he is moving forward with the interview process, and it is going to be an onsite interview. I had 5 days to prepare.

\n\n
\n

I have been working remotely from past 3 years and never been to office, so I was scared more because of office rather than the interview rounds \ud83d\ude43\ud83d\ude02

\n
\n\n

\n \n \n Further Interview Rounds\n

\n\n

I went to the amazon office, few candidates were already there. We all went for interviews. I had 3 technical rounds of interview that day.

\n\n

\n \n \n 1. Troubleshooting Round\n

\n\n

The first round was a troubleshooting-focused interview. As soon as I walked into the room, I was greeted by an interviewer who was incredibly supportive. He kept smiling throughout the session, which helped ease my nervousness.

\n\n

He handed me a sheet of paper and presented several questions related to system failures, networking, and network layers. The approach he used was particularly interesting. He asked me to think about basic solutions first\u2014essentially encouraging me to solve the problem from the ground up. Once I provided an answer, he changed the scenario slightly, adding more complexity with each step.

\n\n

For example, after discussing a network failure, he shifted the conversation to deeper layers of the network and asked what I would do if standard solutions didn\u2019t work. This pushed me to think creatively and consider various failure points in a system, from the most common to more intricate issues.

\n\n
\n

Interview asked me to wait outside, after that one recruiter came and said that I will be going for second round.

\n
\n\n

\n \n \n 2. DSA Round\n

\n\n

The next round was a deep dive into data structures and algorithms (DSA). This time, my interviewer was a senior SDE at Amazon. She greeted me with a sheet of paper and presented a fairly large and complex question. As I read through it, I quickly realized that the main objective was to find the shortest path in a graph. This type of problem is common in interviews but can get tricky when edge cases are involved, which she was sure to include.

\n\n

I asked a few clarifying questions to fully understand the problem and its various scenarios. Once I felt confident, I began to work on a solution\u2014writing pseudocode directly on the paper. As I explained my approach and logic, she continuously probed deeper, asking why I made certain decisions and how I was handling different parts of the graph. I walked her through my thought process, discussing the trade-offs and optimizations. Fortunately, I was able to solve the question completely and correctly.

\n\n

Once she was satisfied with my graph solution, she asked me about the time and space complexity, which I analyzed and explained to her. Feeling a sense of accomplishment, I thought the round was going well.

\n\n

However, she soon moved on to another, more challenging question\u2014this time involving dynamic programming (DP). The problem involved a matrix in which different crops needed to be planted in a way that followed certain rules. This was a more complex question, and I took my time to fully understand it. I asked several questions to ensure I covered all the constraints and edge cases.

\n\n

I wrote a pseudocode solution, but it wasn\u2019t fully optimized. She gave me some test cases, and while my code ran successfully on about 80% of them, there were still edge cases that failed. I was getting nervous at this point, and she noticed that. Fortunately, she offered a helpful hint, and I tried to optimize my solution further. Despite my best efforts, I couldn't completely nail the solution, likely due to my nerves taking over.

\n\n
\n

I waited outside again, I was not very happy and confident about with this round, but the recruiter again came said that my next round is System design. I got so happy!

\n
\n\n

\n \n \n 3. System Design Round\n

\n\n

The final round of the day was the System Design interview, and this was by far the most intense and draining session. The interviewer was part of Amazon\u2019s architecture team, and right from the start, I could tell that this round would be challenging. We began with a discussion about my resume, focusing on my past projects and the design decisions I had made in previous work. He asked several questions about the architecture of the systems I had worked on, probing into the details of my design choices and the trade-offs I made.

\n\n

After this initial discussion, he asked me to design a system for an ed-tech platform, with a specific focus on the video streaming feature. The goal was to design a system where teachers could stream live video sessions, and students could attend those sessions online.

\n\n

We began with the high-level architecture, discussing the main components such as video servers, databases, and APIs. I explained my approach to handling the large number of users and ensuring a smooth video streaming experience. He continuously asked about scalability, reliability, and latency issues, which are crucial for a platform with live video.

\n\n

Once we had covered the high-level design, he shifted the conversation to the low-level details. This is where the discussion became more technical. We explored various approaches for optimizing the system, handling edge cases, and ensuring a seamless experience for users even in worst-case scenarios. I had to think on my feet, offering solutions and alternatives for different problems, including handling spikes in user traffic and ensuring minimal downtime.

\n\n

The interviewer kept presenting different scenarios\u2014what if a video server goes down? How would you handle network congestion? How do you ensure low latency for students in different geographical regions? Each scenario required a detailed answer, and I found myself fully immersed in discussing possibilities and design patterns.

\n\n

The entire interview lasted about 1.5 hours, and by the end of it, I was exhausted. It was mentally draining but also one of the most insightful interviews I\u2019ve ever had. We explored various architectural challenges, and it felt more like a collaborative problem-solving session than a traditional interview.

\n\n
\n

So I went to amazon office at 9 AM in the morning and came out at 5 PM in the evening, I had all my rounds completed and the recruiter said that he is moving forward with the managerial round, which is not scheduled yet.

\n
\n\n

\"Office

\n\n

\n \n \n Anyways forgot to tell you one thing, Please understand all the amazon's principle before going for the interview, they will ask at-least 2 question around it in every round. So please prepare that as well\n

\n\n", + "slug": "my-amazon-sde-interview-experience-may-2024", + "status": "approved" + }, + { + "title": "Tata 1mg SDE1 - Frontend Engineer Interview Experience", + "original_url": "https://dev.to/heysujal/tata-1mg-sde1-frontend-engineer-interview-experience-21nh", + "source": "dev.to", + "author": "Sujal Gupta", + "published_at": "2025-03-24T03:23:08Z", + "tags": "inter", + "summary": "Hi, in this post I am sharing my interview experience for the role of SDE-1 Frontend Engineer at Tata...", + "formatted_content": "

Hi, in this post I am sharing my interview experience for the role of SDE-1 Frontend Engineer at Tata 1mg. This interview happened a while back in May 2024 and this blog was still in my draft. So, I finally decided to share my experience by completing this blog.

\n\n

This is my first time writing a detailed blog post. I tried to cut out too many details and keep the relevant parts. Please share your feedback in comments.

\n\n

So let's start,
\nAs for the application process, I applied to the job through their career portal without any referral.

\n\n
\n

Tip : It is more sensible to apply at the job as soon as possible directly instead of waiting for a referal. It often happens that by the time you hear from the other person for referal, the job post has already expired.

\n
\n\n

I got a call from the HR one week after I applied and she scheduled my first round of interview. My first interview round was scheduled for two days later. I was told that the first interview round will happen about Data Structure and Algorithms.

\n\n

Since I was already preparing for interview and practicing Leetcode, I was confident in that part.

\n\n

\n \n \n First Round\n

\n\n

: This started with a brief introduction from both ends.
\nThe first question was to implement a function to check if a string is palindrome.

\n\n

While, this was not a hard question or involved any usage of complex data structures, I asked the interviewer if I could implement the same in C++ as I am much faster in writing C++ code as compared to JavaScript, since I was solving LeetCode problem in C++ for a very long time.
\nThe interviewer suggested that the this is a frontend interview so I should be using JavaScript instead.

\n\n
\n

Tip: Practicing basic DSA Questions in JavaScript might help you in some cases as some interviewers expect you to code in only JavaScript. Remembering how to use common data structure like map and set would help.

\n
\n\n

Okay, now back to the questions.
\nI then started to implement it in JavaScript.

\n\n

Q. The first problem was to implement a function to check if a given string is palindrome. Even though I knew how to solve it by heart. A silly mistake in the code outside the function cause some error which took us(yes the interviewer too) a while to find out. I found the error and fixed it and it worked.

\n\n

Then we started discussing some basic JavaScript questions

\n\n

Q. Difference between let and const.
\nAns. I told him the basic difference and he was satisfied.

\n\n

Q. What are primitives and non-primitive types in JavaScript?
\nAns. I didn't know about the term back then, but the answer was to mention all the basic types like boolean, number, undefined, null etc. For more Read here.

\n\n

Q. Why mutating const is allowed but not reassignment.
\nAns: I wasn't sure about the answer and explained through code examples that reassignment is not allowed but I couldn't explain why this happens.
\nThe interviewer told me that the answer was somewhat related to previous question about primitives.

\n\n

To learn more about this you can refer this excellent interactive blog by @joshwcomeau The \u201cconst\u201d Deception

\n\n

Q. What is hoisting in JavaScript?
\nAns. Preety straight forward. I told him the answer and then we moved to next question.

\n\n

Q. What is TypeScript and its features?
\nAns. I told him about interfaces and types, and other basic features like being able to catch error before hand which could only be identified when you run code in case of plain JavaScript. He was satisfied with the answer.

\n\n

\n \n \n Second Round\n

\n\n

Q. Implement Debouncing
\nAns. I have only heard about debouncing back then and had some idea in mind. So, using that idea I started writing some code. I started writing thing based on my rough understanding of debouncing. I wrote a loop which would run for a long time to showcase a heavy/long operation which we then would need to somehow cancel when a certain event keeps firing within a certain delay.

\n\n

The interviewer saw my intuition and pointed that he understood what I am trying to achieve but I was missing some key logic.

\n\n

Q. A slight variation of 2-sum problem on Leetcode.
\nArr = [1, 5, 2, 6, 8, 9, 10], target = 7
\nO/P: [1, 6], [5, 2], [2, 5], [6, 1]

\n\n

Ans. I was able to implement it correctly.

\n\n

Q. Polyfill of Promise.all
\nAns. I was unaware of this, so couldn't implment it.

\n\n

Q. What is prototypal inheritance?
\nAns. I answered it correctly and we moved on to the next question.

\n\n

Q. How does useMemo works under the hood?
\nAns. I told the interviewer that useMemo does memoization by saving the calculation in some data structure so we can use it directly when needed without doing the calculation again. But the interviewer was expecting some indepth answer which I was not aware of at that time.

\n\n

Overall, my second round went bad and I got a rejection mail after a few days.

\n\n

\n \n \n Learnings\n

\n\n

I have now understood that it is now very common and bare minimum for frontend developers to learn some optimization techniques and also practice about commonly asked interview questions. DSA questions asked to frontend devs is usually easy.

\n\n

I suggest using Akshay Saini's playlist for preparing for frontend interviews.

\n\n

After this interview, I learned many optimization techniques and commonly asked interview questions and formed a good understanding of them. I also apply whatever I learned from those material. I made me a better developer overall.

\n\n", + "slug": "tata-1mg-sde1-frontend-engineer-interview-experience", + "status": "approved" + }, + { + "title": "My TikTok (ByteDance) Frontend Software Engineer Interview Experience", + "original_url": "https://dev.to/alaster/my-tiktok-bytedance-frontend-software-engineer-interview-experience-dbn", + "source": "dev.to", + "author": "Alaster", + "published_at": "2023-01-25T14:10:22Z", + "tags": "webde", + "summary": "The post was originally published on ExplainThis with title \u300aMy TikTok (ByteDance) Frontend Software...", + "formatted_content": "
\n

The post was originally published on ExplainThis with title \u300aMy TikTok (ByteDance) Frontend Software Engineer Interview Experience\u300b

\n
\n\n

This is a blog post on my interview experience with TikTok in summer 2022. The role I interviewed for was Frontend Software Engineer.

\n\n

I applied this frontend software engineer position through TikTok's career website, but somehow I was contacted by a ByteDance recruiter. It's because ByteDance is TikTok's parent company. It's kinda like applying Facebook but get contacted by Meta a recruiter. I must say ByteDance's efficiency was very impressive. I submitted my resume in the morning and received an interview invitation in the afternoon in the same day.

\n\n

After each round of interview, I was arranged the next round within an hour. It took only two weeks from application to finishing all interviews. ByteDance is already a company with more than 100K employees, and it's very impressive that they still maintain this kind of efficiency and speed. Because ByteDance did not specifically sign a confidentiality clause for the interview part, and most people directly share the questions they did on the Internet, I will also directly share the questions I was asked.

\n\n\n
\n\n

\n \n \n First Round\n

\n\n

The interviewer was a senior frontend engineer. The interviewer asked me to do a self-introduction first. Then he started asking questions about past projects I put on the resume, and he followed up with \"what is the most challenging project you have done\".

\n\n

After the resume question, he asked questions related to frontend. The questions included

\n\n\n\n

After the React questions, he asked basic networking questions, mainly for HTTP

\n\n\n\n

After network questions, he asked me JavaScript questions.

\n\n\n\n

\n \n \n Second Round\n

\n\n

The interviewer was a senior frontend engineer. After self-introduction, he asked questions on my resume, and asked me about my experience in writing unit tests and E2E tests in the past. Then he asked a few JavaScript questions, including

\n\n\n\n

This round ended with a whiteboard question, which was a LeetCode Medium string question.

\n\n

\n \n \n Third Round\n

\n\n

This interview is not the same as the previous two rounds. There was no self-introduction. The interviewer asked a LeetCode Medium question in the very beginning, which is basically a variation of 3Sum. After that, he asked me a few frontend questions

\n\n\n\n

Finally, there is a front-end system design question. It took about 20 minutes to discuss how to design a Typeahead front-end.

\n\n

After the three technical interviews, I feel that they pretty much covered everything from JavaScript, React, Networking, algorithm and system design. So if you want to prepare for the TikTok frontend interview, you need to prepare a lot!

\n\n

\n \n \n Fourth Round (Human Resources)\n

\n\n

After successfully passing the three rounds of technical interviews, I finally entered the HR round. The HR first introduced the culture of ByteDance and what the team I interviewed was doing. Many people shared on the internet that you should not take this round lightly, and you must prepare well for various behavioral interview questions. The question asked by HR was mainly to see your fit with the company culture, so it will be helpful to read the company culture in advance.

\n\n

I received the offer one week after the HR round.

\n\n", + "slug": "my-tiktok-bytedance-frontend-software-engineer-interview-experience", + "status": "approved" + }, + { + "title": "Unacademy Software Engineer interview experience, Web", + "original_url": "https://dev.to/kushagra_mehta/unacademy-software-engineer-interview-experience-web-14d4", + "source": "dev.to", + "author": "Kushagra Mehta", + "published_at": "2021-08-07T15:33:19Z", + "tags": "webde", + "summary": "Hello everyone, I'm Kushagra Mehta, a final year student from Jaipur. I have joined Unacademy as a...", + "formatted_content": "

Hello everyone,
\nI'm Kushagra Mehta, a final year student from Jaipur. I have joined Unacademy as a Software Engineer. In today's blog, I'll be sharing my interview experience at Unacademy for a Software Engineer position.
\n\"Unacademy-logo\"

\n\n
\n

Big shoutout to Rajat Gupta who, wrote a great Interview experience article that helps me along the way. Link\ud83d\udd17

\n
\n\n

\n \n \n How it started?\n

\n\n

Hmm, This is an interesting one. From my side, I did some cold-DM's in mid of Jun-21 asking for interviews(Great videos on it).

\n\n

Then on the sweet morning of 13-Jul, I got a call from HR team of Unacademy asking that, Was I available for an interview or not. From here, my journey started, So the call goes like this

\n\n\n\n

The recruiter explained everything related to the next rounds over the call and scheduled the first round.

\n\n
\n

I asked my recruiter where he got my profile from, he said he liked my LinkedIn & Github profile and that's why he reached out to me. So boys and girls it's time to improve your online profiles.

\n
\n\n

\n \n \n Interview rounds\u2728\n

\n\n
    \n
  1. JS Fundamentals (~ 1 hr)
    2. \n
  2. Frontend with React (~ 1 hr)
    3. \n
  3. Senior Engineering Manager (~ 30 m)
    4. \n
  4. Culture ( ~ 30 m)
    5. \n
\n\n

Platform: Google Meet

\n\n

Coding Environment: CodeSandbox

\n\n

Let's dive into each round in detail.

\n\n

\n \n \n \ud83d\udc68\ud83c\udffb\u200d\ud83d\udcbb JS Fundamentals\n

\n\n

It started with a simple intro. Then we quickly jumped into the realm of JS. The questions revolved around basics concepts of Javascript like:- this, let/var/const, Promises

\n\n

The interview was more around discussion-based, Why or How something is happening. We started with output-based questions, where we discussed What, Why & How things are happening.

\n\n

He told me to implement Promises after that, we discussed my approach.

\n\n

At last, we discussed eventHandling, debouncing & throttling. After that, I was asked to build debouncing function and implement a use-case for it(build Search bar).

\n\n

How to prepare:\ud83d\udc9bjavascript.info, Akshay Saini - FE Interview Ques

\n\n
\n

Everything was chill, he helped me in every step of the interview. Even when I did something wrong with .addEventListener he explained why things are not working and helped me with the process\ud83e\udd2f

\n
\n\n

\n \n \n \u269b\ufe0fFrontend with React\n

\n\n

This happened the day after the first round. We started with building a Google timer clone. I was asked to explain the approach I took.

\n\n

After that, We discussed some basic concepts of JavaScript
\nclosures, setTimeout, this, async/await, promises, async/defer, event loop... Then we jumped into some basic CSS questions like inline/inline-block, Box model, etc.

\n\n

Then we jumped into the territory of ReactJs. The questions ranged from what is React, State/Props, Lifecycle methods, Lifecycle in Class components vs Functional components, Virtual DOM.

\n\n

At last, I was given a basic problem to solve Sort an array of 0s, 1s and 2s

\n\n

How to prepare: Front End Interview Handbook\u2728, List of top 500 ReactJS Interview Ques\ud83d\ude35

\n\n
\n

This round was also super chill. I stuttering a lot in explaining things. Even I got confused in some question, but interviewer helped me understand them\ud83e\udd2f.

\n
\n\n

\n \n \n \ud83d\udc68\ud83c\udffb\u200d\ud83d\udcbcSenior Engineering Manager\n

\n\n

It was more of a discussion on my decisions over tech-stack, team dynamics, and culture fit. It started with technical questions on Why I choose ReactJs, what I did in my previous internship, What I learned from there, and What I did not like there.

\n\n

Then he asked me some behavioral questions like:

\n\n
    \n
  1. How will you suggest someone to opt ReactJs rather than other options?
    2. \n
  2. What if there is some conflict with your manager. How will you resolve them?
    3. \n
  3. What if a mentor in a new Organization is not helping much how would you be going to tackle the situation?
    4. \n
\n\n

Then I was asked, If I have any questions for them and what I would like to work on.(If you see my profile, I'm more of a full-stack guy. \ud83d\ude05 They said we're a flexible team you can work on anything until you're sure about its working \ud83e\udd29)

\n\n

How to prepare: 60 Toughest Interview Questions\ud83d\ude0e

\n\n
\n

After this round, I got very excited as I wanted to work as a Full-stack guy and got a green flag from the Manager. \ud83d\udd7a\ud83c\udffb

\n
\n\n

\n \n \n Culture\n

\n\n

In this round, we discussed the working of the company.

\n\n

This round was all about behavioral and situation questions like how will you react if the project you're working on for a few months gets shelved.

\n\n

\n \n \n \ud83e\udd73The End\n

\n\n

After all these rounds, I got an Offer letter\ud83d\udc8c and I accepted it (voil\u00e0 \ud83c\udf8a).
\nI really liked the complete interview process at Unacademy. All the rounds were more oriented toward discussion rather than typical Questions and Answers sessions.

\n\n

Big thanks to Unacademy for giving me chance to prove myself and to the Talent Acquisition team for the wonderful interview experience. I can't even imagine that I would ever receive an offer from Unacadmey, whole process was like a dream to me (some say I'm still dreaming till this date \ud83d\ude33)

\n\n

If you're someone who wants to build the future of education, please apply here \ud83d\udc49\ud83c\udffbhttps://apply.workable.com/unacademy/

\n\n", + "slug": "unacademy-software-engineer-interview-experience-web", + "status": "approved" + }, + { + "title": "Day 18: My Frontend Interview Experience at Redisolve \u2013 What I Learned", + "original_url": "https://dev.to/seenuvasan_p/day-18-my-frontend-interview-experience-at-redisolve-what-i-learned-179", + "source": "dev.to", + "author": "SEENUVASAN P", + "published_at": "2025-06-23T11:00:19Z", + "tags": "payil", + "summary": "Today, I had an exciting experience attending a frontend developer interview at Redislove, located in...", + "formatted_content": "

Today, I had an exciting experience attending a frontend developer interview at Redislove, located in Nandanam. The first round was a written test, which consisted of 20 questions covering core frontend concepts. I wanted to share the questions and a brief overview of the topics, which might help others preparing for similar roles.

\n\n

\n \n \n Interview Questions \u2013 Round 1 (Written Test)\n

\n\n\n\n
\n
1.How to optimize a webpage for performance?\n    Use lazy loading, compress images, minimize CSS/JS, use CDN, cache assets, and avoid render-blocking resources.\n\n2.How is CORS handled in JavaScript?\n    CORS (Cross-Origin Resource Sharing) allows restricted resources on a web page to be requested from another domain. It\u2019s handled using HTTP headers or by setting up a proxy or modifying server-side configurations.\n\n3.What is a closure and how does it work?\n    A closure is a function that remembers its outer variables even after the outer function has finished executing.\n\n4.Explain about positions: relative, absolute, and fixed in CSS.\n\n        relative: positions the element relative to its normal position.\n\n        absolute: positions the element relative to the nearest positioned ancestor.\n\n        fixed: positions the element relative to the viewport, staying fixed during scroll.\n\n5.What is a media query and how does it work?\n    Media queries apply different CSS styles based on screen size, orientation, or resolution.\n\n6.What is SPA (Single Page Application)?\n    A web application that loads a single HTML page and dynamically updates content without refreshing the entire page.\n\n7.Client-side vs Server-side rendering\n\n        Client-side rendering: content is rendered in the browser using JavaScript.\n\n        Server-side rendering: content is rendered on the server and sent as a fully formed HTML.\n\n8.Explain about npm and yarn\n    Both are package managers. npm comes with Node.js, while yarn was created by Facebook for faster and more reliable installs.\n\n9.How do you manage versioning and collaboration using Git?\n    Using Git branches, commits, pull requests, rebasing, and merge strategies. Platforms like GitHub or GitLab help in collaboration.\n\n10.Build tools like Webpack or Vite are used for?\n    They bundle and optimize frontend assets for development and production, improving performance and modularity.\n\n11.Difference between development and production environments\n\n        Development: with debug tools, source maps, and no minification.\n\n        Production: optimized, minified code with performance enhancements.\n\n12. How do you debug a frontend application?\n    Using browser dev tools, console logs, breakpoints, network tabs, and tools like React DevTools.\n\n13.Difference between id and class in HTML\n\n        id: unique and used for one element.\n\n        class: can be reused for multiple elements.\n\n14.How to use the CSS Box Model?\n    Understand how margin, border, padding, and content affect layout and spacing.\n\n15.Difference between arrow function and traditional function\n\n        Arrow functions do not have their own this, arguments, or new.\n\n        Traditional functions are more flexible in usage.\n\n16. Explain em, rem, and px in CSS\n\n        px: fixed size\n\n        em: relative to parent\n\n        rem: relative to root (html) element\n\n17. What are template literals and why are they used?\n    Template literals allow embedded expressions and multi-line strings using backticks ``.\n\n18.Explain var, let, and const in JavaScript\n\n        var: function-scoped\n\n        let: block-scoped, reassignable\n\n        const: block-scoped, not reassignable\n\n19.Synchronous vs Asynchronous JavaScript\n\n        Synchronous: code runs in sequence.\n\n        Asynchronous: code can run in the background (e.g., with setTimeout, fetch).\n\n20.How does the event loop work in JavaScript?\n    The event loop manages the call stack and task queue to handle asynchronous callbacks without blocking the main thread.\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

\ud83d\udcad Final Thoughts

\n\n

This interview was a great refresher on core frontend concepts. Whether you're a beginner or experienced developer, it's crucial to understand the fundamentals clearly. Preparing well and practicing problem-solving is key.

\n\n

If you're preparing for frontend roles, I hope this list helps. I\u2019m planning to write more about how I answered these questions in detail \u2014 stay tuned!

\n\n", + "slug": "day-18-my-frontend-interview-experience-at-redisolve-what-i-learned", + "status": "approved" + }, + { + "title": "My Unorthodox Frontend Interview", + "original_url": "https://dev.to/mazenemam19/my-unorthodox-frontend-interview-com", + "source": "dev.to", + "author": "Mazen Emam", + "published_at": "2022-09-25T14:36:48Z", + "tags": "inter", + "summary": "Picture from the Search Committee episode\u200a\u2014\u200aThe Office tv series Last week I did my first technical...", + "formatted_content": "


\nPicture from the Search Committee episode\u200a\u2014\u200aThe Office tv series

\n\n

Last week I did my first technical interview at a medium-size tech company, most of the interviews I had so far were at small-size tech companies, It was interesting and different from other interviewing experiences I had before.

\n

\n \n \n Q: What is the difference between small and medium size company interviews?\n

\n\n

A: The difference is in the type of questions and what the interviewer seeks to learn about you.

\n\n

Here is a comparison between applying to a React Developer role in those two different organizations.

\n\n

In the small ones, you would typically be asked about programming languages and frameworks you will use in your daily life.

\nFor example: in my last interview in a small company I was asked about the difference between var, let, and const, some more Javascript questions, and a Javascript problem, I was also asked If I\u2019ve used Typescript before, then we moved to the React, I was asked about Context API, React Router and Redux Toolkit.

\n\n

In the medium ones, the interviewer is after something else, they want to know if you know the value of the code you are writing and its effect on the whole project.

\nExample: I was asked about clean code, object-oriented programming (OOP), testing (unit testing\u200a\u2014\u200aautomated testing), website performance, tracking traffic, data structure, and the space and time complexity of an algorithm.

\n\n

I was also asked some general frontend questions which I regret not answering perfectly :(

\n\n

Hopefully, they will help you be more prepared for your next interview\ud83e\udd1e

\n\n

Q1: What is the difference between cookies, local storage, and session storage?

\n\n

\n

\n\n

Q2: What is the difference between HTTP and HTTPS?

\n\n

\n

\n\n

Q3: What is the difference between Put and Patch request methods?

\n\n

I didn\u2019t know the answer to this one at all \ud83d\ude10 I\u2019m still embarrassed about it.

\n\n

\n

\n\n

Q4: What are 3 ways you can use to optimize a page that loads 100 Images

\n\n\n\n

I found this article to be very insightful on optimization and performance.

\nHave you heard of AbortController API before \ud83d\udc40 Check out this article!

\n\n

Q5: Find all the duplicates in an array and explain the time complexity of your algorithm

\n\n

At the time of the interview, I didn\u2019t do well at this one, I gave an algorithm with O(n\u00b2) complexity\ud83e\udd26\u200d\u2642 but this incident taught me a lesson about the importance of learning algorithms.

\n\n

On a regular day, I\u2019d probably solve this problem with a code like this:
\n

\n\n
\n
function removeDuplicates(arr) {\n   return arr.filter((item,index) => arr.indexOf(item) === index);\n }\n\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

If you are looking for a more efficient solution, you should check the video below, I tested both solutions on Leetcode and the one from the video was way faster than my solution.

\n\n

\n

\n\n

Bonus: Do you know that for loop is the fastest loop?

\n\n

Hope you enjoyed this read and have refreshed your memory on some interview topics.

\n\n

Ciao\ud83d\udc4b

\n\n", + "slug": "my-unorthodox-frontend-interview", + "status": "approved" + }, + { + "title": "Amazon SDE 1 Interview Experience: I received the acceptance letter!", + "original_url": "https://dev.to/oa_vo_support/amazon-sde-1-interview-experience-i-received-the-acceptance-letter-42i8", + "source": "dev.to", + "author": "OA VO Interview", + "published_at": "2025-08-15T08:35:05Z", + "tags": "caree", + "summary": "Timeline January: Job application February: Initial interview Mid-May: Interview...", + "formatted_content": "

\n \n \n Timeline\n

\n\n

January: Job application
\nFebruary: Initial interview
\nMid-May: Interview invitation
\nJune: Final interview

\n\n

\n \n \n The Interview Process\n

\n\n

Round 1: LP+Coding
\nBQ 1: How do you adjust your work strategy and manage tasks when facing time pressure?

\nBQ 2: How do you adapt and effectively execute new tasks or goals during work transitions or changes?

\n\n

2 LP questions, followed by several follow-up questions. For the second BQ, the interviewer encouraged me to choose a story that better aligns with the LP. Here, I combined my past project experience from school with the STAR method to answer. The interviewer was very satisfied with my second answer and kept nodding in agreement.

\n\n

Q: Similar to designing an iterator to retrieve the next smallest number from K arrays.

\n\n

Here, I used object-oriented design (OOD) and a min-heap. We discussed test cases (TC) and scenarios (SC). The initial implementation went smoothly, but I was later asked about the scalability of this solution for more arrays and how to perform arbitrary operations on K arrays. I\u2019m not sure if my answer was correct; I suspect there may be multiple acceptable solutions. I also asked the interviewer a few questions afterward, and the conversation went smoothly.

\n\n

Round 2:Coding
\nQ1: Merge all intervals that may overlap and return the merged result.

\n\n

The key to this problem lies in sorting the preprocessing. If the intervals are sorted by their starting points, adjacent intervals can be merged in order. For example, after sorting, you only need to compare the endpoint of the current interval with the starting point of the next interval to determine whether they need to be merged. The endpoint of the merged interval is the maximum value of the two, and the starting point is the starting point of the current interval. Here, I used a greedy algorithm and solved it smoothly.

\n\n

Q2: Determine whether the sum of the path from the root to the leaf of a binary tree is equal to the target value.

\n\n

The DFS solution works fine. First, recursively traverse the tree, accumulate the path sum, and then determine whether it meets the target. When the current path does not meet the rules, perform backtracking.

\n\n

Round 3:Coding
\nQ: Find the number of islands in a 2D array

\n\n

The algorithm checks each position in the two-dimensional grid one by one to ensure that every land position is taken into account. By using the loops for i in range(len(grid)) and for j in range(len(grid[0])), all positions are traversed to ensure that no possible islands are missed.
\nWhen an unvisited land position is encountered, DFS is initiated to mark all adjacent land positions (adjacent in all four directions) as visited (changed to \u20180\u2019). Once marked as visited, other land positions on the same island will not be counted again.

\n\n

The DFS recursive traversal continues to expand until all adjacent land areas have been visited and marked, which exactly covers the entire range of the island. DFS ensures that each time it is initiated, it marks an entire connected land area, which meets the definition of an island in the problem statement.

\n\n

Each time DFS is initiated, it means a new island has been found, so the counter is incremented by one. Through this mechanism, the final value of the counter is exactly the number of islands, meeting the problem requirements.

\n\n

Follow-up: If you could turn a body of water into land, how would you operate to obtain the largest island?

\n\n

This follow-up question was a bit tricky for me, but after discussing methods with the interviewer, we found the correct solution. The interviewer approved all my answers and discussed technical details and software engineering practices.

\n\n

## Interview Summary & Suggestions
\nI received the offer letter on June 10. I recommend that everyone thoroughly research all Amazon LPs until you can recite them off the top of your head, and prepare two different STAR cases for each LP. It is best to use data in your cases to prove that your logical thinking is clear. You can also show your enthusiasm for the company and its employees. The interview process is very energy-consuming, so please be prepared physically and mentally. If you encounter any difficulties or have any questions, please feel free to come here to find solutions.

\n\n", + "slug": "amazon-sde-1-interview-experience-i-received-the-acceptance-letter", + "status": "approved" + }, + { + "title": "Mentorship to Full-time Offer | Flipkart SDE-1 Interview Experience", + "original_url": "https://dev.to/parulchaddha/mentorship-to-full-time-offer-flipkart-sde-1-interview-experience-13bp", + "source": "dev.to", + "author": "Parul Chaddha", + "published_at": "2024-09-01T22:24:05Z", + "tags": "flipk", + "summary": "Hello readers! I\u2019m excited to share my journey of interviewing at Flipkart, which led to an offer for...", + "formatted_content": "

Hello readers!
\nI\u2019m excited to share my journey of interviewing at Flipkart, which led to an offer for a 6-month internship (January to July) and a full-time Software Development Engineer (SDE-1) role. I got this opportunity through Flipkart\u2019s Girls Wanna Code 5.0 program, a mentorship initiative designed to support Women in Tech.

\n\n

Out of over 13000+ applications, only 200 women were chosen for the program. From that group, the top 30 were selected for interviews. I feel incredibly lucky to have been one of them, and in this blog, I\u2019ll walk you through my experience and the lessons I learned along the way.

\n\n

Points considered to be in TOP 30:

\n\n

1- Your interaction with your mentor : Once you are selected for the program, you will be assigned a mentor
\n2- Attendance in the sessions : You will get to attend live sessions
\n3- Scores of the contests held during the mentorship : You will have to clear multiple mini contests
\n4- Most Important- Scores of the Final Assessment : Usual DSA questions

\n\n

There were a total of 3 rounds of interview (2 Tech + 1 Hiring Manager ) for all Top 30. Here is my interview experience:

\n\n

Round 1 : Technical Interview (PS/DS 1) \u2014 Offline Flipkart Office,Bengaluru

\n\n

My first interview was an in-person technical round held at Flipkart\u2019s Bengaluru office. During this hour-long session, I was presented with two DSA (Data Structures and Algorithms) questions \u2014 one easy and one medium-level. However, I completed the interview in just 35 minutes.

\n\n

The first question focused on string manipulation, while the second was a dynamic programming problem named \u201cUnique Paths II\u201d from LeetCode. I was asked to explain my approach, perform a dry run by drawing the recursion tree, and then write the optimized code on the whiteboard.

\n\n

Round 2 : Technical Interview (PS/DS 2) \u2014 Online

\n\n

My second interview was online and it was an hour long that I concluded in 50 minutes. During this round, I was given one medium-level and one hard-level question.

\n\n

The first question was to determine if a linked list is a palindrome, and the second involved finding the distance between two nodes in a binary tree.

\n\n

I explained and wrote both the brute-force and optimized solutions for each problem. The interviewer was satisfied with my approach and solutions.

\n\n

Round 3: Hiring Manager \u2014 Online

\n\n

This round was a mix of CS fundamentals + Projects + Past Experience + HR questions.

\n\n
\n

Here is the list of questions that were asked to me.
\n1- My past internship experience and questions related to that.
\n2- About Projects and cross-question related to the implementation and its features.
\n3- What is the difference between process and threads?
\n4- What is deadlock?(Interviewer wasn\u2019t expecting the bookish language instead a real-life example)
\n5- Why do we use OOPs ?
\n6- Difference between SQL and NoSQL databases?
\n7- What is Cap theorem for NoSQL databases?
\n8- Some SQL queries.
\n9- What is Master-Slave architecture in DBMS and it\u2019s working.
\n10- My ambitions and how am I fit for the role?
\n11- Why do I want to join Flipkart?
\n12- Why do we hire you?
\n13- My strengths and my weaknesses.
\n14- How will I handle the pressure of work ?
\n15- What do you think that you need to change in yourself?

\n
\n\n

RESULTS!!
\nFinally #Flipkart_it_is!!!! and my happiness knew no bounds after that\u2026\u2026.

\n\n

Resources :

\n\n
    \n
  1. Flipkart Interview Questions on GFG
    2. \n
  2. GFG past interview experiences
    3. \n
  3. DSA sheet by Fraz -> link\n
    4. \n
  4. DSA sheet by Striver(takeUforward) -> link\n
    5. \n
  5. DSA sheet by NeetCode -> link\n
    6. \n
\n\n

Thank you for reading! In case you need any help, feel free to reach out to me! You can reach out to me for any queries via LinkedIn :) If the blog was helpful, show some love and smash the clap button below!!!

\n\n", + "slug": "mentorship-to-full-time-offer-flipkart-sde-1-interview-experience", + "status": "approved" + }, + { + "title": "Amazon Virtual Interview Experience - Frontend Engineer II", + "original_url": "https://dev.to/sunil12738/amazon-virtual-interview-experience-frontend-engineer-ii-284c", + "source": "dev.to", + "author": "Sunil Chaudhary", + "published_at": "2020-12-28T10:02:17Z", + "tags": "javas", + "summary": "About a few months ago I was looking out for a job when I got the opportunity to be interviewed at Am...", + "formatted_content": "

About a few months ago I was looking out for a job when I got the opportunity to be interviewed at Amazon. As I started my research online (or googling as others would say), I found less articles for frontend interviews and that too for virtual processes were close to none. So, after the interview process was over, I thought of writing down an article of my own experience at Amazon.

\n\n

Hoping that a lot of people will be benefitted by this!

\n\n

Even if you are not a frontend/UI developer, do have a look as a lot of processes are common for both frontend and backend engineers.

\n\n

This will be a detailed article going in depth of the entire process from start to end. I will be covering the entire virtual process, online tools, interview rounds (including questions summary) and their timelines as well as will be attaching the relevant docs provided by Amazon. So without further waiting, let's start.

\n\n\n
\n\n

\n \n \n Brief Summary about me\n

\n\n

(at the time of interview process)

\n\n\n\n\n
\n\n

\n \n \n Role - Frontend Engineer II (FE2)\n

\n\n

The Role I interviewed for was for a Frontend Engineer II (FE2) role (JD attached at bottom). Now, Amazon do have multiple categories of roles even in frontend development. There is one Web Development Engineer (WDE) role and other type is Frontend Engineer (FE) role. As per the interviewers, FE role is more senior in terms of responsibilities and work compared to WDE. So even for same level (e.g. FE2, WDE2); FE2 will have more responsibilities and salary than WDE2.

\n\n\n
\n\n

\n \n \n Process\n

\n\n

Do note that Amazon is a very big firm and sometimes, it takes a lot of time to get the process done. Process was relatively longer for me. From applying till the final selection/rejection it took about 3 months.

\n\n

\n \n \n Shortlisting\n

\n\n

My profile went through third party recruitment firm CareerNet Technologies. Kiran from Careernet and their team helped a lot in the overall process. I used to get constant and timely updates from them. All the info related to interviews, shortlisting was conveyed properly. My resume was submitted in early week of March 2020 and took a few weeks to get shortlisted for next rounds.

\n\n

\n \n \n Number of rounds:\n

\n\n

There were 6 rounds in total (including one screening round). All the rounds were done virtually. Most of the rounds were scheduled 1 hour rounds (but few got extended to 2 hours in my case).

\n\n

\n \n \n Arrangements/Logistics for Virtual Interview\n

\n\n

So, the way interviews are happening now will be very different from how they used to happen onsite (pre-covid era). The rounds happened over video call (except for screening which was over chat). I used to get mails few days before the interview. It contained the link for the chat, the online editor as well as white board tool. The mail also contained various other links for me to read and get to know about the company, interview tips and preparation docs etc. The links for documents have been added at bottom.

\n\n\n\n\n
\n\n

\n \n \n Timelines\n

\n\n

I started to look for a job in mid February 2020 and had started to apply for Amazon via referral as well as third party recruitment firms.

\n\n

Here is also a timeline of the various rounds. As far as I know, this can vary for individuals depending upon the requirements. The interviews happened as per my convenience and even some interviews happened on Saturdays as my week days were occupied with my work. So, amazon was very much flexible with it.

\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Date
Resume submitted1st week of March 2020
Screening Round17th April 2020
Round 112th June 2020
Round 212th June 2020*
Round 313th June 2020
Round 415th June 2020
Round 518th June 2020
Round 618th June 2020
Result23rd June 2020
\n\n

*This round was interrupted and postponed due to internet issues. So it wasn\u2019t evaluated.

\n\n

I wasn\u2019t expecting the process to take so long. So, somewhere around screening, I had already joined another firm. But, when the interview call came, I just thought of giving interviews so as to get an experience which will help me in future.

\n\n\n
\n\n

\n \n \n Interview Rounds\n

\n\n

There were about 6 interview rounds (including screening round). The pattern was very standard with the only exception being that this was more related to frontend perspective. The questions were mostly restricted to html/css/javascript and the basic principles. No framework specific questions were asked.

\n\n

Briefly summing up the interview rounds:

\n\n\n\n

In almost all rounds, the solution expected was to be perfect covering all the edge cases and with best practices. A lot of discussion happened on why certain approaches were better or why this has been done or how can you improve this. This is why it sometimes becomes difficult to crack the interview.

\n\n\n
\n\n

\n \n \n Result\n

\n\n

My profile wasn\u2019t shortlisted. This was the mail sent by their HR team.

\n\n

\"Alt

\n\n

Post this mail, it took about 10 days for HR to get me the detailed feedback. It was mainly the Data Structure and Algorithms implementation where they felt I need to work a bit more and HR asked me to reapply after some months (the usual stuff \ud83d\ude00).

\n\n

Also, an interesting point to note here is that during the course of interview Amazon also tries to move the profile between various other job profiles they have if the candidate is not suitable for current applied position which is a pretty good thing on their part. So, they themselves will recommend other positions and will change the course of interviews.

\n\n\n
\n\n

\n \n \n Some useful links:\n

\n\n\n\n\n
\n\n

\n \n \n Summary\n

\n\n

Overall it was a nice interview experience. Got to learn a lot of things.

\n\n

Note: I haven\u2019t included a very detailed description of all the interview questions as the article was getting really long. But do let me know in the comments and I will write a separate article on that. Additionally, I have dumped all the interview questions (even from other companies as well) in this Github Repository. Do check that out as well and contribute by practising and submitting your solutions :-).

\n\n

Please share it amongst your colleagues, friends and others who might get benefitted from it.

\n\n

Thanks!

\n\n\n
\n\n", + "slug": "amazon-virtual-interview-experience-frontend-engineer-ii", + "status": "approved" + }, + { + "title": "Frontend Internship Interview Experience", + "original_url": "https://dev.to/ashutoshdash/frontend-internship-interview-experience-3a7i", + "source": "dev.to", + "author": "Ashutosh Dash", + "published_at": "2022-03-27T03:53:54Z", + "tags": "javas", + "summary": "Long story short, I applied to XYZ company through Internshala for a frontend developer position....", + "formatted_content": "

Long story short, I applied to XYZ company through Internshala for a frontend developer position.

\n\n\n\n

\n \n \n Q1. Tell me about yourself apart from your skill sets.\n

\n\n

Ans: My name is Ashutosh Dash and I'm from Balasore, Odisha. Currently, I'm in my 1st year of MCA at the Odisha University of Technology and Research. My hobbies include books reading and listening to songs. My strength includes my ability to work as part of a team. During hackathons, I always lead my team and out of 5 hackathons my team has secured a position in the top 10 or as a runner up. Also, I have volunteered as a frontend developer for GirlScript Bhubaneswar, where we built a homepage for them.

\n\n

\n \n \n Q2. What are the advantages of react?\n

\n\n

Ans: 1. Reusable Components
\n2. Easier to write code in JSX.
\n3. Ability to create SPA(Single Page Application)
\n4. SEO friendly (I don't why! Please mention in comments if you know)
\n5. Virtual DOM helps in smooth and faster performance.

\n\n

\n \n \n Q3. Angular vs React\n

\n\n

Ans: 1. Angular is a framework built using Typescript while React is a library built using JSX.
\n2. Angular is used to create complex projects while React is used to build UI components.
\n3. The learning curve for Angular is more than React.

\n\n

\n \n \n Q4. What are the keys in react?\n

\n\n

Ans: A key helps in uniquely identifying a list item or giving the elements a stable identity

\n\n

\n \n \n Q5. Differences between Functional Components and Class Components in React\n

\n\n

Ans: I'm not sure about its answered but I guess functional components codes are much shorter to write, more straightforward and have fewer complexities for a larger product.

\n\n

\n \n \n Q6. What is virtual DOM? How react render virtual dom?\n

\n\n

Ans: A virtual DOM is like a virtual representation of actual DOM UI kept in memory and synced with actual DOM UI by ReactDOM. Updating virtual DOM is faster than actual DOM.
\nReact compares the actual DOM with the changes in the virtual one stored in memory. Once it sees which component is updated it then replaces the actual component with the changed one.

\n\n

\n \n \n Q7. What is Redux?\n

\n\n

Ans: Redux is a centralized state container that holds the value of the state.

\n\n

\n \n \n Q8. What is prop drilling?\n

\n\n

Ans: A little long explanation, so linking this video.

\n\n

\n \n \n Q9. What are states?\n

\n\n

Ans: A state is a property storage area belonging to the component. Every time a state is updated, the component is re-rendered.

\n\n

\n \n \n Q10. What is JWT?\n

\n\n

Ans: JSON Web Token(JWT) is used for authentication protocol on the web. It is based on the exchange of JSON files for authentication and authorization.

\n\n

Thank you for taking your time to read this article. Please let me know if you want me to improve something.
\nYou can connect with me on LinkedIn and Twitter.
\nWant to discuss an amazing opportunity, you can visit my portfolio if I'm a good fit for you.

\n\n", + "slug": "frontend-internship-interview-experience", + "status": "approved" + }, + { + "title": "Interview experience at Google - SDE II", + "original_url": "https://dev.to/rajeshroyal/interview-experience-at-google-sde-ii-n09", + "source": "dev.to", + "author": "Rajesh Royal", + "published_at": "2022-06-19T15:36:47Z", + "tags": "javas", + "summary": "It was my first time getting an interview at any FAANG company. The position was for SD II Fullstack...", + "formatted_content": "

It was my first time getting an interview at any FAANG company. The position was for SD II Fullstack Developer Bengaluru | Hyderabad | Remote.

\n\n

After the phone call with recruiter he schedule the interview 1 month after so I can have a little time to prepare for DS and Algo. Although I never took DS and Algo seriously and had a little idea about these topics.

\n\n

First Round:
\nIt was a 45min Technical Interview round. I was asked 2 question and I was able to solve those Problems as these was easy problems [as feedback says It was warm up round].

\n\n

I was Rejected and given Boundary Line candidate feedback. I asked recruiter and he gave me detailed feedback where I missed and also the feedback of the person who took my Interview that where I was lacking.

\n\n

Mistakes I made

\n\n\n\n
\n

Although I though I did very good but It was not even enough. Will have better luck next time.

\n
\n\n

Questions
\nAs per the guideline cannot share the exact questions but I will mention the type here.

\n\n
    \n
  1. Was related to string validation [Leetcode easy].
    2. \n
  2. Something similar to generic language translator. [Leetcode medium].
    3. \n
\n\n

Feedback:

\n\n\n\n
\n

I was able to improve my solution but only after prompting by interviewer so never wait for him to ask, just tell him if he wants an optimal solution ?.
\nMost candidates gets to coding stage but I was able to only get to planning stage in second question.

\n
\n\n

Note:

\n\n\n\n
\n

My advice to you all, go to the interview with no expectations, don't let thoughts about failure get in the way of your own success. Keep your mind free, this is much easier said then done. from: @helloKali

\n
\n\n

\u00a0
\ncover image is taken from google search:

\n\n

Thanks for reading and best of luck \u270c\ufe0f

\n\n", + "slug": "interview-experience-at-google-sde-ii", + "status": "approved" + }, + { + "title": "Day 16: My First Round Node.js Interview Experience at Payilagam \u2013 Writing Round", + "original_url": "https://dev.to/seenuvasan_p/day-15-my-first-round-nodejs-interview-experience-at-payilagam-writing-round-4pb1", + "source": "dev.to", + "author": "SEENUVASAN P", + "published_at": "2025-06-19T04:47:16Z", + "tags": [ + "payilagam", + "node", + "programming" + ], + "summary": "Today (17th June 2025), I attended the first round of my Node.js interview at Payilagam Institute,...", + "formatted_content": "

Today (17th June 2025), I attended the first round of my Node.js interview at Payilagam Institute, conducted by Maan Sarovar Tech Solutions Pvt Ltd. The first round was a written test and the duration was 1 hour.

\n\n

This round mainly tested my JavaScript and Node.js fundamentals. I faced a set of 20 questions that covered both technical concepts and personal opinion-based questions.

\n\n

Here are the questions I got in the interview:

\n\n
    \n

  1. What do you know about Maan Sarovar Tech Solutions?

    2. \n

  2. How do you say 'You are the right candidate' for this position?

    3. \n

  3. What is the difference between a function declaration and function expression?

    4. \n

  4. How does setTimeout work?

    5. \n

  5. How do you select elements from the DOM?

    6. \n

  6. What is the purpose of async and await in JavaScript?

    7. \n

  7. What is a callback function?

    8. \n

  8. What is Node.js and how does it work?

    9. \n

  9. Why does Node.js use the V8 engine (used by Google)?

    10. \n

  10. Why is Node.js single-threaded?

    11. \n

  11. Can you access the DOM in Node.js?

    12. \n

  12. How to create a simple HTTP server in Node.js?

    13. \n

  13. What is the difference between synchronous and asynchronous functions?

    14. \n

  14. What are the different types of HTTP requests?

    15. \n

  15. Explain the this keyword.

    16. \n

  16. What is the difference between undefined and null in JavaScript?

    17. \n

  17. What is the difference between == and === operators in JavaScript?

    18. \n

  18. What are truthy and falsy values?

    19. \n

  19. What is the difference between global and local scope?

    20. \n

  20. Startup vs Bigger Companies \u2013 Which is your preference and why?

    21. \n
\n\n", + "slug": "day-16-my-first-round-nodejs-interview-experience-at-payilagam-writing-round", + "status": "approved" + }, + { + "title": "My Node.js - First Interview Experience & Important Concepts!", + "original_url": "https://dev.to/sathish_226_/my-nodejs-first-interview-experience-important-concepts-48j9", + "source": "dev.to", + "author": "Sathish A", + "published_at": "2025-06-18T17:45:01Z", + "tags": [ + "webdev", + "javascript", + "node", + "career" + ], + "summary": "Hello, friends!! Today I attended my first Node.js interview round as part of my backend...", + "formatted_content": "

Hello, friends!!

\n\n
\n

Today I attended my first Node.js interview round as part of my backend development journey. Since Node.js is closely related to JavaScript, most of the interview questions covered both JavaScript and Node.js basics.

\n\n

This interview made me realize how important it is to understand core concepts before diving deeper into backend development.

\n
\n\n

Let me share what I learned and some important topics with short explanations!!

\n\n

JavaScript & Node.js Topics from the Interview:

\n\n

1.Function Declaration vs Function Expression:

\n\n\n\n

2.setTimeout() in JavaScript:

\n\n\n\n

Example:
\n

\n\n
\n
setTimeout(() => { console.log(\"Hello after 2 seconds\"); }, 2000);\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

3.Selecting Elements from DOM:

\n\n

Example:
\n

\n\n
\n
document.getElementById('id');  \ndocument.querySelector('.class');\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

4.Async/Await in JS:

\n\n\n\n

5.Callback Function:

\n\n\n\n

6.What is Node.js?

\n\n\n\n

7.Why Node.js uses V8 Engine?

\n\n\n\n

8.Why Node.js is Single-threaded?

\n\n\n\n

9.Can you access DOM in Node.js?

\n\n

\u274c No, because Node.js runs on the server, not in the browser.

\n\n

10.Simple HTTP Server in Node.js:
\n

\n\n
\n
const http = require('http');\nhttp.createServer((req, res) => {\n  res.write('Hello World');\n  res.end();\n}).listen(3000);\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

11.Synchronous vs Asynchronous Functions:

\n\n\n\n

12.HTTP Methods:

\n\n\n\n

13.\u2018this\u2019 Keyword in JavaScript

\n\n\n\n

14.undefined vs null

\n\n\n\n

15.== vs ===

\n\n\n\n

16.Truthy & Falsy Values:

\n\n\n\n

17.Global vs Local Scope

\n\n\n\n

18.Startup vs Big Companies - My Preference:

\n\n

1.Startups = Learning, Growth, Multi-tasking
\n2.Big Companies = Stability, Process, Big Teams
\n3.For now, I prefer startups to learn and grow fast!

\n\n

\"

\n\n

Takeaway for the Day:

\n\n
\n

\"Strong JavaScript knowledge is the foundation for learning Node.js. I\u2019ll keep practicing small tasks daily!\"

\n
\n\n

Learn!!. Build!!. Repeat!!...

\n\n", + "slug": "my-nodejs-first-interview-experience-important-concepts", + "status": "approved" + }, + { + "title": "Frontend interview experience at CoinDCX", + "original_url": "https://dev.to/sadanandpai/frontend-interview-experience-at-coindcx-1ac5", + "source": "dev.to", + "author": "Sadanand Pai", + "published_at": "2021-11-27T03:34:44Z", + "tags": [ + "javascript", + "react", + "webdev", + "angular" + ], + "summary": "Hello folks, I am glad that I am a part of CoinDCX organization now and got the opportunity to make...", + "formatted_content": "

Hello folks,

\n\n

I am glad that I am a part of CoinDCX organization now and got the opportunity to make crypto accessible to millions. In this post, I would like to share my interview experience at CoinDCX.

\n\n



\nHow did I apply

\n\n

I was invited to a job search platform called Enthire via Linkedin by a Talent Acquisition Lead. It's a platform that helps candidates to get fast-tracked opportunities with verified employers by giving interviews with their Industry Experts. Depending on these interview results, Enthire recommends and helps us to apply for good opportunities on their platform.

\n\n



\nInterview at Enthire - JS and DSA (45 mins)

\n\n

Enthire conducted a generic frontend interview round that was focused on core JavaScript and DSA (data structures & algorithms). The difficulty level of questions on JavaScript was intermediate to advanced. The difficulty level of questions on DSA was beginner to intermediate.
\nI got a good rating \u2605\u2605\u2605\u2605\u2606 in this interview round which allowed me to apply for CoinDCX.

\n\n



\nRound 1 at CoinDCX - Assessment (1 hour)

\n\n

My resume got shortlisted by CoinDCX and 1st round of assessment was scheduled. This was a multiple-choice quiz. Questions covered both frontend (HTML, CSS, JS, Angular) and aptitude. Many of the questions were tricky and challenging due to the time limits.

\n\n



\nRound 2 at CoinDCX - System Design (45 mins)

\n\n

The system design interview round started with a discussion on my core skills and framework knowledge. I was given a large component of the CoinDCX web application and was asked to design the system. I started by clarifying all my doubts and explaining my approach. Once I got the approval for the approach, I proceeded by breaking down this complex system into components. I explained the design of each component and finally the interaction & integration of the components to build the whole system.

\n\n

I was then asked to code the logic for one of the components of this complex system in JavaScript. I explained the logic and coded the core functionality.

\n\n



\nRound 3 at CoinDCX - Live coding round (1 hour)

\n\n

The live coding interview round started with a few of the advanced questions on JavaScript concepts. As I was more comfortable coding React than Angular, I was asked to code a small component using React by sharing my screen. Once I came with the functional code, many more complicated scenarios were introduced to the same component. As Angular is the technology being used at CoinDCX I was given a new problem to code using Angular. Similar to the previous challenge, variations were introduced progressively.

\n\n

Once the live coding session was over, many advanced questions were asked on JavaScript, CSS, and Angular framework.

\n\n



\nRound 4 at CoinDCX - Cultural fit (1 hour)

\n\n

The cultural fit interview round started with a few behavioral questions. Then there was a dedicated question on studying and coming up with a practical solution for a real-world problem (non-technical). It was more like a brainstorming discussion with no specific right answer. The rest of the 30 mins were focused on the responsibilities I was taking care of previously and more on the processes.

\n\n



\nResults

\n\n

After a few days, I got to know from HR that I got selected. The whole interview process was super smooth and the interviewers were also highly knowledgeable. Fortunately, I was offered Senior Software development engineer (SDE2) at CoinDCX and happily accepted the offer.

\n\n

\"Screenshot

\n\n

I joined CoinDCX in the 1st week of April 2021 and so far my experience at CoinDCX is awesome. I wish to see my knowledge and career grow at CoinDCX similar to the price of \u20bf bitcoin \ud83d\udcc8 in recent years.

\n\n
\n

To know more about the frontend resources and frontend interview preparation, please visit Frontend Learning Kit which is a generic guide to crack interviews of any company for the role of frontend development.

\n
\n\n



\nOther opportunities

\n\n

I had cleared the interviews at Byjus, MediaMonks, Glowroad, ORMAE, PhiGRC, SkillExchange, & Aroha and was rejected at Flipkart & Typeset. I had also applied for frontend roles at CureFit, FireEye, Amazon, Razorpay, Acko, Publicis Sapient, & MEX where my resume was either not shortlisted or never heard back.

\n\n

I did not try to go through referrals for any of the companies in my job search process and utilized only the freely available platforms.

\n\n

If you wish to be a part of CoinDCX and if you think you have the right skill set, then please visit Careers @ CoinDCX

\n\n", + "slug": "frontend-interview-experience-at-coindcx", + "status": "approved" + }, + { + "title": "I Failed 3 React Interviews Before I Understood What They Actually Want in 2026", + "original_url": "https://dev.to/harsh2644/i-failed-3-react-interviews-before-i-understood-what-they-actually-want-in-2026-2hhf", + "source": "dev.to", + "author": "Harsh ", + "published_at": "2026-03-04T06:55:36Z", + "tags": "react", + "summary": "I thought I was ready. I knew hooks inside out. I could explain Virtual DOM in my sleep. I had...", + "formatted_content": "

I thought I was ready.

\n\n

I knew hooks inside out. I could explain Virtual DOM in my sleep. I had memorized the difference between useCallback and useMemo. I had done 50+ LeetCode problems.

\n\n

And I still failed. Three times. Back to back.

\n\n

The third rejection email hit different. I sat back and asked myself \u2014 what are these companies actually looking for?

\n\n

What I discovered changed everything. Here's the full breakdown. \ud83d\ude80

\n\n\n
\n\n

\n \n \n The Hard Truth Nobody Tells You\n

\n\n

React interviews in 2026 are not testing your React knowledge anymore.

\n\n

They're testing your judgment.

\n\n

AI can write components. AI can implement hooks. AI can scaffold entire features in seconds. Companies know this. So they've stopped hiring for syntax and started hiring for something AI cannot replicate \u2014 how you think under pressure.

\n\n
\n

\"AI writes the components. Companies are hiring for judgment, not syntax.\"

\n
\n\n

Let me show you exactly what that looks like in practice.

\n\n\n
\n\n

\n \n \n What They Asked Me (That I Was NOT Prepared For)\n

\n\n

\n \n \n \u274c What I prepared for:\n

\n\n\n\n

\n \n \n \u2705 What they actually asked:\n

\n\n\n\n

See the difference? These aren't trivia questions. These are judgment tests.

\n\n\n
\n\n

\n \n \n The 3 Things That Actually Matter in 2026 Interviews\n

\n\n

\n \n \n 1. Reasoning Under Ambiguity\n

\n\n

Companies give you incomplete scenarios on purpose.

\n\n

Here's a real example from my third interview:

\n\n
\n

\"Build a notification system for our app.\"

\n
\n\n

That's it. No details. No constraints. No tech stack specified.

\n\n

What I did wrong (Interview 1): I immediately started coding. I assumed a simple toast notification. I built it. They stopped me after 5 minutes.

\n\n

What they wanted: Questions first. \"How many notification types? Real-time or polling? Does it persist across sessions? Mobile too or web only? What's the expected volume?\"

\n\n

Developers who clarify before building signal maturity and real-world experience. Junior developers jump straight to code. Senior developers ask questions first.

\n\n

Practice this: Next time someone gives you a vague task, force yourself to ask 3 clarifying questions before writing a single line.

\n\n\n
\n\n

\n \n \n 2. Tradeoff Awareness\n

\n\n

This was my biggest gap. I knew HOW to implement things. I didn't know WHY to choose one approach over another.

\n\n

They would ask: \"How would you manage state in this app?\"

\n\n

My wrong answer: \"I'd use Redux.\"

\n\n

What they wanted to hear:

\n\n
\n

\"For this scale, I'd start with useState and Context. Redux adds boilerplate that isn't justified unless we have complex cross-component state or need time-travel debugging. If the app grows and we hit performance issues with Context, I'd migrate to Zustand \u2014 it's lighter than Redux and has a simpler API. But I'd only do that after profiling confirmed it's necessary.\"

\n
\n\n

See the difference? The second answer shows tradeoff thinking. It names alternatives, explains the reasoning, and acknowledges conditions under which the decision would change.

\n\n

Here are the tradeoffs every React developer should know cold in 2026:
\n

\n\n
\n
State Management:\nuseState \u2192 Context \u2192 Zustand \u2192 Redux\n(Simple) \u2190\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2192 (Complex)\n\nData Fetching:\nuseEffect \u2192 React Query \u2192 SWR \u2192 Server Components\n(Basic) \u2190\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2192 (Production)\n\nRendering:\nCSR \u2192 SSR \u2192 SSG \u2192 ISR\n(Dynamic) \u2190\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2192 (Static/Performance)\n\nStyling:\nCSS Modules \u2192 Tailwind \u2192 CSS-in-JS \u2192 Styled Components\n(Simple) \u2190\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2192 (Dynamic)\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

Practice this: For every technical decision in your next project, write down: \"I chose X over Y because Z. I would switch to Y if W happened.\"

\n\n\n
\n\n

\n \n \n 3. Failure Mode Thinking\n

\n\n

This one surprised me most. In my second interview, after I designed a solution, the interviewer asked:

\n\n
\n

\"Great. Now tell me \u2014 what could go wrong with this approach?\"

\n
\n\n

I froze. I had never thought about my own solution's weaknesses before.

\n\n

What they're testing: Can you think like a senior engineer who has seen production failures?

\n\n

Here's a framework for answering \"what could go wrong\":
\n

\n\n
\n
// When reviewing ANY React architecture, ask:\n\n1. Performance: What happens under heavy load?\n   \u2192 \"If 10,000 users hit this simultaneously...\"\n\n2. State: What happens when state gets corrupted?\n   \u2192 \"If the API returns unexpected data...\"\n\n3. Edge cases: What happens with empty/null data?\n   \u2192 \"If the user has no notifications yet...\"\n\n4. Memory: What happens if the component unmounts mid-fetch?\n   \u2192 \"We need cleanup in useEffect to avoid memory leaks...\"\n\n5. Failure: What happens if the API is down?\n   \u2192 \"We need error boundaries and fallback UI...\"\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

The interviewer doesn't want a perfect solution. They want to see that you think about failure before it happens.

\n\n\n
\n\n

\n \n \n The Frontend System Design Question (That Caught Me Off Guard)\n

\n\n

My third interview had a 45-minute system design round. I was expecting the usual backend stuff \u2014 databases, load balancers, distributed systems.

\n\n

Instead: \"Design the architecture for a collaborative document editor like Google Docs \u2014 frontend only.\"

\n\n

This is Frontend System Design \u2014 and it's now standard at mid-level+ interviews. Here's the framework I learned after failing:

\n\n

\n \n \n The 5-Step Framework:\n

\n\n

Step 1: Clarify requirements (5 minutes)

\n\n\n\n

Step 2: Define the component architecture (10 minutes)
\n

\n\n
\n
App\n\u251c\u2500\u2500 DocumentEditor\n\u2502   \u251c\u2500\u2500 Toolbar (formatting options)\n\u2502   \u251c\u2500\u2500 EditorCanvas (the actual text area)\n\u2502   \u2514\u2500\u2500 CollaboratorCursors (real-time user positions)\n\u251c\u2500\u2500 Sidebar\n\u2502   \u251c\u2500\u2500 DocumentOutline\n\u2502   \u2514\u2500\u2500 CommentThread\n\u2514\u2500\u2500 Header\n    \u251c\u2500\u2500 AutoSaveIndicator\n    \u2514\u2500\u2500 ShareButton\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

Step 3: State management strategy (5 minutes)

\n\n\n\n

Step 4: Performance considerations (5 minutes)

\n\n\n\n

Step 5: Failure scenarios (5 minutes)

\n\n\n\n\n
\n\n

\n \n \n The Technical Questions That Still DO Get Asked\n

\n\n

Before you panic and throw away your technical prep \u2014 the fundamentals still matter. They're just the entry bar, not the differentiator.

\n\n

In 2026, hooks (useState, useEffect, useCallback, useMemo) are still the most common technical questions, followed by state management patterns, performance optimization, and practical coding challenges.

\n\n

Here's what you need to know cold:

\n\n

1. Custom Hooks
\n

\n\n
\n
// Can you build a useFetch hook from scratch?\nfunction useFetch(url) {\n  const [data, setData] = useState(null);\n  const [loading, setLoading] = useState(true);\n  const [error, setError] = useState(null);\n\n  useEffect(() => {\n    let cancelled = false; // Prevent state update on unmounted component\n\n    fetch(url)\n      .then(res => res.json())\n      .then(data => {\n        if (!cancelled) {\n          setData(data);\n          setLoading(false);\n        }\n      })\n      .catch(err => {\n        if (!cancelled) {\n          setError(err);\n          setLoading(false);\n        }\n      });\n\n    return () => { cancelled = true; }; // Cleanup\n  }, [url]);\n\n  return { data, loading, error };\n}\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

2. Performance Optimization
\n

\n\n
\n
// When to use React.memo, useMemo, useCallback?\n\n// React.memo \u2014 prevent component re-render\nconst ExpensiveComponent = React.memo(({ data }) => {\n  return <div>{data}</div>;\n});\n\n// useMemo \u2014 memoize expensive calculation\nconst sortedData = useMemo(() => {\n  return data.sort((a, b) => a.name.localeCompare(b.name));\n}, [data]);\n\n// useCallback \u2014 stable function reference for child components\nconst handleClick = useCallback(() => {\n  doSomething(id);\n}, [id]);\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

3. useReducer vs useState
\n

\n\n
\n
// useReducer for complex state logic\n// useState for simple independent values\n\n// \u2705 useReducer when:\n// - State has multiple sub-values\n// - Next state depends on previous state\n// - Complex state transitions\n\nconst [state, dispatch] = useReducer(reducer, initialState);\ndispatch({ type: 'INCREMENT', payload: 5 });\n
\n
\n
\n Enter fullscreen mode\n \n\n\n Exit fullscreen mode\n \n\n\n
\n
\n
\n\n\n\n

Class components won't be asked from scratch in 2026 \u2014 focus entirely on functional components and hooks.

\n\n\n
\n\n

\n \n \n My Interview Prep Framework (What I Use Now)\n

\n\n

After 3 failures, this is the system that got me offers:

\n\n

Week 1-2: Technical Foundation

\n\n\n\n

Week 3: System Design

\n\n\n\n

Week 4: Soft Skills + Behavioral

\n\n\n\n

Every Day:

\n\n\n\n\n
\n\n

\n \n \n The Mindset Shift That Changed Everything\n

\n\n

The biggest change wasn't technical. It was this realization:

\n\n

Interviewers are not trying to catch you. They're trying to see if they'd enjoy working with you.

\n\n

When you freeze on a question, the wrong response is silence. The right response is:

\n\n
\n

\"I haven't implemented this specific pattern before, but here's how I'd approach thinking through it...\"

\n
\n\n

That sentence alone changed my interview outcomes.

\n\n

Companies in 2026 are smaller. Teams are leaner. One difficult team member costs more than a skill gap that can be trained. They're hiring for someone who communicates clearly, thinks out loud, and handles uncertainty without shutting down.

\n\n

That's the real interview.

\n\n\n
\n\n

\n \n \n Wrapping Up\n

\n\n

If I could go back and tell myself one thing before those three failed interviews:

\n\n

Stop memorizing. Start reasoning.

\n\n

React knowledge is the ticket to the interview. How you think is what gets you the offer.

\n\n\n
\n\n

Have you noticed this shift in your own interviews? Or are you currently preparing for React interviews? Drop your experience in the comments \u2014 I'd love to hear what questions you're seeing in 2026! \ud83d\udc47

\n\n\n
\n\n

Heads up: AI helped me write this.But the ideas, personal experience, and learnings are all mine \u2014 AI just helped me communicate them better. I believe in being transparent about my process! \ud83d\ude0a

\n\n\n
\n\n", + "slug": "i-failed-3-react-interviews-before-i-understood-what-they-actually-want-in-2026", + "status": "approved" + }, + { + "title": "Preparing for My Amazon Front End Engineer Interview", + "original_url": "https://dev.to/spencerlepine/preparing-for-my-amazon-front-end-engineer-interview-5d0m", + "source": "dev.to", + "author": "Spencer Lepine", + "published_at": "2024-04-08T20:56:00Z", + "tags": "front", + "summary": "My experience and advice for the Amazon Front End Engineer interview.", + "formatted_content": "

\"Blog

\n\n

This article covers all the study material and advice that helped me ace my Amazon Front-End Engineer I (FEE) interview (November 2022, remote onsite). This is relevant to both the 60min phone interview and final round on-site. I\u2019ll break it down into two sections, technical and behavioral.

\n\n
\n

Note, if you\u2019re brand new to the FEE role, I\u2019d recommend skimming through this article first.

\n
\n\n

\n \n \n Interview Stages\n

\n\n

The initial 60-minute phone screen is typically more laid back, but still focused. It\u2019s an opportunity to talk about your background and motivation to work at Amazon. You\u2019ll want to be up to speed with LeetCode-style problems (mostly medium, rarely hard) and familiarized with the LPs (Leadership Principles).

\n\n

For the full on-site, I\u2019d recommend reviewing this entire article.

\n\n

Here\u2019s brief visual for the interview pipeline at Amazon:

\n\n

\"Amazon

\n\n

Amazon Interview Stages: Application \u2192 Online Assessment (OA) \u2192 Phone Screen (60min) \u2192 Onsite (4 rounds) \u2192 Team Matching

\n\n

\n \n \n Technical Skills & Coding Challenges\n

\n\n

You likely won\u2019t use an IDE during the interview, allowing you to focus on the concept/design, instead of wasting time on bugs. In my job-hunt experience, this style of using plain JS/CSS/HTML was unique to Amazon and I took some time to brush up on vanilla JS.

\n\n

Here\u2019s a breakdown of what I studied for the technical portion:

\n\n\n\n

For the online assessment (OA) and coding challenges, it\u2019s best to practice LeetCode style problems (medium difficulty, rarely high). When solving these problems, I briefly think about edge-cases/constraints, write all the psuedo-code, then attempt the problem. Don\u2019t hesitate to check in with the interviewer at checkpoints, asking if you\u2019re on track or they have any thoughts. Even if you don\u2019t solve 100% of the problem, an interviewer still values the progress you make.

\n\n

It\u2019s critical to verbalize your thought process while solving problem. Whether you are explaining your implementation, or thinking through the problem, the interviewer is assessing how you work through it. Avoid going silent if possible. I pretty awkward at this, so to practice I did talked through LeetCode problems in recorded mock Zoom meetings (like this video)

\n\n

For the on-site final round, you\u2019ll work on a frontend system-design question, which will be solved using vanilla JS, CSS, and HTML (including DOM API). Keep in mind that the difficulty level may vary based on your experience, potentially covering a broader scope than outlined in this article.. Note, this could vary based on your level of experience, so difficulty level could be a larger scope than this article. You may need to brush up on the DOM methods and syntax. I recommend building several small widgets to practice. Make sure you understand selectors, event listeners, and modifying styles with JS. If you are unsure what kinds of widgets I am talking about, look through\u00a0this\u00a0page.

\n\n

Make sure you understand frontend system design basic: component design, state management, performance optimizations, and APIs. To delve into this check out this\u00a0playlist\u00a0with TONS of detailed videos.

\n\n

\n \n \n Example Questions\n

\n\n\n\n

\n \n \n Resources\n

\n\n\n\n

\n \n \n Soft Skills & Behavioral Questions\n

\n\n

Each interview will include a behavioral question relating to one of the 16 LPs. You don\u2019t have to be an expert, but take some time to learn & familiarize yourself with them.

\n\n

My advice would be to prepare 1-2 stories per LP before the interview, as you will need to share concise answers on the spot. I\u2019d recommend jotting down keywords for each story to reference. These can be related to work experience, internships, school projects, personal projects, volunteering, extracurriculars, or any situation where you demonstrated leadership, problem-solving, or collaboration. It doesn't have to be strictly work-related.
\nTo tell a concise/structured story, you can use the STAR framework, or slightly adapt it. STAR helps to give clearer context and outcomes.

\n\n

An important theme is that technical skills can easily be taught, soft skills cannot. A valuable candidate has great personality and team collaboration skills.

\n\n

\n \n \n Example Questions\n

\n\n\n\n

\n \n \n Resources\n

\n\n\n\n

\n \n \n Additional Resources\n

\n\n

In no particular order, here\u2019s a list of more material I found useful:

\n\n\n\n
\n

\ud83d\ude80 Nail Your Tech Interviews with FAANG+ Experts. Get 20% off on Mock Interviews.

\nMock interviews and thorough feedback to help you land your dream tech role faster.

\nTrusted by over 25,000 experienced tech professionals.

\nStart Practicing Now

\n
\n\n

\n \n \n Conclusion\n

\n\n

TL;DR - practice LeetCode medium, brush up on vanilla JavaScript and CSS fundamentals, verbalize your thought process, prepare stories for each LP, and be confident.

\n\n

This covers just about everything I used to prepare for my FEE interview. Keep in mind, my interviews were fully remote, and this is biased to my experience for an entry level position.

\n\n

I hope you found this article useful! If you have any questions and would like to connect, you can find me over on LinkedIn or shoot me an email.

\n\n", + "slug": "preparing-for-my-amazon-front-end-engineer-interview", + "status": "approved" + }, + { + "title": "Interview Experience Digital Specialist Engineer - Infosys", + "original_url": "https://dev.to/vedantjain03/interview-experience-digital-specialist-engineer-infosys-4p4n", + "source": "dev.to", + "author": "vedant-jain03", + "published_at": "2022-05-16T16:39:34Z", + "tags": [ + "hackwithinfy", + "infosys", + "dse", + "interview" + ], + "summary": "What is HackWithInfy? HackWithInfy is a competitive coding competition for second-year to...", + "formatted_content": "

\n \n \n What is HackWithInfy?\n

\n\n

HackWithInfy is a competitive coding competition for second-year to pre-final year students across India. In this competition, participants have to solve coding questions in a given time and top performers get a chance to interview Infosys.
\nThe level of the competition was medium-hard. I solved 1 question and got AC and other 2 partially accepted. I did not remember the exact questions but they were mainly based on Arrays, Greedy and DP.

\n\n
\n

All questions can be solved partially with brute force, so will recommend you to solve every question.

\n
\n\n

If you solved 1 questions fully and some testcases for other 2, you will definitely going to get the interview for DSE role.
\nSo there were two roles Infosys was offering:

\n\n\n\n

If you are able to solve all 3, you will get upgraded to advanced rounds and will surely get the interview for SE.

\n\n

\n \n \n Interview Experience\n

\n\n

I got the mail on 3 May 2022 to schedule my interview and I scheduled nearest date possible 7th May. My interviewer forgot about the interview and hence he slept and get back to me after 2 hours. That was funny, XD. Never mind.
\nThe interviewer was really chilled and cool.

\n\n\n\n

We wrapped up and ask me for any doubts.

\n\n\n\n

\n \n \n Conclusion\n

\n\n

It is going to be very chill and easy, just be confident(not over).

\n\n", + "slug": "interview-experience-digital-specialist-engineer-infosys", + "status": "approved" + }, + { + "title": "My Interview Experience at MVI Technologies", + "original_url": "https://dev.to/sathish_226_/my-interview-experience-at-mvi-technologies-5gho", + "source": "dev.to", + "author": "Sathish A", + "published_at": "2025-10-17T18:10:50Z", + "tags": [ + "java", + "interview", + "programming", + "productivity" + ], + "summary": "Hello everyone, I want to share my small experience about my interview in MVI Technologies. That day...", + "formatted_content": "

Hello everyone,

\n\n

I want to share my small experience about my interview in MVI Technologies. That day was really awesome and I learn many new things.

\n\n

First I got one mail from MVI about my interview schedule. I was so happy that time. They give me 5 days time for prepare before interview day. So I start my preparation immediately.

\n\n

In that days I study Core Java, JDBC, Arrays, and String programs. I practice many examples and try to improve my logic. I was little nervous but I feel I prepare well.

\n\n

Then the interview day came. That day was really nice. They ask some good questions from file handling and collections. Some questions are mix with small task also, that was nice.

\n\n

But only problem is time not enough, only 1 hour. Some questions I see first time. I try my best.

\n\n

These are questions from the interview.

\n\n
\n

1.Task: Create a Java program that works with product data and calculates category-wise total sales.
\nRequirements:

\n\n
    \n
  1. Create a text file named products.txt programmatically.
    2. \n
  2. Write product details into the file. Each product has three fields:\nCategory (e.g., Phone, Stationery, Music)\nProduct Name,Product Price
    3. \n
  3. Category Details:\nThere should be 3 categories: Phone, Stationery, Music.\nEach category should have 3 products with their respective prices.\nExample: Phone,Samsung,15000
    4. \n
  4. Read the products.txt file and calculate the total price for each category.
    5. \n
  5. Create another text file named summary.txt and write category-wise totals into it.\nEach line should have the category name and total price.
    6. \n
\n
\n\n

Example:
\nPhone : 125000
\nStationery : 100
\nMusic : 14200

\n\n
\n

2.Task:
\nYou are given a string containing letters and digits. Write a program to reverse only the letters in the string while keeping the digits in their original positions.
\nRules:

\n\n
    \n
  1. Only alphabetic characters (a\u2013z, A\u2013Z) should be reversed.
    2. \n
  2. Digits (0\u20139) must remain at the same index as in the original string.
    3. \n
  3. No inbuilt methods like StringBuilder.reverse() should be used; solve it manually using arrays and loops.
    4. \n
\n
\n\n

Example:
\nInput: \"abcde1234fgh567ijk\"
\nOutput: \"kjihg1234fed567cba\"

\n\n
\n

3.Task:
\nWrite a Java program that performs the following tasks:

\n\n
    \n
  1. Create a file programmatically and allow the user to enter data.
    2. \n
  2. Store the user input in a Map with the following structure:\nKey: Long number\nValue: String word
    3. \n
  3. The user should enter at least 3 entries.\nValidation Conditions:\nCondition 1 (Number Key Validation):
    4. \n
  4. The number must be even.
    5. \n
  5. All digits of the number must also be even.\nExamples of valid numbers: 246864, 888222\nExamples of invalid numbers: 248678 (contains 7, 1, 3, etc.), 135792\nCondition 2 (String Value Validation):
    6. \n
  6. The word must have exactly 6 letters.
    7. \n
  7. The word must be a palindrome (reads the same forwards and backwards).\nExample valid words: madam, deeded (length must be exactly 6)\nIf both conditions are satisfied, store the number-word pair in the Map.
    8. \n
  8. After all entries are collected, write the valid data from the Map to another file.
    9. \n
\n
\n\n

Example Flow:
\nEnter number: 246864
\nEnter word: deified
\n--> Valid, added to map

\n\n

Enter number: 248678
\nEnter word: madamm
\n--> Invalid, not added

\n\n
\n

4.Task:
\nWrite a Java program that performs the following steps:

\n\n
    \n
  1. Get employee details from the user:\nEmployee ID (integer)\nEmployee Name (string)\nEmployee Salary (double)\n2.Store all the entered employees into an ArrayList as objects.\nCreate an Employee class with fields: id, name, and salary.\nGet input for at least 3 employees from the user.
    2. \n
  2. After storing data in ArrayList,\nTransfer all data into a LinkedList (one by one using loops \u2014 don\u2019t use foreach or streams).
    3. \n
  3. Then, programmatically create a file (e.g., employees.txt) and write all the employee details into the file.
    4. \n
  4. Use only basic collections and file handling \u2014\nNo Map, no Stream, no foreach.\nUse Iterate interface
    5. \n
\n
\n\n

I put all answers in my repo. If you want you can check my repo...

\n\n

[(https://gitlab.com/sathish226/java_exercise/-/tree/main/Java/src/mvi_Interview_Questions?ref_type=heads)]

\n\n

Thank you for reading my small experience.

\n\n

Keep learning and never give up!!!

\n\n", + "slug": "my-interview-experience-at-mvi-technologies", + "status": "approved" } ] \ No newline at end of file