Software Engineer

About ResumeGrade

ResumeGrade helps Indian universities see how ready a graduating batch is for placements. Officers upload the cohort once. They get per-student resume scores, at-risk flags, and batch analytics without anyone on staff reading hundreds of PDFs by hand.

We're early-stage: small team, live product, long backlog. Students use the app to upload resumes, get scored, and edit them. Universities use the portal for cohort views, at-risk lists, and batch review. Both sides ship changes every week.

You're not engineer #47 on a checkout tweak. You ship work placement officers and students touch the next day, then fix what breaks after. Schema to deployed UI, on your plate.

What we build with

Frontend

Next.jsReactTypeScriptTailwind CSSshadcn/ui

Backend

SupabaseNext.jsNodeJSOpenAIAnthropicZod

Infrastructure

VercelSentry

What you will work on

• Ship full-stack features yourself: schema, API route or server action, UI, deploy
• Student app work: PDF/DOCX upload and parsing, rubric scoring, LLM feedback, resume editor
• University portal: cohort dashboards, at-risk flags, batch analytics, department views, advisor workflows
• Supabase migrations, RLS policies, and Postgres functions as the data model changes
• LLM features in production: structured JSON, prompt tuning, resume rewrites, JD matching
• Transactional email with React Email and Resend
• Resume templates and PDF generation (puppeteer-core, Chromium)
• Refactor before small messes become big ones
• Work with the founder on product calls, not just tickets from a backlog
• Help set how we review code, deploy, and measure quality while the team is still small

What we are looking for

• 0 to 3 years shipping real web apps in production, not coursework clones
• Solid TypeScript and React; you know why the code works, not just that it compiles
• Comfortable with databases: queries, indexes, spotting a bad join
• You can take a rough spec or a Figma frame and figure out the build
• Code that's readable without a tour guide. Not clever for its own sake
• Async-first: clear written updates, no hand-holding
• Available during IST or GMT working hours

Good to have

• Something shipped with real users: side project, OSS, or freelance work
• Next.js App Router, server components, server actions
• Supabase or Postgres RLS
• LLMs in production: prompts, structured output, catching bad model output before users do
• Tailwind and building UI without pixel-perfect mocks
• You've fixed someone else's code without making it worse

How we hire

1. 1Application review. We read every resume.
2. 2Short async task. Something small and close to the actual codebase.
3. 3Video call with the founder. Background, fit, your questions.
4. 4Offer