Yes, you can assess your own readiness for a web development internship, and a rubric makes it honest. Score yourself from 0 to 3 on specific, observable tasks in HTML, JavaScript, backend and version control, then give your weakest areas the most practice time. This article provides the full rubric, a conversion method, and a 14-day plan that fits a two-week internship.
Why a skills-first rubric works better than a topic checklist
Most students describe their readiness by listing topics: “I have studied HTML, CSS, JavaScript, Node and Git.” That tells you nothing about whether you can build anything. A skills-first rubric asks a different question: what can you do, unaided, in a fixed amount of time?
The difference matters in a short internship. In 14 days, nobody will wait while you relearn how a form submits data. A mentor will hand you a small feature and expect progress. If you know in advance that your fetch handling is shaky or your Git branching is weak, you can fix exactly that before day one rather than discovering it on day four.
The rubric below has four skill areas, each with four levels (0 to 3). Every level is defined by a task you can attempt and check yourself, not by how confident you feel.
How to run the assessment honestly
- Use a blank folder. No copying from an old project. Create a new directory and build from nothing.
- Set a timer. Give each task a time limit (suggested limits are in the table). If you exceed it, score the level below.
- Limit your references. Official documentation is allowed, as it would be on the job. Pasting a full solution from a tutorial or an AI assistant is not.
- Score the lowest level you fully pass. Passing half a level means you stay at the lower one.
- Write down where you got stuck. The stuck points become your practice plan.
Free 2-Week CareerSwami Internship
Online, 14 days, with a free offer letter and a free completion certificate once you finish the work. Check with your college that it fits your requirement before you enrol.
The four-level rubric for HTML, JavaScript, backend and version control
Level 0 means you could not complete the Level 1 task. Levels 1 to 3 are described below. Each descriptor is a task you can attempt in one sitting.
| Skill area | Level 1 (Basic) | Level 2 (Working) | Level 3 (Internship-ready) |
|---|---|---|---|
| HTML and CSS | Build a static profile page with headings, a list, an image with alt text and a link, in 20 minutes. | Build a responsive card layout with semantic tags (header, main, section, footer) and a working form with labels, in 40 minutes. | Build a mobile-first page with flexbox or grid, accessible form validation messages and a keyboard-navigable menu, in 60 minutes. |
| JavaScript | Select elements, handle a click event and change text or a class, in 20 minutes. | Fetch JSON from a public API, render it as a list, and show loading and error states, in 45 minutes. | Build a small to-do or filter app with array methods, local storage persistence and functions split into readable modules, in 60 to 90 minutes. |
| Backend | Start a server (for example with Node and Express) that returns a JSON response on one route, in 30 minutes. | Create GET and POST routes that read and write to an in-memory array or a JSON file, with basic input checks, in 60 minutes. | Build a CRUD API connected to a database, with environment variables for config, sensible status codes and one route tested with a client tool, in 90 minutes. |
| Version control | Initialise a repository, commit changes with clear messages and push to a remote on GitHub, in 15 minutes. | Create a feature branch, make two commits, open a pull request and merge it, in 25 minutes. | Resolve a deliberate merge conflict, use .gitignore correctly, and revert a bad commit without losing other work, in 30 minutes. |
Optional fifth row: connecting front end to back end
If you want a full stack view, add a short integration task. Level 1: submit an HTML form to your own server route. Level 2: send JSON with fetch and display the server response without reloading. Level 3: handle a failed request gracefully and show the user a useful message. Score it separately and treat it as a bonus area in your plan.
A score sheet you can copy
Area | Score (0-3) | Time taken | Where I got stuck
HTML and CSS | | |
JavaScript | | |
Backend | | |
Version control | | |
Integration | | |
Total (out of 12 core, 15 with integration): ____
Converting rubric scores into practice hours
The goal is not a grand total. It is a distribution of your limited preparation time. A simple method: give each area a gap score equal to 3 minus your level, then share your hours in proportion.
- Calculate the gap for each core area (3 minus score).
- Add the gaps together.
- Decide how many preparation hours you have before the internship starts (for example, 20).
- Hours for an area = (area gap divided by total gap) multiplied by available hours.
- If an area scored 0, add a bonus of two hours for fundamentals before you begin the Level 1 task again.
Interpreting your total
| Core total (out of 12) | What it suggests | Focus |
|---|---|---|
| 0 to 4 | Foundations are still forming. | Spend the pre-internship days on HTML and JavaScript basics and one small Git workflow. Expect to learn alongside the tasks. |
| 5 to 8 | You can contribute with guidance. | Lift your two weakest areas to Level 2 and practise combining front end with a simple API. |
| 9 to 12 | You can take on small features. | Polish the weakest area to Level 3 and prepare a short portfolio project you can explain. |
Worked illustration: one student’s scores turned into a plan
This example is illustrative. The student and numbers are invented to show the method; no code was run.
Imagine a second-year student, Meera (a made-up name), who completes the rubric and records these scores.
- HTML and CSS: 2
- JavaScript: 1 (she could handle clicks but got stuck on fetch, and her error state never displayed)
- Backend: 0 (she could not start a server without a tutorial)
- Version control: 2
Gaps are 1, 2, 3 and 1, so the total gap is 7. She has 21 hours before the internship, which makes each gap point worth 3 hours.
- HTML and CSS: 3 hours (build one responsive layout with a form)
- JavaScript: 6 hours (fetch an API, handle promise failure, render a list)
- Backend: 9 hours, which already includes a fundamentals bonus; she spends the first two on how HTTP requests and responses work
- Version control: 3 hours (practise a deliberate merge conflict)
Her stuck notes also tell her what to write in her plan: “handle fetch errors” and “start Express server from scratch.” These are far more useful than “study JavaScript and backend.”
A 14-day plan built from your gap scores
If you have time before the internship, use the hours method above. If you are already inside the two-week window, use this structure and tilt the time toward your biggest gap.
| Days | Focus | Output to aim for |
|---|---|---|
| 1 to 2 | Re-run the rubric on your weakest area and read the relevant documentation. | One passing Level 1 task, with notes on what broke. |
| 3 to 5 | Move the weakest area to Level 2 and keep the second weakest ticking over. | A small working feature, committed daily to Git. |
| 6 to 8 | Connect front end to back end through one route. | A form or fetch call that talks to your own server. |
| 9 to 11 | Build the mini project and push to a branch with a pull request. | A feature branch with at least five meaningful commits. |
| 12 to 13 | Fix issues, add error handling, write a short README. | A readme with setup steps and one screenshot or description. |
| 14 | Re-score yourself on the rubric and write a one-page reflection. | A before and after score sheet. |
A free option for the practice itself is the free two-week online internship from CareerSwami, which includes a free offer letter and a free completion certificate after successful completion, with 26 tracks to choose from. Running your rubric before you start and again on day 14 gives you concrete evidence of what you actually improved.
Evidence to keep so your scores can be defended
A score is stronger when you can point to something. For each level you claim, keep one artefact.
- A GitHub repository link with dated commits.
- A short screen recording or screenshots of the working feature.
- A README describing what you built, how to run it and what you would improve.
- Your stuck-notes sheet, showing what you learnt from each failure.
Rajasthan ILD Skills University students: using this rubric alongside your university’s rules
Rajasthan ILD Skills University was established in Jaipur under the Rajasthan ILD Skills University, Jaipur Act, 2017 (Act No. 6 of 2017), which received the Governor’s assent on 28 March 2017. The same Act places the headquarters at Jaipur and defines a “college” as either a constituent or an affiliated college, so the statute allows for affiliation. It also defines ILD as the Institute of Leadership Development, Jaipur, a society registered under the Rajasthan Societies Registration Act, 1958.
What does that mean for a web development internship? The Act is a founding statute, not an internship regulation. It does not tell you how many weeks an internship must run, whether an online internship is accepted, or whether a certificate carries any weight in your programme. Those details sit in your programme’s regulations, scheme documents or department circulars, and they may differ between programmes or colleges. Treat any rule you hear second-hand as unconfirmed until you see it in writing.
The rubric helps here because it is independent of those rules. Whether your internship is recorded formally or not, your score sheet, repository and README are evidence of skill you can show to a faculty mentor or a recruiter. A free internship from CareerSwami is a voluntary, independent learning activity; it does not come with academic credit, a stipend or placement, and it has no link to the university.
Use these steps to confirm what applies to you.
- Ask your department office which document governs internships or project work for your programme, and request the current version in writing or as a PDF.
- Email your faculty coordinator with one question: “Is an online internship of two weeks accepted for my programme’s internship requirement, and in what format must it be reported?”
- Ask whether a mentor sign-off, completion certificate, report or presentation is needed, and by what date.
- Find out if your college is a constituent or affiliated college and which body’s rules apply to your programme.
- Ask the training and placement or career cell, if your college has one, whether it keeps a list of accepted internship formats.
- Check your academic calendar for semester breaks so your 14-day window does not clash with exams or lab submissions.
Warning signs that your self-score is too generous
- You passed a task only because you remembered the exact tutorial it came from.
- Your code works but you cannot explain a single line when asked.
- You never committed during the task and only made one big commit at the end.
- Your backend runs only when a specific browser tab is open or a specific file exists on your laptop.
- You skipped the timer because “it would have worked given more time.”
If two or more apply, drop that area by one level. Being under-scored costs you a little pride; being over-scored costs you the first week of the internship.
Retesting and tracking progress across the two weeks
Re-score at day 7 and day 14, using a different task at the same level so you are not just remembering the answer. For example, if your Level 2 JavaScript task was a weather list from an API, use a quotes list or a book list next time. Record the time, the score and the stuck points in a simple table or spreadsheet. Improvement shows up first as shorter completion times, then as a higher level.
Frequently Asked Questions
How long does the full rubric assessment take?
Adding the suggested time limits, a full run through all four core areas at Level 3 takes roughly four to five hours. Many students split it across two sittings. Stop at the first level you fail in each area rather than attempting everything.
Can I use documentation during the assessment?
Yes, official documentation and language references are fine because working developers use them daily. Avoid copying finished solutions, since that tests your ability to paste rather than build.
What if I have never touched backend code?
Score yourself 0 and treat it as the largest gap. Spend your first hours on how HTTP requests and responses work, then attempt the Level 1 task of a server with one JSON route. A beginner-friendly stack such as Node with Express keeps you in JavaScript throughout.
Should I learn a framework before the internship?
The rubric tests fundamentals that every framework depends on. If you score below Level 2 in JavaScript, a framework will add confusion rather than speed. Reach Level 2 first, then explore a framework if your internship track calls for it.
Does this rubric match what my university will assess?
No. It is an independent self-assessment tool, not an official evaluation scheme. Your programme may have its own report, viva or sign-off requirements, so confirm them with your department using the verification steps above.
How do I show my rubric results to a recruiter or mentor?
Share a repository link, the before and after score sheet and a short README. Describe what you were stuck on and how you resolved it. Specific evidence is more convincing than a statement that you are “good at JavaScript.”
What if my scores are the same on day 14 as on day 1?
Check your stuck notes. Often the level has not changed but the time has dropped, or one sub-skill has improved without clearing the whole level. Pick the single failed requirement and make it your next small task.
Does completing the CareerSwami internship count for academic credit?
CareerSwami offers a free offer letter and a free completion certificate after successful completion, but no academic credit is promised. Whether your department accepts it for any requirement is a question for your faculty coordinator.
Ready to put this into practice?
Join the free two-week CareerSwami online internship in Full Stack Web Development. The internship, the offer letter and the completion certificate are free.




