Hey folks. Rolepad is a product born out of my dissatisfaction with hiring processes - both as a candidate and as a hiring manager. Processes that are non-transparent, inefficient, and full of frustration for both sides. This early iteration has focused on the application tracking aspects with a few extra goodies.
These days it is common to apply to dozens of positions (some users track over a hundred opportunities). Without a record-keeping system, it can quickly become an unmanageable mess. Even the better-organized among us often end up juggling spreadsheets, emails, and various notes. Rolepad was built to keep this data (company facts, role details, interview stages, contact info, freeform notes, follow-up actions, and more) in one place. Some of the other neat additions:
- Forward emails to save@rolepad.com to save them as notes connected to specific opportunities. Forward recruiter messages to no@rolepad.com to have the system automatically reply with a decline response.
- Generate shareable Sankey charts of your progress like this: https://app.rolepad.com/metrics/6QEbaktB7bqR8glhuYR32
- Submit anonymous reviews and insights about application/interview/offer processes at a company . This is new and there aren’t great examples to share yet (https://rolepad.com/companies/brilliant.org is an early glimpse), and I didn’t want to create fake data as a matter of principle.
Oh yeah, and it’s totally free :) Creating an account is passwordless and takes seconds, but if you want to kick the tires even faster, I created test credentials for this occasion:
username: test@rolepad.com
password: hntest
With this release, I am also starting conversations with employers (
https://rolepad.com/employers). A unified platform for candidates and employers can significantly reduce frustration for both in ways that email cannot. I should note that any solutions here have privacy implications and will require an exceedingly thoughtful execution.
And now for the tech stack. The main application uses React with Tailwind on the frontend, C# on the backend, hosted in AWS (App Runner, Lambda, RDS Postgres, SES), with auth provided by Google Firebase, and CI/CD via GitHub Actions. The home page is actually an SSR (server-side rendered) application built with vite-plugin-ssr (now vike) and hosted in a Cloudflare Worker that hits the AWS-hosted API. This is basically a best-of-all-worlds SSR configuration - very fast, zero cold start (!), and essentially free.
Any and all feedback is sincerely appreciated!
> These days it is common to apply to dozens of positions (some users track over a hundred opportunities).
Honest question: is it that common? I'm an average software engineer in Western Europe. When I was junior (around 2010-2015) I usually got a job after submitting ~3 job applications (mainly, because I was accepting anything at that time). Nowadays, since I have more experience, whenever I want to switch my job, I know exactly to what kind of company I want to apply to, this means I don't send a dozen applications; rather I send usually 1 or 2. But I do my investigation on that 1 or 2 companies I'm applying to. And I never interview with more than 1 company at a time (it would be very stressful for me).
So, I've never had the struggle of "keeping track" of job applications. I've never worked for FAANG, though (not sure if this has anything to do). I thought my situation was more common, but based on your statement perhaps it's not.