Skip to content
Interview Questions

What to Send in an Interview Experience

Candidate reports make company pages useful when they are specific, recent, and privacy-safe. This page explains what to send if you want your interview experience considered for interviewquestions.app.

Send submissions to anchal@kasp.ae via Contact. How we review and update content is described on Editorial process.

Key takeaways

  • Include role, year/month, campus vs off-campus, and round-by-round notes.
  • Describe question themes and your approach; do not paste proprietary test PDFs.
  • Strip names of interviewers, peers, and internal tool URLs that are not public.
  • Say whether you were selected, rejected, or waiting.
  • Short and accurate beats long and vague.

Why your report helps

Readers use experiences as process maps (see How to read an interview experience). A clear 2026 campus report for TCS or Amazon helps someone prep the right round shape. A vague “it was hard but I cleared” helps no one.

Email subject line

Use a predictable subject:

Interview experience: <Company> · <Role> · <Month Year> · <Campus/Off-campus>

Examples:

  • Interview experience: Infosys · SES · Aug 2026 · Campus
  • Interview experience: Google · SWE L3 · Jan 2026 · Off-campus

Template to copy

Company:
Role / level (intern, FTE, L3, Digital, etc.):
Location preference discussed (optional):
Month and year of interviews:
Campus / off-campus / referral:
College tier note (optional, e.g. Tier-1 campus drive):
Outcome: selected / rejected / on hold / offer accepted elsewhere:


Round-by-round:
1) Name of round · duration · mode (call, meet, onsite, HackerRank)
   - What was asked (themes + 1-2 example prompts if you remember)
   - What went well / poorly
2) ...


OA / online test (if any):
- Sections and rough difficulty
- Time limit
- Do not attach proprietary question papers


HR / behavioural:
- Prompts (why company, location, projects, LP/Googleyness themes)
- Anything surprising


Prep that helped:
- 3 bullets


Advice for next candidates:
- 3 bullets


Permission:
- Publish anonymously: yes/no
- Credit name/handle if yes: ________
- Okay to edit for clarity: yes/no

What good detail looks like

Useful

  • “Two coding rounds on shared Doc, ~45 min each; first was array/hashing, second was tree recursion with follow-ups on complexity.”
  • “HR asked about bond/location and one conflict story; managerial asked about a production bug in internship.”
  • “NQT done in June; interview mid-July; technical focused on OOP + project.”

Less useful

  • “DSA round was LeetCode medium.”
  • “HR was chill.”
  • Entire chat transcripts with interviewer names.

Privacy and safety rules

Do not include:

  • Interviewer full names, personal emails, or phone numbers
  • Peer candidate names
  • Internal dashboards, unlisted Meet links, or access credentials
  • Offer letters, CTC screenshots, or government IDs
  • Exact proprietary assessment PDFs or copyrighted question banks

You may include:

  • Public question themes
  • Your own paraphrased prompts
  • Approximate CTC bands if you want them discussed at a high level (we may generalize)
  • Public links you already shared yourself (LinkedIn post, etc.)

If you are unsure, omit it. We would rather ask a follow-up than publish something unsafe.

How we use submissions

Under the editorial process:

  1. We check clarity, recency, and whether the report conflicts with known process shape.
  2. We edit for grammar, structure, and anonymization.
  3. We may merge details into an existing company interview experience style page rather than publishing a raw email.
  4. We may decline reports that are too thin, unverifiable in risky ways, or primarily promotional.

Sending a report does not guarantee publication or a reply timeline during peak hiring months, but concrete templates get reviewed faster.

If your report is for one of these, skim the current page first so you can note what changed:

OA-oriented material still belongs primarily on placementpapers.app; you can mention OA structure briefly here and point readers there.