DEV Community: Govtpvt

Parsing a Result PDF to Find Your Roll Number in Seconds

Govtpvt — Wed, 21 Oct 2026 08:23:45 +0000

Government exam results in India are often published as long PDFs with thousands of roll numbers. Searching them in a browser works, but when you are checking for a whole group of friends or students, a script is faster.

Install

pip install pdfplumber

Script

import pdfplumber, sys

pdf_path = sys.argv[1]
targets = set(sys.argv[2:])

with pdfplumber.open(pdf_path) as pdf:
    for i, page in enumerate(pdf.pages, start=1):
        text = page.extract_text() or ""
        for t in targets:
            if t in text:
                print(f"{t} found on page {i}")

Run it with:

python find_roll.py result.pdf 2401001234 2401005678

Caveats

Some PDFs are scanned images. You will need OCR (for example pytesseract) for those.
Roll numbers can be split across lines in tables. Normalise whitespace if you get misses.
Always confirm with the official PDF before celebrating.

Where do the PDFs come from? Official board sites, or a tracker that links to them. I use the Sarkari results page on govtpvt.com, which links the official result notice for each exam.

Building a Deadline Reminder for Government Job Forms with Google Calendar and a CSV

Govtpvt — Wed, 21 Oct 2026 08:23:44 +0000

Applying to several government recruitments at once means juggling last dates, fee deadlines, admit card weeks and exam days. I built a tiny workflow that turns a CSV into calendar reminders. No server, no paid tools.

The CSV

exam,event,date
SSC CGL,Last date to apply,2026-11-14
SSC CGL,Fee payment closes,2026-11-15
RRB NTPC,Admit card expected,2026-12-02

Fill it from the official notices. I copy new rows whenever a notice appears on a tracker like the latest government jobs page on Govtpvt.

Convert to ICS with Python

import csv
from datetime import datetime

lines = ["BEGIN:VCALENDAR", "VERSION:2.0"]
with open("deadlines.csv") as f:
    for row in csv.DictReader(f):
        d = datetime.strptime(row["date"], "%Y-%m-%d").strftime("%Y%m%d")
        lines += ["BEGIN:VEVENT", f"DTSTART;VALUE=DATE:{d}",
                  f"SUMMARY:{row['exam']} - {row['event']}",
                  "BEGIN:VALARM", "TRIGGER:-P2D", "ACTION:DISPLAY",
                  "DESCRIPTION:Reminder", "END:VALARM", "END:VEVENT"]
lines.append("END:VCALENDAR")
open("deadlines.ics", "w").write("\n".join(lines))

Import deadlines.ics into Google Calendar. Each event gets an alert two days early.

Why two days

Payment gateways and portals slow down near deadlines. Two days of buffer has saved me more than once.

If you are building something similar, Govtpvt is a handy source for dates, since it lists notices, admit cards and results in one place.

Scraping-Free Alerts: Tracking Government Job Notices with RSS and a Spreadsheet

Govtpvt — Sat, 17 Oct 2026 08:50:43 +0000

Most government recruitment sites in India don't offer an API, and scraping them is fragile and often against their terms. Here is a low-tech setup that works for a personal job-alert pipeline.

1. Pick sources that publish feeds

Many aggregators and some official portals expose RSS or Atom. Collect the feed URLs in one list.

2. Pull feeds into a spreadsheet

Google Sheets' IMPORTFEED function pulls the latest items into rows:

=IMPORTFEED("https://example.org/feed", "items title", FALSE, 20)

3. Filter by keyword

Use FILTER with REGEXMATCH to keep only rows matching terms like "engineer", "apprentice" or your state:

=FILTER(A2:B, REGEXMATCH(LOWER(A2:A), "apprentice|junior engineer"))

4. Add a closing-date column by hand

Feeds rarely include the last date. Add it when you open the official notice. Conditional formatting can turn rows red seven days before the deadline.

5. Notifications

Sheets can email you on change via Tools > Notification settings.

For a human-curated source to cross-check, Govtpvt keeps a running list of Sarkari job notifications, each linked to the official PDF.

Modelling India's PSU List as Structured Data: A Small Schema

Govtpvt — Sat, 17 Oct 2026 08:19:11 +0000

While building the PSU section on Govtpvt, we needed a clean way to store India's public sector companies so the same data could drive tables, filters and per-company pages. Here is the schema we settled on, in case it helps anyone working with Indian government data.

The problem

A "PSU list" looks simple until you try to store it. Companies change status (Miniratna to Navratna to Maharatna), merge, get renamed or move ministries. Public sector banks and insurers are government companies but follow different rules from industrial CPSEs. And recruitment details (GATE or own exam) matter more to readers than the status itself.

The schema

{
  "name": "NTPC Limited",
  "short_name": "NTPC",
  "status": "maharatna",
  "status_since": "2010",
  "type": "cpse",
  "sector": "power",
  "ministry": "Ministry of Power",
  "listed": true,
  "hq": "New Delhi",
  "recruitment": ["gate", "apprenticeship"],
  "careers_url": "https://careers.ntpc.co.in"
}

A few choices worth explaining:

status is an enum (maharatna, navratna, miniratna_1, miniratna_2, none) plus status_since, so upgrades are easy to track.
type separates cpse, state_psu, psb (public sector bank) and insurer. Mixing them in one flat list confuses readers.
recruitment is an array because many companies use more than one route.
careers_url always points at the official site. We never link to third-party mirrors for application forms.

Rendering

Grouping by status gives the Maharatna/Navratna/Miniratna tables, and grouping by sector gives the sector-wise view. Filtering recruitment on gate produces the "PSUs that recruit through GATE" list automatically.

You can see the result on the PSU list in India page. The same approach powers our latest government jobs listings, where every entry links back to the official notice.

If you maintain similar datasets for Indian public data, I'd love to compare notes in the comments.

Dates are the hardest field: handling deadlines that change after you publish them

Govtpvt — Sun, 11 Oct 2026 11:17:42 +0000

If you publish anything with a deadline on it, such as event listings, tender notices, admissions or job openings, you already know the awkward truth: the source changes the date after you have published it, and it does not tell you.

We run a jobs portal for India, and deadline extensions are the single largest source of corrections. A few patterns have made them manageable.

1. A date is a claim with a source

Store each date together with where it came from and when you saw it:

{
  "field": "closing_date",
  "value": "2026-03-24",
  "source": "corrigendum-1.pdf",
  "seen_at": "2026-03-09",
  "supersedes": "2026-03-14"
}

Now a correction is an append, not an overwrite, and you can always answer the question of what the page said last Tuesday.

2. "Unknown" must be a valid value

When an exam is postponed with no new date, the honest state is to be announced. If your schema or UI forces a date, someone will type a guess, and guesses get screenshotted.

3. Show the change, do not hide it

Render the old value struck through next to the new one with a link to the notice. It costs a line of UI and removes most "is this right?" emails.

4. Derive, do not duplicate

"Closing soon" badges, countdowns and reminder emails should be computed from the latest assertion at read time. Anything cached with the old date will be wrong the day after an extension.

5. Time zones and end-of-day

"Last date: 24 March" almost always means 23:59 local time at the source, and occasionally means 17:00. Record the time when the notice gives one, and never convert a date-only value through UTC.

6. Re-check on a schedule that matches risk

Listings within a week of closing are the ones most likely to be extended. Re-verify those daily; everything else can wait.

None of this is clever. It is just treating published dates as versioned data. You can see the result on our latest government jobs listings at Govtpvt.

GATE CS is not only for M.Tech: how PSU recruitment through GATE works

Govtpvt — Sat, 10 Oct 2026 11:21:06 +0000

If you are a CS or IT graduate sitting GATE, the M.Tech route is only one of the things the score is good for. Several public sector employers shortlist engineers directly from GATE, and the process is very different from campus placement. Here is how it works, step by step.

The score is necessary, the form is mandatory

PSUs do not pull your score from GATE automatically. Each one publishes its own recruitment notification and its own application form, where you enter your GATE registration number. Many of these forms open before the GATE result is declared and close soon after. Every year, people with good scores miss out because they never applied.

A simple habit fixes this: from January onwards, check a list of current government job notifications once a week and apply to every PSU whose eligibility you meet.

Check the paper code and branch mapping

Each notification lists which GATE paper it accepts for which discipline. For software roles that is usually CS, sometimes also DA or EC. If the notification says CS only and you wrote DA, you are not eligible for that post, whatever your rank.

What happens after shortlisting

Shortlist by GATE score, category-wise, usually at a fixed ratio to vacancies
Group discussion or group task at some PSUs
Personal interview, technical plus HR
Final merit list, typically weighted around 75 to 85 percent GATE and the rest interview
Medical examination and document verification

Because GATE carries most of the weight, the interview rarely rescues a low score, but it can reorder candidates who are close together.

Things the notification will tell you (read them)

Service bond: many PSUs ask for a bond of a few years
Pay scale: quoted as a range such as 50,000 to 1,60,000; your starting basic is the lower figure, with allowances on top. This guide to government salary basics explains how to read it
Minimum percentage in your degree, which is separate from your GATE score
Final-year eligibility and the date by which you must produce the degree

A realistic timeline

Month	What to do
Aug to Oct	GATE registration
Jan to Mar	PSU forms open; apply with registration number
Feb	GATE exam
Mar	GATE result; PSUs fetch scores
Apr to Jul	Shortlists, interviews, final results

Keep one folder ready

GATE scorecard, degree and mark sheets, category certificate in the central format, photo ID and recent photographs. Document verification is where avoidable rejections happen.

A longer version of this, including research bodies that take GATE scores, is in this GATE to PSU guide. Results and shortlists are tracked on the Govtpvt results page.

Lessons from running a government jobs portal: treat every update as data, not content

Govtpvt — Sat, 10 Oct 2026 11:13:50 +0000

Running a jobs portal sounds like a content problem. In practice it is a data quality problem. A wrong last date or a wrong fee on a government job listing costs a real person an application, so the whole workflow at Govtpvt is built around one rule: nothing gets published unless it points to the official source document.

These are the practices that have held up for us. They apply to any site that republishes time-sensitive public information.

1. Store the source, not just the summary

Every listing carries the URL of the official notification PDF and the official apply page. Reviewers check the listing against the PDF, and readers can check it too. If we cannot find an official document, the update does not go out, however widely it is being shared elsewhere.

2. Model the lifecycle, not the announcement

A recruitment is not one event. It is a sequence:

notification -> application window -> correction window
  -> admit card -> exam -> answer key -> result -> document verification

Each stage has its own date and its own official link. Treating them as states of one record, instead of separate articles, is what lets a reader land on a page and see where things stand today. That is why the site is organised by stage: latest jobs, admit cards, answer keys and results.

3. Dates are the highest-risk field

Most corrections we make are date corrections, because recruiting bodies extend deadlines through short corrigendum notices. Three habits help:

Keep the original date and the revised date, and show both
Record which notice changed it
Never infer a date. "Exam likely in December" is not a date

4. Write eligibility as a table

Age limits, relaxations, qualification and fee vary by category. Prose hides the differences; a table exposes them. It also makes review faster, because a reviewer can compare row by row with the notification.

5. Keep explainers separate from updates

Updates expire. Explanations do not. Things like how normalisation works or what a pay level means live as standalone guides, for example this glossary of government job terms, and listings link to them instead of repeating the explanation each time.

6. Make corrections visible

When we get something wrong, the fix is made on the same page with the corrected value. Quietly replacing a number teaches readers not to trust the page.

What I would tell anyone building something similar

Speed matters less than you think. Being ten minutes behind and right beats being first and wrong, because the reader's next step is to pay a fee and submit a form.

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

Govtpvt — Sat, 10 Oct 2026 11:12:56 +0000

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.