How I built NexeraAI, an AI career platform built on real job listings

By Shivam Anil Jha · AI architect & full-stack developer, Mumbai ·

The NexeraAI home page: a job search box, an upload-your-résumé button and a dotted globe
NexeraAI's home page, live at nexera-ai-xi.vercel.app.
What
An AI career platform: jobs, résumé analysis, referrals and learning roadmaps
Built with
Next.js and TypeScript, PostgreSQL with Prisma, Auth.js, Tailwind CSS
AI
One small client for Groq, Google Gemini and OpenAI
Live at
nexera-ai-xi.vercel.app

NexeraAI is the career platform I have been building since June 2026. You upload your résumé, it reads it, scores it, and shows which open jobs fit you and which skills you are missing. Around that sit referrals, skill-gap lessons with quizzes, a learning roadmap, interview practice, cover letters, a résumé builder and a salary check. Employers can post jobs on it too.

The AI gets the attention, but most of the work went into two plainer problems: getting real, clean job listings, and making sure the AI never fills a gap with something made up. This post is about both.

Where the jobs come from

An AI career site without real jobs is just a chat window. So the first thing I built was an importer. It reads listings from public sources: RemoteOK, Arbeitnow, and the public job boards that companies run on Greenhouse, Lever and Ashby. Three more, Adzuna, JSearch and Jooble, switch themselves on when their API keys are set. Each source is a small module that returns the same raw shape, so adding a new one doesn't touch the others.

Every source formats things its own way, so each listing goes through one normaliser before it is saved:

The same job, five times

Popular roles are posted on several boards, and nobody wants to scroll past the same opening five times. The importer deals with that in three steps:

  1. Same source, same ID as a job already saved: update it in place, so its page address never changes.
  2. Different source, same job: skip it. The check is a SHA-1 hash of the title, company and location, lowercased and with spaces collapsed, so “Senior  Engineer” and “senior engineer” match.
  3. A new job gets a readable address made from its title, company and place, with -2 or -3 added only when two jobs would collide.

Every job is a real page

Each job has its own page under /jobs/, with JobPosting structured data so Google can show it in job search. A posting counts as valid for 30 days from the day it was posted. The dashboard, the API and the sign-in pages are kept out of search in robots.txt, so only the public pages get indexed.

Running the import on Vercel

The import starts from a scheduled call to an endpoint that needs a secret. When Redis is available, the endpoint puts the run on a BullMQ queue and returns. When it isn't, it answers at once and keeps working in the background with Vercel's waitUntil. That second path exists because some external cron services stop waiting after about 30 seconds, and an import can take longer than that. Without it, a run that worked would still be logged as a failure.

One AI client, three providers

Every AI feature goes through one small client. Groq, Google Gemini and OpenAI all accept the same chat-completions format, so a single code path serves all three. The client tries the providers that have a key, in order (Groq with Llama 3.3 70B first, then Gemini, then OpenAI), retries once on a rate limit or a server error, and then moves on to the next.

The rule I care about most is at the end of that client: if every provider fails, it raises a clear error. It never returns sample data. A made-up résumé score is worse than no score, because people act on it.

Each feature asks the model for one JSON object with fixed keys. The résumé analysis, for example, returns a score from 0 to 100, an ATS score, the skills it found, strengths, specific improvements and a short summary. Models sometimes wrap JSON in code fences or add a sentence before it, so a small function strips that and takes the outermost object before parsing. If it still doesn't parse, the error says so.

Reading a résumé

Résumés arrive as PDFs. The server pulls the text out with pdf-parse and keeps the file in a private storage bucket. A scanned résumé is only a picture of text, and the text models can't read pictures, so NexeraAI says that plainly and asks for a text PDF instead of guessing.

An assistant that only suggests real roles

The Nexera AI chat can talk about anything, but it is built for careers. With each question it gets today's date, recent web results when they help, and the open roles on Nexera that fit the question. Its instructions say to recommend only from that list, by exact title, and never to invent a role. The buttons under an answer are plain search queries, so a tap takes you to real listings.

Job matching works the same way. The model compares your résumé with one job's description and returns a match percentage, the skills you have, the skills you are missing, a fit level and a short explanation. I asked for the missing skills and the explanation on purpose: a percentage alone doesn't tell you what to do next.

The stack

What I would tell someone building one

Start with the data, not the prompts. Clean listings, no duplicates and page addresses that never change made every AI feature after them simpler, and they are also what search engines see. And decide early what the product does when the AI is down. For NexeraAI the answer is to say so.

Shivam Anil Jha is an AI architect and full-stack developer from Mumbai, India. He builds NexeraAI, Clonix and Orbit OS, and co-founded the product studio Sqaron Technologies. More about him.

← All posts · Shivam Anil Jha's portfolio