Inspiration

Most resumes are rejected by Applicant Tracking Systems before a person reads them, and tailoring one to every job takes hours. We built ATS-Ready to do that tailoring automatically, and for this hackathon we added real checkout so the product can take payments.

What it does

Paste a job description or a job-board link and ATS-Ready builds a resume tailored to it from your saved profile, then scores it against ATS criteria. It also writes cover letters and generates interview prep. The free plan includes 3 resumes a month. Pro ($19) and Team ($49) unlock unlimited resumes, cover letters and API access, and are paid through PayPal.

How we built it

  • Backend: FastAPI, PostgreSQL, Redis and an async worker for resume generation. An LLM does the parsing and writing.
  • Frontend: React with Vite.
  • Payments: PayPal Orders v2 over plain REST (no SDK). The backend creates an order, the user approves it on PayPal, and on return the backend captures the payment and grants the plan for 30 days.
  • Hosting: Docker, deployed on Render. Payments run in PayPal's sandbox, so no real money moves.

Challenges we ran into

  • Moving providers: the app was built around Razorpay subscriptions. We isolated billing behind one service, so swapping to PayPal changed only that service, three endpoints and one frontend component.
  • Trusting the redirect: the return from PayPal can't be trusted on its own. The server only captures the exact order it created for that user and checks the order's owner and plan before granting anything, so nobody can redeem someone else's payment.
  • No webhooks on localhost: capturing on return means the plan applies immediately, in dev and in production.
  • Currencies in the sandbox: our first test buyer was an India account and PayPal rejected the USD order. A US sandbox buyer fixed it.

Accomplishments that we're proud of

A full working payment loop on a public URL: sign up, upgrade, pay on PayPal, and come back on the new plan, with the server verifying every step.

What we learned

How PayPal's order lifecycle works (create, approve, capture), why the server must verify what it captures, and how to keep a payment provider swappable.

What's next for ATS-Ready

Recurring PayPal subscriptions, automatic plan expiry (plans are saved with a 30-day end date but not yet enforced), PayPal webhooks as a backup for users who close the tab mid-payment, and live mode.

Share this project:

Updates

Submission history