Contribute an Interview Experience That Gets Approved
Every interview experience on CodinzHub was written by a student who went through the process. A good write-up helps the next batch and earns you coins; a vague one gets sent back. This guide shows the exact structure that gets approved, the rewards for each tier, and the mistakes that slow review down.
On this page
Every interview experience on CodinzHub was written by a student who went through the process. A good write-up helps the next batch and earns you coins; a vague one gets sent back. This guide shows the exact structure that gets approved, the rewards for each tier, and the mistakes that slow review down.
In this guide
- Standard vs detailed experience rewards
- The round-by-round structure reviewers expect
- Why approved write-ups also feed the Premium placement data
What you can earn
| Type | Reward |
|---|---|
| Standard interview experience | 50 coins once approved |
| Detailed experience: full OA process, round-by-round breakdown, questions asked, selection process and final result | A higher configured coin amount |
The structure that gets approved
Write in this order. Reviewers check each section, so a missing one is the usual reason an experience sits in review.
- Basics: company, role (for example SDE or intern, with PPO if it applied), your college, and whether the drive was on-campus or off-campus
- Online assessment: sections, duration, number of coding and MCQ questions, platform name if you remember it, and difficulty
- Each interview round: what was asked, how you approached it, what the interviewer pushed on, and where you got stuck
- HR / Googliness-style round: the questions and how the conversation went
- Result: selected or not, plus what you would do differently
Formatting tip: keep the question text as close to what you were given as possible. Paraphrasing the problem statement is the single most common reason a write-up is less useful than it could be.
What separates a standard write-up from a detailed one
A standard experience names the rounds and topics. A detailed one lets a reader rebuild the paper: exact question wording, input constraints, follow-ups, the approach you used, complexity, and the edge cases that broke your first solution. It also records the small process facts nobody blogs about — how long the recruiter took, whether the code went into a shared doc, whether you were allowed to run it.
Mistakes that slow review down
- Describing only the topic ("a graph question") instead of the problem
- Skipping follow-ups — they reveal what interviewers actually care about
- Cleaning up the story so much that the failure disappears; a failed round teaches more than a perfect recap
- Sharing anything covered by an NDA, or pasting a company's internal document
Why your write-up matters beyond coins
Approved experiences feed the company pages and the placement layer on the Premium page, where college-wise CTC data, CGPA cutoffs and PYQs are kept free for everyone. One honest, detailed submission can improve three different pages at once.
Where to submit, and what to read next
Submit from the Contribute page. Before you write, skim Reading OA Formats so your OA section uses the same vocabulary as other reports, and How CodinzHub Works for how coins land in your balance. Aiming at a specific company? Compare your draft against its company page first.
Related: CodinzHub Premium explained · Using the Requests page · Explore CodinzHub
Keep track of what you’ve learned.