After a gap plan¶
~6 min
In short¶
You have a gap in your record. Maybe you took a year out, your marks were low, you had no placements, or you left a job and have been learning on your own since. This is common, and it does not end the search. What helps is honest reflection about your options, small steps you can finish, and a visible record of what you built.
Nothing on this page promises a job. Some employers' eligibility rules may exclude people with low marks or backlogs, and sources disagree on those rules (see the non-CS branch plan for an example). Check each company's current notice before you spend time on it.
Start with an honest list of options¶
Write down what is true for you today: your degree, marks, the years since you last studied or worked, what you have built, and what you can give each week. Then list the options that fit.
- Keep applying where your record meets the rules. Some companies publish eligibility, and some roles accept experience. Use the applying section to find them.
- Build a visible record first. A few finished projects on GitHub can show what you can do when a resume alone cannot.
- Take a structured free course. CS50x, Missing Semester and freeCodeCamp are free paths (links below).
- Look at a degree route, if fees and time suit you. The IIT Madras BS in Data Science and Applications publishes its fees, and its qualifier deadline is 29 Jan 2027 for the January 2027 term (https://study.iitm.ac.in/ds/, checked 18 Oct 2026). It is an option, not a requirement.
- Consider a nearby role. QA, support or data work can be a step into software. Check the skills the job description names.
Pick the option that is cheapest to try this month.
Small steps beat big plans¶
After a gap, large plans often stall. Shrink the goal until you can finish it in a week:
- One coding problem, solved and written up in three lines.
- One lesson from a free course, with a note on what you did not understand.
- One small program that does a real task you have.
- One application, with a note on what you would change.
Repeat the same small steps each week. Measure yourself by how many you finished, not by how far away the goal feels.
Build evidence, in public if you can¶
Employers and interviewers look for evidence that you can build and explain. Make your work visible:
- Put each project on GitHub with a readme that says what it does, how to run it, and what you would change.
- Keep a short learning log, with dates. It shows steady progress, which a gap can hide.
- If you cannot show employment, show a project. Explain the gap in one sentence, then move to what you built.
Do not invent experience or dates. Interviewers ask follow-up questions, and a false claim will fall apart.
Explain the gap¶
Say it briefly and move on. A good answer covers what happened, what you did about it, and what you are doing now. For example: "I took a year away for family reasons. During that time I finished a database course and built a small inventory app, which I now want to build on at work." Adjust the words to your facts. Keep it under thirty seconds.
Honest limits¶
- Hiring rules differ by company, and some use marks or backlog cut-offs. Check the notice.
- No public data was found on hiring rates for people after a gap in India.
- Some paths take longer than you would like. A slow path that you keep walking is better than a fast plan you abandon.
Targets, in order¶
| # | Target | You can move on when |
|---|---|---|
| 1 | Honest options list, and one small step done each week | The list is written and you have done four small steps |
| 2 | Missing Semester basics, with one command or git note each week | You can use the terminal and make a commit |
| 3 | CS50x first half, a short program each week | You have a program that reads input and saves a file |
| 4 | CS50x second half, final project started | You can explain the project in two minutes |
| 5 | One problem a week from the DSA section | You can solve an easy problem and write it up |
| 6 | First GitHub project with a readme | The project runs and the readme explains how |
| 7 | Core subject notes, one topic a week | You can explain one topic without notes |
| 8 | Second project with a database or an API | The project has a clear purpose you can state |
| 9 | Resume draft that states the gap in one line | Each resume line points to something you built |
| 10 | Decide on one option to try: a role, a course, or a degree | You have written the reason for your choice |
| 11 | Applications to roles that match your record, logged | Your log has each application with a date |
| 12 | Review of replies, and a plan for the next three months | You know what to change and when you will do it |
Try this¶
What to do this week: Write your honest options list on one page, with five lines: your degree, your marks, the years since you last studied or worked, what you have built, and the hours you can give each week. Then choose one small step from this page and finish it by the end of the week.
Sources¶
- Harvard CS50x: https://cs50.harvard.edu/x/ (checked 18 Oct 2026)
- MIT Missing Semester: https://missing.csail.mit.edu/ (checked 18 Oct 2026)
- freeCodeCamp: https://www.freecodecamp.org/learn (checked 18 Oct 2026)
- IIT Madras BS in Data Science and Applications: https://study.iitm.ac.in/ds/ (checked 18 Oct 2026)