Question pages for technical roles
Practice sessions you can rerun
Notes only when you choose to save them

Your real-time interview practice desk.

Keep a structured answer close while you rehearse. Algorithms, JavaScript, Python, Java, .NET, SQL, system design, and the story you want to tell about the role.

Try for free See how it works

No card is collected in this release.

Practice sessionsPrepare for practice calls and review past sessions.

+ Create session

Hash map screenInterview · 18 minLive
Rate limiter walkthroughMock · 32 minEnded
Event loop drillMock · ReadyReady

Question bank

Browse the questions candidates are asked, grouped by subject, with the points worth saying out loud.

Learn more

Mock interviews

Practice one current question, then read the note back. Your first mock on this desk is open.

Learn more

Resume studio

Build a one-page resume for the role you are chasing, so the practice starts from the right story.

Learn more

Session desk

Name a session, keep the role beside it, and decide later whether the notes are saved.

Learn more

Everything you need, mid-practice.

Code, notes, and an answer you can defend, while the rehearsal is still going.

Programming

Full coding notes

A coding question includes the approach, a sample, and the case you would mention before the interviewer asks.

Learn more

key: api token, plus a coarse IP limit
store: shared counter, atomic increment
burst: token bucket
limit hit: 429 and Retry-After
cache down: fail closed on writes

A transcript you can turn off

Practice notes exist so you can review. If you end a session with saving off, the words are not the thing you keep.

Answers with a source

Each published answer names the decision. When the model API is connected, generated notes will have to stay inside your resume and documents.

Your notes stay a choice.

Real-time practice without a saved transcript unless you ask for one. The desk is yours. It is not advertised as invisible on a shared screen.

01Saving is optional
A session can record the title and timing without the transcript.
02This browser first
The practice profile, progress, and resume draft live locally until the API ships.
03Delete is local today
Clear the profile from sign-out. Session rows you add leave when you refresh.
04No sale of notes
Study text is not a product we sell to recruiters.
05Follow the room
If the employer forbids help, the rule wins. We will honor a blacklist request.

See the privacy page

Built around real interview moments

These are the situations the studio is written for, not quotes from a user base we do not have yet.

45 minutes, one public API

A system design screen

You open the rate-limiter question the night before, write the key and the failure mode in your own words, then rerun the mock until the 429 response is part of the story and not an afterthought.

One problem, your language

A coding round

You open the hash-map question, write the complexity in the language the role uses, and say when a nested loop is still fine. The same desk holds algorithms, JavaScript, Python, Java, C#, SQL, and system design.

One disagreement, told once

A behavioral round

The behavioral prompt keeps you on the decision and the result. You trim the story until it fits two minutes and still names the risk you were protecting.

Before, during, and after practice

Set the roleCompany, title, and the kind of session: interview, mock, or a quiet reread.
Bring the resumeThe studio should not invent projects that are not on the page you wrote.
Keep one question currentFollow-ups belong to the same question until you answer it.
Review the noteMark the question learning, practiced, or confident.
Run it againA mock is useful the second time, when the tradeoff is shorter.

Plans you can read before you pay

Monthly and yearly practice plans are listed in rupees. Nothing is charged from this screen.

See pricing

Start with a topic

All topics

Every technical screen

Algorithms

Complexity, data structures, and the tradeoff you would name before you write the loop.

Open topic

Frontend and full-stack engineers

JavaScript

The event loop, promises, and the browser behavior interviewers ask you to trace.

Open topic

Backend, data, and automation roles

Python

The runtime, concurrency, and the data-model choices that show up in Python loops.

Open topic

Backend and platform engineers

Java

Collections, equality, and the concurrency story you can defend on a whiteboard.

Open topic

Backend and full-stack engineers

C# and .NET

Language behavior, async work, and the runtime choices interviewers expect you to defend.

Open topic

API and platform engineers

ASP.NET Core

Request pipeline, dependency injection, APIs, and how you keep a service observable.

Open topic

Frontend engineers

Angular

Change detection, signals, routing, and server rendering for interview-sized examples.

Open topic

Engineers who own data access

SQL and data

Indexes, isolation, and the query plan you would actually ask for in a review.

Open topic

Mid-level and senior candidates

System design

Capacity, failure, and the tradeoff you would write on the board first.

Open topic

Every interview loop

Behavioral

Short stories with a decision, a result, and the part you would do differently.

Open topic

Questions to open first

Search the bank

Algorithmsfoundation

When does a hash map beat a nested loop?

Name the time and space tradeoff, then say when the nested loop is still the right answer.

JavaScriptworking

How does the JavaScript event loop order a promise and a timeout?

Trace the call stack, then microtasks, then the next macrotask.

System designsenior

How would you design a rate limiter for a public API?

Choose the key, the algorithm, and what the client sees when it is limited.

SQL and datafoundation

Why does a function on a column stop an index from helping?

Define sargable predicates and the index you would add for a real filter.

Common questions

What is Prep Desk for?

Prep Desk is a study studio for technical interviews across stacks. You read a question, practice the answer out loud, keep a mock session, and shape a resume around the role. It is for preparation you are allowed to do: self-study, mock calls, and notes you choose to save.

Do I need an account to read the questions?

No. Topic and question pages are public. Create a free account with your name, email, phone, password, and country when you want one. Sign-in uses a JWT. Progress marks still stay in this browser.

Does the question bank include coding questions?

Yes. Coding pages include the approach, a short sample, and the tradeoff worth saying out loud. They are study notes, not a hidden window for a live proctored test.

Are practice transcripts saved?

Only when you leave saving on. In this UI release, session notes stay in the browser. When the API is connected, a session will be able to discard the transcript and still keep the title, role, and timing.

Which subjects are on the site today?

Technical interviews, not one stack. The bank covers algorithms, JavaScript, Python, Java, C# and .NET, ASP.NET Core, Angular, SQL, system design, and behavioral rounds. Each subject has its own page, and each question has a stable URL.

Read every question

Ready to answer every question?

Open the bank, or create a practice profile that stays in this browser.

Try for free