# Run an interview-coaching business, not a quiz widget *Assessment* For coaches, placement cells and bootcamps who put candidates in front of real interviewers. Question banks, timed mocks that grade themselves, a real code sandbox, live interviews with shared notes, and a written report at the end. Try it on Jversity: https://jversity.com/services/interview-prep ## Who it is for - An interview coach running structured programmes rather than ad-hoc calls - A college placement cell preparing a cohort for recruitment season - A bootcamp that promises mock interviews as part of the course ## What it does ### A question bank you build once Nine question types, including coding and SQL, assembled into rounds and reused across every programme you run. - Nine question types, aptitude through open-ended - Coding and SQL questions with real execution - Rounds assembled from the bank and reused - Difficulty and topic tagging for targeted drills ### Mocks that grade themselves A timed mock test returns a score the moment it is submitted, so a candidate is not waiting on you to find out how they did. - Timed tests with automatic submission - Objective, coding and SQL answers graded on submission - Code executed in a sandbox, not pattern-matched against an answer key - Attempt history a candidate can see and compare ### The live interview Join the session, ask your questions, and take notes stamped to the moment they were made. More than one interviewer can write at the same time. - Live interview sessions with the candidate - Timestamped notes from multiple interviewers - Session playback afterwards - Peer interviews between candidates ### What to practise next Weak-area analysis reads every attempt a candidate has made and points the next drill at what it finds, so practice is aimed rather than repeated. - Weak-area analysis across all attempts - Drills targeted at the areas it identifies - Résumé review as part of the programme - Progress visible to the candidate and to you ### The report Scores, weak areas and your notes come together into one report per candidate, published when you decide it is ready. - One report per candidate - Scores, weak areas and interviewer notes in one place - You control when it is published - Kept with the candidate's record ## How it is used 1. **Build the programme** — Assemble rounds from your question bank: aptitude, technical, coding, SQL or open questions. 2. **Candidates enrol and practise** — Timed mocks grade themselves on submission, so candidates get a score without waiting on you. 3. **You run the interview** — Join the live session, ask your questions and take timestamped notes. Everything around the interview is already handled. 4. **The report goes out** — Scores, weak areas and your notes become one report per candidate, published when you say so. ## How it is built - **Code is run, not compared** — A candidate's solution executes in a real sandbox and is judged by whether it works, which is the only judgement worth reporting. - **Notes are timestamped and multi-author** — A panel can write at once and the notes stay anchored to the moment in the session they refer to, so a debrief has something to point at. - **Weak areas come from attempts, not opinions** — The analysis is computed across everything a candidate has actually submitted, so the drill it recommends is evidence rather than a hunch. ## Questions we get asked ### Is the coding question really executed? Yes. Candidate code runs in a sandbox and is graded on whether it works, not on whether it resembles a stored answer. ### Can several interviewers take notes at once? Yes, and every note is stamped with the moment in the session it was written, so the debrief has an anchor. ### Who decides when a candidate sees their report? You do. The report is assembled automatically but published only when you choose.