Contact
Feedback, a correction, or a question you think belongs here? I’d like to hear it.
Reach me at nachiketsalvi11@gmail.com.
What’s useful to include
If you’re reporting an error in a specific question, mentioning the question title — and, if you can, what the answer should say instead — helps a lot and gets it fixed faster. For a suggested new question, a one-line description of the pattern or concept it tests is plenty.
What kind of feedback is welcome
Corrections to answers or code, clearer explanations, missing edge cases, broken links, and ideas for topics that aren’t covered yet are all genuinely appreciated. This guide is maintained as a single source of truth, so a fix you send in is reflected everywhere — the interactive page, the Markdown export, and the Word document.
Response time
This is a personally maintained project, so please allow a little time for a reply. There’s no newsletter, no account, and no tracking — just email.
Privacy
Anything you send by email is used only to answer you or to improve a question, and it is never added to a mailing list or shared. The site itself asks for no personal details and keeps your study progress in your own browser; for the full details see the privacy policy.
Contributing to the corpus
The questions here grow from real interview patterns and reader suggestions. If a topic keeps coming up in interviews you’ve sat and it isn’t covered, that’s exactly the kind of gap worth flagging — say which area it belongs to (HTML/CSS, Browser, JavaScript, TypeScript, React, System Design, Accessibility, Web Performance, Testing, Networking/Security, or DSA) and roughly what it should test. Because everything is generated from one source, an accepted addition or fix appears across the interactive page, the Markdown export, and the Word document at once.