Connect your coding profile, choose your target, and we’ll map what you already know against the skills you actually need.
1
Your profile
2
Skill analysis
3
Company + role
4
Personalized plan
GitHub LeetCode Frontend System Design JavaScript React TypeScript
Target
Experience
Target company
Your target
Google · Frontend Engineer
3-5 years
Coding profiles · optional
LeetCode
Coding practice profile
Your username goes to our server, which reads your public solved counts from LeetCode. The results are kept in your browser, and in your account if you sign in.
GitHub
Analyze your public repositories & activity
Reads only your PUBLIC profile & repos, with no token. Kept in your browser, and in your account if you sign in.
What we’ll build for you
JavaScript
React
TypeScript
Browser / Web
System Design
Machine Coding
DSA
Preview — your actual gaps are calculated after setup, from the curated question bank and your progress. Not a measured score.
Company relevance is evidence-labelled (Curated / Reported / Suggested). We never claim a question was asked at a specific company, and never fabricate stats.
Tell us the company, role and interview date, optionally connect your engineering activity, and get a focused preparation workspace — not another question dump. Every company-relevant question carries an evidence label, never a fabricated “asked at” claim.
How the frontend interview prep works
From a target to a daily plan:
Pick your company (Google, Meta, Amazon…), role and interview date.
Optionally add your GitHub username and LeetCode solved counts to sharpen recommendations.
See per-area coverage across JavaScript, React, system design, machine coding, DSA and more.
Practice questions and cycle their status (practiced → solved → needs revision).
Follow the daily focus and gap analysis, and design systems in the interactive System Design tool.
Practise coding drills in the Play tab: the daily challenge, Output rush and the drill library.
Why use it
Personalized, not generic. A workspace built around one company + role + date, with gap analysis on your actual progress.
Honest by design. Evidence labels (Curated / Reported / Suggested) — no fake frequencies, no invented company questions.
Private. Progress lives in your browser, with no account needed. Sign in only if you want your plan and mock interviews synced (Play stays on this device); the mock interviewer’s optional AI feedback sends your answers to our server.
Real system design. System-design tracks open the interactive HLD/Service/LLD workspace — you design and explain the architecture.
Frequently asked questions
How is this different from LeetCode?+
LeetCode is a question set. This is a personalized preparation workspace: you tell us the company, role and date, and we turn the curated question bank into tracks (JavaScript, React, HTML/CSS, Browser, DSA, machine coding, frontend system design, performance, accessibility, security, behavioral) with progress tracking, gap analysis and a daily focus. Your GitHub/LeetCode profile is an optional data source, not the product.
Do you claim these questions were “asked at Google”?+
No. Every question carries an evidence label — Curated, Reported, Observed or Suggested — and a company relevance tag, never a claim that a specific company asked it. We do not fabricate frequency percentages.
Is my progress private?+
Yes. Your plan and progress are stored in your browser, with no account needed; clearing your browser data resets them. If you sign in, your plan, target company and role, question progress, mock interviews, code-judge submissions and the LeetCode and GitHub figures you connect also sync to your account so they follow you between devices; the Play tab’s progress does not. The mock interviewer’s optional AI feedback and the code judge send your answers and code to our server, and a connected LeetCode username is looked up server-side.
Does it connect to my GitHub or LeetCode?+
Yes — both are optional, first-class connections. GitHub reads only your public profile and repositories, with no token, to personalize recommendations; signed in, those figures are saved to your account. LeetCode imports your public solved counts server-side; if that is unavailable you can enter your counts manually. We only use what you connect, never store secrets, and you can prepare fully without connecting anything.
Can I practice frontend system design here?+
Yes — system-design questions deep-link into the existing interactive System Design tool (HLD/Service/LLD, request flows, failure and scale analysis), so you design and explain the architecture in the real workspace.
What are the coding drills?+
145 short JavaScript exercises of three kinds: 80 Predict the output (read a snippet and choose what it prints), 35 Implement it (write a function from a prompt) and 30 Find the bug (fix code so its tests pass). Each has a topic, such as closures, the event loop or promises, and a level: easy, medium or hard. You answer Predict the output drills in the Play tab; Implement it and Find the bug open in the practice editor.
How are the answers checked?+
Nobody writes a Predict the output answer by hand. Each snippet was run in Node and in Chrome, and the answer is the option that matches what it printed in both; a drill is offered only while its content is unchanged since that run. Implement it and Find the bug drills are checked by running their tests in your browser, in a sandboxed Web Worker (timer drills use a fake clock), so your drill code is not sent to our server. Each of those drills was also checked against a reference solution and deliberately wrong versions, so its tests are known to catch mistakes. The mock interview is different: there, the code judge sends your code to our server when it is available, and the optional AI feedback sends your answers and code to an AI provider.
What is the Play tab?+
A place to practise the drills. Each day there is a daily challenge (3 Predict the output drills and 1 Implement it or Find the bug drill, the same all day). You earn XP for the first correct solve of each drill, for finishing the daily challenge and in Output rush (1 XP per right answer in your first 2 rounds each day, at most 30 a round), and you can level up, keep a streak of days with a finished challenge, and collect 9 badges. There is a drill library by type, topic and level, and Output rush: easy and medium Predict the output drills one after another, one try each, in a 60-second or untimed round, with a combo of ×1.5 from the 4th right answer in a row and ×2 from the 7th.
Where is my Play progress kept?+
On this device only. XP, levels, the streak, badges, your Output rush best and your drill results are saved in this browser, separately for each account you use here, and are never synced to your account or sent to our server. Clearing this site’s data from your browser resets them.
Do the drills change my plan or the Review queue?+
No. Drills are kept apart from the question bank: solving or missing a drill does not change your plan, your question progress, the gap analysis or the Review queue, which only schedules questions from the bank.
Do the drills need an account or use AI?+
Neither. The drills, the practice editor and the Play tab work without signing in, and none of them calls AI.