**1400** (6.66%) - You can solve a handful of easy problems, as well as an occasional medium one. For the problems you are able to solve, you often use brute-force. Understanding of DSA remains basic such as the manipulation of arrays and strings.**1500** (15.09%) - This is where everyone starts with, assuming no contest participation. As a regular participant, you can solve many easy problems as well as few mediums. You can solve these problems using the brute-force method, but often have difficulty optimizing the solution.**1600** (27.35%) - You can solve most easy problems at ease as well as some mediums. You have at least a basic understanding of DSA as well as few other tools to help you solve such problems. However, your DSA toolbox is relatively smaller compared to other frequent participants.**1750** (49.98%) - You can solve easy problems as well as big chunk of medium ones. For some problems, you may think of multiple approaches, including the optimal ones. You have an decently-sized DSA toolbox that helps you identify what you should use for many problems you can solve.**1850** (63.77%) - It is not uncommon for frequent participants to get this far with their shiny Knight badge! You can solve many medium LeetCode problems as well as a few hard ones. Since hard problems often involve graphs, DP, trees, and other hard algorithms, you will need to be accustomed to harder problems (or solve nearly all mediums) to reach this rating . At this point, you are mostly interview ready!**2000** (79.98%) - You can solve most LeetCode problems, even some harder ones. You can write up with multiple solutions, including the optimal ones. Your DSA toolbox is significantly larger compared to others that your understanding of DSA is advanced at this point.**2200** (91.19%) - If you get this far, you will earn the Guardian badge. You can solve most LeetCode problems including many hard ones due to your advanced understanding of DSA.**2500** (97.63%) - You have expert-level understanding of DSA, and can solve nearly any LeetCode problem you can think of. While it is extremely impressive to have this rating, interviewers will also gauge your communication skills as well. If you want another challenge, then practice thinking out loud while solving LeetCode problems!I know that the percentages I put next to contest ratings may be interpreted as "comparing to others", however, it doesn't have to be that way. Back in July, I had a contest rating as low as 1350 (4.09%), but I don't let that stop me from participating. The way to improve yourself is to take small steps towards your contest rating improvement. For instance, you have a 1400 contest rating, and you want to be a Guardian, right? It doesn't take just one contest or two to do that. It will take many, many contests to see significant results. So if you want to see improvement from your 1400 rating, why not try reaching for a 1500 contest rating? Or if you already have a 1500 contest rating, try reaching for 1600.By the way, here is the contest rating graph that is generated from the clist.by website:Download App](https://leetcode.com/app/?utm_campaign=AppPromotion&utm_medium=site&utm_source=site_footer&gio_link_id=nPN4bXe9)
↓
Code · Fields · Cost ·
Run it keyless, no account
The same call, in code.
The capture above came back as markdown. These examples add a key, so you get browser rendering, proxies, and concurrency on leetcode.com.
leetcode-scraper.ts
import { SpiderBrowser } from "spider-browser";const spider = new SpiderBrowser({ apiKey: process.env.SPIDER_API_KEY!,});await spider.connect();const page = spider.page!;await page.goto("https://leetcode.com/problemset/");// No selectors, no schema. Spider reads the page and names the fields.const data = await page.scrape();console.log(data);await spider.close();
import { SpiderBrowser } from "spider-browser";const spider = new SpiderBrowser({ apiKey: process.env.SPIDER_API_KEY!, stealth: 2,});await spider.connect();const page = spider.page!;await page.goto("https://leetcode.com/problemset/");await page.content(12000);const data = await page.evaluate(`(() => { const problems = []; document.querySelectorAll("[role='row']").forEach(el => { const title = el.querySelector("a[href*='/problems/']")?.textContent?.trim(); const difficulty = el.querySelector("[class*='difficulty']")?.textContent?.trim(); const acceptance = el.querySelector("[class*='acceptance']")?.textContent?.trim(); const link = el.querySelector("a[href*='/problems/']")?.getAttribute("href"); if (title) problems.push({ title, difficulty, acceptance, link }); }); return JSON.stringify({ total: problems.length, problems: problems.slice(0, 20) });})()`);console.log(JSON.parse(data));await spider.close();
Problem titleDifficultyAcceptance rateTagsDescriptionLikesCompaniesSubmissions
Spider names these from the page. The capture above came back as markdown; the same
call with return_format: "json" returns them as keys.
What leetcode.com costs to scrape.
The capture above cost $0.000312 to fetch. Pricing is $1 per GB of pre-transformation bandwidth plus $0.001 per CPU minute, so a page like this one lands at a fraction of a cent. Failed requests are billed at $0.
You already have the call. A key raises the rate limit and turns on browser rendering,
proxies, and concurrency. Balance never expires, and top-ups go through secure checkout.