5 steps~15 minutes to startNo setup required

Studio Usage Guide

Everything you need to go from a blank editor to a verified solution: how the workspace is laid out, what Run and Submit actually do, how to read a verdict, and how to study without outsourcing the thinking.

Technical Guides, Intermediate Projects & Course Recommendations

Pair your studio practice with our in-depth engineering articles covering the most asked Python interview questions, intermediate level portfolio project ideas, and top Udemy/Coursera courses and books.

Five steps to your first verdict

01

Pick a module

Start with Module 1 if you are new. Each module groups 20 progressive problems around one problem family, from easy to hard.

02

Read before you code

Read the description, constraints and visible examples. Write down your approach and complexity in plain words before touching the editor.

03

Solve in the editor

Write Python in the built-in editor. Press Run to execute example tests locally in your browser; iteration is instant.

04

Submit to the judge

Sign in and press Submit. Your code is evaluated on the server against hidden boundary tests. Hidden inputs never reach your browser.

05

Use the feedback

Read the verdict and the failure summary. Ask the AI coach about the error or complexity — not for the answer. Then revise and submit again.

Getting to know the workspace

Problem panel

Description, constraints, example tests and follow-up questions. Read the constraints twice; most wrong answers come from a missed boundary, not from a weak algorithm.

Editor

A real Python editor with syntax highlighting. Starter code defines the expected function signature — keep the name and parameters intact.

Run vs. Submit

Run uses visible example tests in your browser and needs no account. Submit sends the code to the server for hidden-test judging and requires sign-in.

AI coach

Ask why something fails, how to reason about complexity, or for a hint about the approach. It will not reveal hidden tests or write the complete solution for you.

A four-week study plan

This is a starting point, not a rule. Adapt the pace to your schedule; consistency beats intensity.

Week 1 — Foundations

Modules 1–2. One or two problems per day, no timer. Focus on reading constraints and writing complexity notes.

Week 2 — Core patterns

Modules 3–5. Alternate easy and medium problems. Review every wrong answer the next day before starting a new one.

Week 3 — Depth

Modules 6–8. Start timing yourself. Explain each solution out loud as if an interviewer were listening.

Week 4 — Mixed review

Modules 9–10 and a mixed set from weak topics. Re-solve three problems you failed earlier without looking at notes.

What you get

Six habits that actually move the needle

  • Spend at least 15 minutes alone with a problem before asking for a hint.
  • Treat examples as a specification, not as the full test suite.
  • Write down the time and space complexity before you submit.
  • Ask the AI coach why, not what. Explanation builds intuition; copied answers do not.
  • Keep a list of failed problems and re-solve them a day later.
  • Use a timer only after your approach is correct, to practice delivery.

Frequently asked questions

Do I need an account to use the studio?

You can open problems and run example tests in your browser without signing in. Submitting a solution, saving progress and using the AI coach require an account.

Where does my code actually run?

Run executes in your browser. Submit runs on the server against hidden tests. The workspace labels both actions so the difference is always visible.

Is the catalog free?

Yes. All 200 problems are free, including the browser editor, example tests and server-side judging.

Is my progress saved?

Yes. Each submission — accepted or not — is recorded in your account so you can revisit problems, see what you solved and return to weak topics.

Can I use the studio on a phone?

The site is responsive, but solving algorithmic problems is significantly more comfortable on a desktop or laptop with a physical keyboard.

I am stuck on a problem. What should I do?

Re-read the constraints, run the smallest possible example, ask the coach for a hint about the approach, and only then inspect the solution notes. Return to the same problem after 24 hours and solve it from scratch.

Ready to start?

Open the first free problem, read the constraints, and give yourself fifteen minutes before asking anyone — including the coach.

Open problem K01Read the methodology