Interview Experience Contributions
Real interview reports from students — company names, round types, questions asked, and honest outcomes.
Why This Section Exists
- Syllabus prep doesn’t tell you what Infosys Round 2 actually feels like
- Knowing others got stumped on
useEffectdeps helps you prioritize - “Selected” and “rejected” experiences both teach something
How to Contribute
- Copy experience-template.md
- Create a new file:
experiences/company-role-year.md(folder optional) - Fill in every section honestly — redact personal info if needed
- Open a PR or share with your placement cell
Anonymize if needed: “Mid-size Bangalore startup” is fine instead of exact company name.
What Makes a Good Experience Write-up
| Good | Not helpful |
|---|---|
| Exact question phrasing | ”They asked JS questions” |
| What follow-ups came after | ”It was hard” |
| What you wish you’d prepared | Only outcome bragging |
| Difficulty rating with reason | Copy-paste question dumps with no context |
| Honest result + learnings | Fake or exaggerated stories |
How to Use Others’ Experiences
- Search by round type — filtering React-heavy startups vs DSA-heavy service companies
- Collect recurring questions — if 5 people got
event loop, study it - Calibrate difficulty — “Medium” at one company may match your “Hard”
- Don’t memorize company-specific answers — patterns transfer; exact questions rarely repeat
Experience Index
No contributions yet — yours can be the first.
| Company | Role | Rounds | Difficulty | Result | File |
|---|---|---|---|---|---|
| — | — | — | — | — | Add yours |
Privacy & Ethics
- Don’t share proprietary coding questions from ongoing hiring drives
- Don’t name interviewers
- Don’t share internal company tools or credentials
- Do share question patterns and your preparation advice
Related
- Mock practice: 10-mock-interview-kits
- Question patterns: 11-interview-patterns
- Contributing guide: CONTRIBUTING.md
Your rejection story might save someone else’s month of wrong prep. Contribute.