Interview-Questions-Collection

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

πŸ“š Interview Questions Collection

This repository contains a curated collection of interview questions categorized by company, position, technology stack, and hiring location. Each entry also contains details about the interview rounds, types, and interviewer names.


πŸ“Œ Table of Contents


βœ… How to Use

Each interview entry follows the format:

Company Name Position Technology Stack Location

Then each round of the interview is listed in order, including the type of interview and the interviewer’s full name.


πŸ“„ Interview Entries

🏒 Amazon | Backend Engineer | Java, AWS, Microservices | Bangalore

Round 1 – Online Coding Test
πŸ‘€ Interviewer: Automated Platform

Round 2 – Virtual Technical Interview
πŸ‘€ Interviewer: John Smith

Round 3 – System Design Interview (Virtual)
πŸ‘€ Interviewer: Jane Doe


🏒 Google | Frontend Engineer | React, TypeScript | Hyderabad

Round 1 – Virtual Coding Round
πŸ‘€ Interviewer: Rajeev Mehta

Round 2 – Technical Deep Dive (F2F)
πŸ‘€ Interviewer: Ananya Verma

Round 3 – Hiring Manager Round (Virtual)
πŸ‘€ Interviewer: Kunal Patel


🀝 Contribution Guidelines

If you’d like to add your own experience:

  1. Follow the format shown above.
  2. Ensure interviewer names and details are accurate.
  3. Use markdown syntax for clarity and formatting.

πŸ“¬ For any suggestions or improvements, feel free to open an issue or pull request.