Write once, interview with it forever.

Build a library of problems with starter files, visible tests the candidate can run, hidden tests only the interviewer sees, and a scoring rubric. Attach a problem to any workspace in one step.

Start free See pricing

Screenshot coming soon

Use cases

When this feature earns its keep.

Three concrete patterns. Use them as templates for your own setup.

Run the same LRU cache problem across 30 candidates consistently

Attach the problem to each workspace. Every candidate starts with the same file tree and the same visible test cases. Hidden tests score consistently without manual grading.

Let candidates see some tests but not all

Visible tests help the candidate check their own progress. Hidden tests let you score correctness on edge cases the candidate has not seen. Both run in the same execution step.

Standardize rubrics across your interview panel

Attach a rubric (correctness, complexity, communication, code quality) to the problem. Every interviewer who uses that problem scores against the same criteria, which makes calibration discussions concrete.

Setup

How the setup looks.

Problems live in the Manage library surface, accessible from the org dashboard. Creating a problem takes about five minutes.

Same workspace, same auth, same collaboration features as every other Typelets workspace. See all features

Open Manage library from the dashboard
Click the Library link in the left sidebar of your org dashboard. The library lists all problems your org has created, plus any Typelets-provided starter problems.
Create a new problem
Click New problem, give it a title and prompt, and upload or paste the starter files. The file tree editor works the same way as the workspace editor.
Add visible and hidden tests
Visible tests appear in the candidate editor and can be run at any time. Hidden tests run when the interviewer triggers a scored run. Add at least one hidden test so the automated score means something.
Attach the problem to a workspace
When creating a workspace (or from workspace settings), select a problem from the library. The starter files are copied into the workspace and the rubric and tests come along automatically.

FAQ

Can I bring my own problems?: Yes. The library is yours to fill. Create as many problems as you need with your own prompts, file trees, and tests. Typelets-provided starter problems are available as a starting point but are not required.
What languages can my problems use?: Any language supported by the runtimes: Python 3, Ruby 3.3, JavaScript (Node), TypeScript (tsx), Go, Java 17, C, and C++. A problem is language-specific; the starter files and test runner are written for one runtime.
Can multiple people on my team manage the library?: Any org admin can create, edit, and delete problems. Org members with the interviewer role can attach problems to workspaces but cannot edit the library. This separation keeps the canonical problem set stable.
What happens to a workspace if I edit the problem it uses?: Workspaces snapshot the problem at attach time. Editing the problem in the library does not change existing workspaces. New workspaces attached to the problem pick up the updated version.

Write once, interview with it forever.

When this feature earns its keep.

Run the same LRU cache problem across 30 candidates consistently

Let candidates see some tests but not all

Standardize rubrics across your interview panel

How the setup looks.

Open Manage library from the dashboard

Create a new problem

Add visible and hidden tests

Attach the problem to a workspace

FAQ

Start interviewing in under a minute.