
How to Write a Resume That Gets Past ATS Software
A practical, non-gimmick guide on structuring your technical resume so Applicant Tracking Systems can parse your skills, dates, and experience accurately.
Every calculator, converter, and the resume builder runs entirely in your browser. I never see your numbers or your resume text — there's no server call to send them to. No sign-up, because I didn't want to build another login you'd have to remember. No upload, because your salary slip has no business sitting in a database somewhere.
The ones people click on the most.
Pick a template, fill in the boxes, export a clean PDF. No watermark, no "upgrade to remove watermark" upsell — I refuse to build that pattern.
Plug in a monthly SIP amount and see what it actually becomes over 10, 20, 30 years — with annual step-up, because nobody keeps investing the same fixed amount forever.
Paste ugly JSON, get readable JSON back. If it doesn’t parse, it tells you exactly which line broke.
Daily, monthly, or yearly compounding, with an inflation-adjusted number at the end so you’re not fooling yourself about what that growth is actually worth.
Work out TDS on salary, freelance income, or contractor payments before your accountant tells you the number. Updated for FY 2024-25.
Base64 in, plain text out, or the reverse. Handles UTF-8 correctly, which trips up more of these converters than you’d expect.
Itemized invoices with tax, discounts, and the balance due calculated for you. Fewer places for a typo to hide than a spreadsheet.
Write your title and description once, see exactly how it’ll look in a Google result and when shared on X or LinkedIn, before you ship it.
SIP, compound interest, CAGR, tax estimates — the kind of math worth double-checking before you act on it.
JSON, Base64, JWTs, regex — the stuff I reach for constantly while building anything, including this site.
Resumes, invoices, PDFs — documents that need to actually look right, not just technically exist.
Meta tags, sitemaps, SERP previews — unglamorous, but it’s the stuff that actually moves rankings.
Most calculator sites upload your inputs to a server before doing anything with them. Mine doesn’t — here’s the actual difference that makes.
| Attribute | Burnjet (Local Browser) | Typical Online Utilities (Cloud SaaS) |
|---|---|---|
| Where it runs | Your browser. That’s the whole architecture. | Uploaded to their servers first |
| What happens to your data | Nothing to retain — it never left your machine | Logged, usually for longer than you’d guess if you read the privacy policy |
| Speed | As fast as you type — there’s no round trip to wait on | Depends on their servers and your connection that day |
| Getting started | Open the tool and use it | Account first, sometimes a card on file even for the free tier |
| Exports | Clean PDF, nothing held back | Watermarked until you upgrade, more often than not |
Five-minute brain breaks. Keyboard, touch, or a gamepad if you’ve got one plugged in.
Visual response time in milliseconds
Spatial visual pattern recall on expanding grids
WPM and code syntax typing accuracy
Rapid mental arithmetic under countdown pressure
Standard board rules with digital clock & resignation
Ever wondered what’s actually happening when you type into ChatGPT? I built a few interactive visualizers — tokenization, attention weights, RAG — that let you drag a slider and watch it happen instead of reading another 3,000-word explainer. No math background required.
Notes from building this site, written up properly instead of left in a scratch file.

A practical, non-gimmick guide on structuring your technical resume so Applicant Tracking Systems can parse your skills, dates, and experience accurately.

Understand the strict specification of JSON format, common syntax pitfalls that crash parsers, and practical strategies for safe serialization in production.

Learn the exact length constraints, copywriting principles, and search intent alignment required to write meta descriptions that maximize click-through rates on Google.

Why local-first, browser-executed utilities protect sensitive API keys, customer data, and development velocity compared to server-side tool websites.

Learn what Compound Annual Growth Rate (CAGR) measures, how to calculate it using the mathematical formula, and why it provides a realistic picture of investment returns.

Practical technical and on-page SEO audit checklist for small websites, indie startups, and developer projects looking to build consistent organic search traffic.
Clear answers regarding privacy, calculation models, and exports.
A pile of free tools I built and kept in one place — calculators, a resume builder, developer utilities, a handful of brain games. No grand unifying theory. Just things I needed badly enough to build properly, and figured other people needed too.
Everything runs in JavaScript, and the heavier stuff (PDF generation, resume export) uses WebAssembly — both execute right there in your browser tab. Your numbers, your resume text, whatever you paste into the JSON formatter: none of it gets sent anywhere, because there’s no API call carrying it out. Close the tab and it’s gone, since it was never stored to begin with.
Free. No usage caps, no "unlock the full version," no watermark slapped on your PDF. I don’t run ads on the tool pages either. If you want to support the site there’s a Buy Me a Coffee link in the footer — that’s the extent of the pitch.
The math itself isn’t mine to get wrong: compound interest and CAGR use the same future-value formulas you’d find in any finance textbook, and the tax calculators follow current provisions under the Indian Income Tax Act. I didn’t invent new formulas — I built a faster interface for the ones that already exist.
No account, no email, no login. Open the tool, use it, leave.
155 tools, one resume builder, zero accounts to create. Go find the one you actually need.