Aller au contenu
Toutes les missions
Veille marché · Dev-to Publiée il y a 1 mois

Government tech jobs in India: a developer's guide to how hiring actually works

Most developers in India hear about government tech jobs second-hand: a friend got into ISRO, a senior joined NIC, somebody's cousin cleared a bank IT officer exam. The process itself is rar...

Entreprise the hiring pipeline looks like.
Mode India hear about government tech jobs second-hand

Résumé

Most developers in India hear about government tech jobs second-hand: a friend got into ISRO, a senior joined NIC, somebody's cousin cleared a bank IT officer exam. The process itself is rarely explained. Here is the short version, written for people who already know how to code and want to know what the hiring pipeline looks like. 1. The notification is the spec Every recruitment starts with an official PDF notification. Treat it like a spec document, because the recruiting body will. It fixes: Eligibility: degree, branch, minimum percentage, and the cut-off date for age Selection stages: written test, skill test, interview, document verification Syllabus and exam pattern: sections, marks, negative marking Dates: application window, correction window, exam date If your branch is not listed, no amount of skill fixes that. Read the eligibility table before anything else. 2. Who actually hires engineers Body Typical roles Entry route NIC Scientist-B, Scientific/Technical Assistant NIELIT-conducted exam ISRO Scientist/Engineer SC (CS, EC, ME) ISRO centralised recruitment exam DRDO Scientist B GATE score + interview C-DAC Project Engineer, Project Associate Direct recruitment, often contract PSUs (IOCL, NTPC, PowerGrid...) Engineer / Executive Trainee GATE score Banks (IBPS SO, SBI SO) IT Officer Prelims + mains + interview 3. GATE is the closest thing to a common API A valid GATE score opens DRDO, most PSUs and several research bodies with one exam. The catch: each organisation publishes its own application form and its own cut-off, and the form usually opens before the GATE result. Miss the form and the score is useless for that employer. 4. The exam is computer based, and normalised Large exams run in multiple shifts with different question papers. Scores are normalised so a harder shift does not cost you. Cut-offs apply to the normalised score, not your raw marks. If that sounds odd, this explainer walks through an example: how normalisation works. 5. Common ways developers lose a seat Applying with a degree certificate dated after the cut-off date Uploading a photo or signature outside the size limits and skipping the correction window Ignoring the reporting time on the admit card (gates close early) Not downloading the response sheet when the answer key is released 6. Where to track it There is no single government feed for all of this, which is why we built Govtpvt. It lists latest government job notifications, admit cards and results, and each entry links to the official source PDF so you can verify it yourself. If you have been through one of these pipelines, I would like to hear what surprised you most.