DEV Community: Jaydeep Goswami

How to Find Tech Jobs Early in India: Watch Where They're Posted First

Jaydeep Goswami — Sat, 24 Oct 2026 17:47:43 +0000

Short version: you can't see a job before the employer publishes it. But you can watch the place where it's published first. For many tech jobs, that's the company's own careers page or applicant tracking system (ATS). Copies on LinkedIn, Naukri and other sites come after that.

The full guide is on jobspiq.in.

1. Where a tech job appears first

When a company opens a role, a recruiter creates it in the company's ATS, which publishes it on the company's careers page. Copies elsewhere come later: the company may post it on LinkedIn or Naukri, aggregators may pull it in, or a recruiter may share it.

The ATS boards you'll meet most in India:

Greenhouse (boards.greenhouse.io, job-boards.greenhouse.io): global and product companies
Lever (jobs.lever.co): product companies and startups
Ashby (jobs.ashbyhq.com): newer startups
SmartRecruiters and Workday (myworkdayjobs.com): larger companies and enterprises
Darwinbox, Keka and Zoho Recruit: widely used by Indian companies

2. Search ATS boards directly

Google indexes these boards. Combine the board's domain with a role and a location:

site:boards.greenhouse.io "India" "backend engineer"
site:jobs.lever.co "Bengaluru" "data engineer"
site:jobs.ashbyhq.com "Remote" "India" "frontend"
site:myworkdayjobs.com "Hyderabad" "SDE"

Use Google's Tools → Past 24 hours filter to see only recent pages. Expect some closed jobs: a board page can stay in Google's index after the role is filled.

3. Follow the companies you actually want

Make a short list of 20–30 target companies and bookmark their careers pages. Many careers pages let you subscribe to new openings by email. Following a company on LinkedIn also shows you the jobs it posts there.

4. Ask about roles before they're public

Teams often know about an opening before it's published. Former colleagues, alumni and people you've helped are your best early signal. Ask a specific question: "Is your team planning to hire a backend engineer this quarter?" is easier to answer than "Any openings?"

5. Let a tool read the boards for you

Checking 30 careers pages by hand every day doesn't last. Alert services differ mainly in two ways:

Where they look: a service that reads employer ATS boards sees jobs at the source. One that only re-lists portal jobs sees them once they reach the portal.
How they tell you: push alerts (app, browser, Telegram) arrive when the job is found. Email alerts are usually a digest: LinkedIn sends them daily or weekly, and Naukri a few times a week.

Disclosure: I build Jobspiq, one of these tools. In my own measurement of jobs posted in the 14 days to 12 October 2026, the median time from an employer publishing a job to Jobspiq finding it was about 6 minutes on Greenhouse (107 jobs) and 12 minutes on Ashby (89 jobs). Here's the full method and its limits. Jobspiq checks its sources about every 30 minutes and sends a strong match usually within a minute of finding it.

For a side-by-side look at the alert tools developers in India use, see Job Alert Apps for Developers in India.

6. Have your resume ready

An alert only helps if you can apply well. Keep a master resume with every project and metric, so tailoring it to a job takes minutes, not an evening. Here's how to tailor a resume to a job description.

Checklist

A list of 20–30 target companies and their ATS boards
Saved Google searches for your role on Greenhouse, Lever, Ashby and Workday
Push alerts (not only email) from a service that reads employer boards
A master resume, ready to tailor
Three people you can ask about openings on their team

More details

The full guide, with links to today's newest tech roles in India, is here: How to Find Jobs Before They Are Posted in India.

Which of these do you already use? Tell me in the comments.

Job Alert Apps for Developers (2026): An Honest Comparison

Jaydeep Goswami — Sat, 24 Oct 2026 17:47:07 +0000

Disclosure: I'm the founder of Jobspiq, which is one of the tools below. Every other product is described from its own public pages as read in October 2026. I didn't test other services' alert speed and make no claim about it. The full comparison, with a link to every source, is on jobspiq.in.

Quick answer: use one large portal for reach (LinkedIn or Naukri) and one fast alert service for the companies you care about. Which fast service suits you depends on where it looks for jobs and how it reaches you: email, app push or Telegram.

At a glance

Tool	Best for	How alerts reach you	Cost to candidates
LinkedIn	Most listings, recruiter reach	Email daily or weekly; app notifications	Free (Premium optional)
Naukri	Volume across Indian employers	Email a few times a week; app	Free (paid services optional)
Instahyre	Curated matches, recruiters reach out	Matches in the app; recruiters contact you	Free
Cutshort	Tech and product roles, skill-based matching	Recommended-jobs feed; employers contact you	Free
Wellfound	Startups	Email alerts	Free
Hirist	Tech-only job board	App and site	Free
Google job search	Jobs from many sites in one search	Email alerts for a saved search	Free
Prefetch	Engineering roles from ATS boards	Email	From ₹99/month
Jobrix	Ranked alerts on Telegram	Telegram	Free tier; Pro ₹349/month
Jobspiq	Tech jobs in India matched to your profile	Android app, browser push, Telegram; email digest	Free during beta

Prices are as listed on each product's own pages in October 2026.

The large portals

LinkedIn has the widest set of jobs and the most recruiters. You create a job alert from any search. By default it sends a daily email plus app notifications, and you can switch the email to weekly. Email alerts are a digest.

Naukri is strong for IT services and large employers. You save an alert from a search, and per Naukri's FAQ it's emailed a few times a week. App notifications are configurable.

Profiles that recruiters find

Instahyre is free for job seekers. It curates openings for your profile and lets matched recruiters contact you. It's often recommended for mid-level engineers.

Cutshort is free for candidates and focused on tech and product roles. You build a profile, and Cutshort matches it to employers and shows recommended jobs. It's strong for startups.

Wellfound (formerly AngelList Talent) is free for candidates, with email job alerts and many India and remote startup roles.

Hirist is a free, tech-only job board for India with an Android app. It's useful when you want listings without non-tech noise.

Search everything at once

Google job search shows a jobs panel gathered from many sites when you search for a role. Signed in, you can turn on email alerts for that search. It's good for breadth; you still apply on the original site.

Built for speed

Prefetch reads company career pages and ATS boards (Greenhouse, Lever, Ashby and others) for engineering roles. It says it checks about every 15 minutes, and it alerts by email. Paid plans start at ₹99 a month.

Jobrix sends ranked job alerts on Telegram. Its free tier lists up to 10 alerts a day with a 2-hour delay. Pro, at ₹349 a month, lists faster alerts, more alerts a day and AI fit explanations.

Jobspiq (mine) checks multiple sources about every 30 minutes: job portals and employer hiring systems such as Greenhouse, Lever, Ashby and Workday. It scores each new tech job in India against your skills and experience, showing the skills you have and the ones you're missing. Strong matches go to the Android app, your browser or Telegram, usually within a minute of Jobspiq finding them, and email comes as a daily digest.

In my own measurement of jobs posted in the 14 days to 12 October 2026, the median time from an employer publishing a job to Jobspiq finding it was about 6 minutes on Greenhouse (107 jobs) and 12 minutes on Ashby (89 jobs). The method is here.

Jobspiq also includes an application tracker and resume tailoring. Every feature is free during the beta, with no card needed.

Where others are better: LinkedIn and Naukri have far more jobs and recruiters. Instahyre and Cutshort bring recruiters to you, which Jobspiq doesn't do for candidates. Jobspiq covers tech jobs in India only.

How to choose

Fresher or early career: Naukri and LinkedIn for volume, plus fast alerts for product companies.
Mid-level, and you want recruiters to come to you: Instahyre or Cutshort, plus LinkedIn.
Targeting specific product companies: a service that reads ATS boards, with push or Telegram alerts.
Remote roles: Wellfound and remote filters, checking that each job is open to candidates in India.

More details

The full comparison, with links to each product's own help and pricing pages, is here: Job Alert Apps for Developers in India (2026).

Products change their features and prices often, so check each site before you decide. If something here is out of date, tell me in the comments and I'll fix it.

How to Tailor Your Resume to a Job Description: ATS Keywords, Skills & Real Evidence

Jaydeep Goswami — Tue, 29 Sep 2026 14:09:30 +0000

Most resume advice says: "Add more keywords from the job description." That's incomplete.

A better approach is to treat resume tailoring as an evidence-alignment problem. The goal isn't to make your resume contain every technology in the job description. It's to make the relevant parts of your real experience easy for both systems and people to find, understand and verify.

That means:

Job requirements → Candidate evidence → Relevant terminology → Stronger presentation → Interview-defensible resume

Here is the framework I use for technical resumes.

1. Start with the job description

Don't immediately start editing your resume.

First, break the job description into requirements.

Look for:

Core programming languages
Databases
Frameworks
Architecture patterns
Cloud/platform requirements
Testing requirements
Responsibilities
Seniority expectations
Domain-specific requirements

Not every word deserves equal weight.

If a technology appears in the title, summary, responsibilities, and qualifications, it is probably more important than a tool mentioned once in a long "nice to have" list.

For example, a backend platform role might emphasize:

Go
PostgreSQL
Distributed systems
API design
Kubernetes

Those requirements should receive more attention than secondary tooling such as Jira or Git.

The first question should therefore be:

What are the 3–5 requirements this role actually revolves around?

2. Map requirements to real evidence

This is where resume tailoring becomes more than keyword matching.

For every important requirement, ask:

Where have I actually demonstrated this?

A useful evidence hierarchy is:

Tier 1 — Commercial experience

You used the technology or capability in a real production environment.

Tier 2 — Project evidence

You implemented it in a meaningful personal, open-source, academic, or independent project.

Tier 3 — Skills-only evidence

You have familiarity with the technology but don't have substantial supporting experience or project evidence.

A technology appearing in your Skills section doesn't automatically mean you should present yourself as an expert.

If your resume says:

Kafka, Kubernetes, Distributed Systems

a technical interviewer can reasonably ask:

Why Kafka?
How did you handle partitioning?
What happened during failures?
How did you deploy Kubernetes workloads?
What architectural trade-offs did you make?

If you can't answer those questions, the wording is probably too strong.

Every important claim should be interview-defensible.

3. Use the job description's terminology — naturally

Matching terminology matters.

But keyword stuffing is not the answer.

Suppose your existing resume says:

Built an internal message routing system.

The job description talks about:

asynchronous messaging, RabbitMQ, Redis, event-driven architecture

If those technologies and concepts genuinely describe what you built, you can translate your wording into standard industry terminology.

For example:

Engineered an asynchronous message-routing pipeline using RabbitMQ and Redis pub/sub.

That's different from simply adding:

RabbitMQ Kubernetes Kafka AWS GraphQL Docker

to the end of an unrelated bullet.

The first improves clarity.

The second looks artificial.

Use the terminology that accurately describes your work.

4. Align your headline with the target role

Your headline is one of the first things a recruiter sees.

A generic:

Software Engineer

may not communicate your actual specialization.

If your experience genuinely supports it, something like:

Backend Software Engineer — Distributed Systems & Platform Infrastructure

can communicate your focus more clearly.

But there is an important boundary:

Never inflate your seniority or ownership.

Don't turn:

contributed to a distributed service

into:

architected the company's distributed platform

unless that is actually true.

Tailoring should improve relevance, not rewrite your career history.

5. Put the strongest evidence near the top

The first section of your resume has limited space.

Use it deliberately.

Your top section should quickly communicate:

Who you are
What role you target
Your strongest relevant technical capabilities
Your most relevant recent experience

When tailoring for an API engineering position, for example, API architecture and performance work should appear before less relevant accomplishments.

The same experience can become much more effective simply by changing its order.

6. Prioritize skills instead of dumping everything

One of the easiest ways to weaken a technical resume is to list everything you've ever touched.

A better structure is to group skills:

Languages

Python, Go, TypeScript, SQL

Frameworks & Runtimes

FastAPI, Node.js, React

Databases & Storage

PostgreSQL, Redis, Elasticsearch

Cloud & Infrastructure

AWS, Docker, Kubernetes, Terraform

Architecture

REST, gRPC, Distributed Systems, Event-Driven Architecture

Then prioritize the groups and technologies that actually matter for the target position.

Your resume isn't a database of every technology you've encountered.

It is a representation of the evidence most relevant to this application.

7. Rewrite responsibilities into accomplishments

A common resume problem is describing what you were assigned rather than what you accomplished.

Compare:

Worked on backend APIs in Go and handled database query optimization.

with:

Engineered asynchronous ingestion APIs in Go, optimizing PostgreSQL indexing and connection pooling to reduce p95 latency from 480ms to 120ms under peak load.

The second statement communicates:

Action → What → How → Result

But there is an important rule:

Only use metrics you can defend.

Don't invent:

Improved performance by 35%.

just because quantified bullets look better.

If someone asks:

How did you measure that 35%?

you should have a real answer.

Technical scope can also be quantified:

Requests per second
Records processed
Latency
Test coverage
Deployment time
Build time
Error rates
Dataset size
Resource utilization

If you don't have a trustworthy metric, write a strong qualitative result instead.

8. Keep projects as evidence

Projects are particularly important when you're moving into a new specialization.

But:

Built a chat application using React, Node.js and MongoDB.

doesn't tell the reader much.

A stronger project description explains:

The engineering problem
Your technical approach
Your contribution
The resulting behavior or outcome
A repository or live demonstration when available

Projects should demonstrate engineering ability, not just technology exposure.

9. Keep the resume ATS-safe

ATS systems need to extract meaningful text from your document.

That makes formatting important.

A safer structure is:

Single-column layout
Standard section headings
Selectable text
Consistent dates
Normal text-based contact information
Working hyperlinks
Clear bullet points

Avoid putting critical information inside:

Images
Graphics
Progress bars
Decorative elements
Complex text boxes
Complicated multi-column layouts

One simple test:

Open your exported PDF.

Press Ctrl+A.

Copy everything into a plain text editor.

If the text is scrambled, missing, or in the wrong order, the document may also be difficult for an ATS parser to interpret.

10. The final test: Can you defend it?

Before submitting, take every important claim and ask:

Context

What problem was I solving?

Decision

Why did we choose this approach?

Contribution

What did I personally build or contribute?

Verification

How did we measure or verify the result?

If you can't explain the claim clearly, weaken or remove it.

A resume shouldn't just describe what you want recruiters to believe.

It should accurately represent what you can demonstrate.

How Jobspiq approaches this

This is the principle behind Jobspiq Resume Studio.

Instead of treating tailoring as rewriting a resume from scratch, the workflow starts with the job description and maps its requirements against the candidate's verified information.

The process is:

Job Description
↓
Requirement Extraction
↓
Candidate Evidence Matching
↓
Evidence Strength
↓
Relevant Skill Prioritization
↓
Bullet Alignment
↓
ATS & Readability Checks
↓
Interview Defensibility
↓
Tailored Resume

The important distinction is that tailoring happens on a targeted version of the resume.

The Master Resume remains the source of verified information rather than being rewritten for every application.

That allows each application to emphasize different evidence while preserving the underlying career history.

The simple rule

Don't ask:

"How many keywords can I put into my resume?"

Ask:

"Which requirements matter, what evidence do I have, and how clearly can I show that evidence?"

That's the difference between keyword optimization and evidence-based resume tailoring.

For the complete guide, examples, checklist, and deeper breakdown:

👉 Read the full Jobspiq guide

About Jobspiq

Jobspiq is an AI job search platform for tech professionals in India. It checks job sources every 30 minutes, scores every job against your skills, and alerts you to strong matches, usually within a minute. Resume Studio tailors a resume to a job without inventing or dropping facts. Every feature is free during the beta: jobspiq.in

State of Tech Hiring in India, July 2026: What 123,875 Job Postings Show

Jaydeep Goswami — Mon, 10 Aug 2026 09:06:55 +0000

This is a short summary of Jobspiq's July 2026 hiring report. The full report, with charts and the data table, is on jobspiq.in.

The headline number

In July 2026 (1–31 July), Jobspiq counted 123,875 tech job postings in India from LinkedIn, Naukri and company career pages.

Where the jobs were

City	Postings
Bengaluru	27,840
Hyderabad	11,271
Pune	11,050
Mumbai	9,974
Chennai	8,544

Bengaluru alone had 22.5% of all postings, more than Hyderabad and Pune combined.

The skills that showed up most

Counted as mentions in job postings; one posting can mention several skills.

Skill	Mentions
Python	26,101
SQL	22,598
Agile	19,727
Azure	18,864
AWS	18,785
CI/CD	18,143
Git	16,503
DevOps	13,649
Java	12,806

Python and SQL lead, and cloud (Azure, AWS) and delivery skills (CI/CD, DevOps) are close behind.

Work mode

89% of postings were onsite or hybrid. 11% were fully remote. If you're filtering only for remote roles, you're looking at about one posting in nine.

Limits

These counts cover the sources Jobspiq checks, so they describe those sources, not every tech job in India. Most listings come from LinkedIn and Naukri. Skill counts measure how often a skill is mentioned, not how many people are hired for it.

About the data

Jobspiq is a job search platform for tech professionals in India. It checks multiple sources about every 30 minutes and publishes free monthly data on the tech job market. Dated copies of the data are on GitHub, and the live datasets are at jobspiq.in/data.

Are these numbers close to what you're seeing in your own search? Tell me in the comments.

How My Frustrating Job Search Led Me to Build an AI Job-Matching Platform

Jaydeep Goswami — Sat, 18 Jul 2026 15:17:37 +0000

A few months ago, I was searching for a backend engineering job.

Every day looked the same:

Open LinkedIn
Open Naukri
Search for Python jobs
Open dozens of tabs
Read every job description
Apply
Repeat

The frustrating part wasn't finding jobs.

It was finding the right jobs.

I kept getting recommendations for roles that technically matched my resume because they contained words like Python, Backend, or API, but after reading the description I'd realize they wanted a completely different skill set.

I started wondering:

Why are job boards still matching keywords instead of understanding what a developer actually knows?

That question eventually turned into a side project called Jobspiq.

The Problem

Imagine these two jobs:

Job A

Python
FastAPI
PostgreSQL
Redis

Job B

Java
Spring Boot
Oracle
Kafka

Both are "Backend Engineer" roles.

A keyword-based system often treats them as similar.

As developers, we know they're not.

What I Built

Instead of matching keywords, I built a system that compares a developer's profile with a job description to understand how well they actually fit.

The platform:

Checks multiple sources about every 30 minutes: job portals, company hiring systems and remote job boards.
Removes duplicate postings.
Gives every job a Match Score against your profile, showing the skills you have and the ones you're missing.
Sends alerts for strong matches, usually within a minute of finding them.
Helps track applications in one place.

The goal isn't to show more jobs.

It's to show fewer, better ones.

I also check whether the matches are any good. In a weekly check on 140 hand-labelled candidate–job pairs (12 October 2026 run), 88% of the jobs that would trigger an alert were judged relevant. It's a small sample, and I explain the method and its limits here.

What I Learned

Building the product taught me something interesting.

Writing the software was the easier part.

Helping people discover it is much harder.

That's why I'm starting to build in public and share what I'm learning along the way.

If you've ever built search systems, recommendation engines, or developer tools, I'd love to hear your thoughts.

I'm writing up how it's built, part by part, in a series on Hashnode: Building Jobspiq.

Jobspiq is in beta, and every feature is free with no card needed: jobspiq.in

Feedback is always welcome.