29 karma · joined March 1, 2025
https://github.com/didtheyghostme
Do you automate the whole process? That's really a lot of applications.
> It would be useful to be able to crowdsource a lot of the due dilligence that must be done individually that could easily be automated as well as see the average turnaround time before rejection, and identify job postings that continuously roll (identical and reposted every 3-6 months)
Currently the platform does this! On the company page, you can see job postings split into "Opened" and "Closed" statuses, as well as when people applied and the turnaround time.
I'm also looking into automated approaches like a browser extension which could be useful if more people uses it.
> including if an LLM looks at it first.
Wow, do you have any links / examples of this kind of tracking or have you seen that done anywhere? If it is effective, I think it would be really useful!
The goal is to bring more transparency to the process, so if someone else had received a reply, I could have known sooner and moved on.
You can check out the GitHub repo too if you're interested!
When we submit our application, usually we also submit a resume. Personally, I do add UTM code (e.g. utm_source) to my links in my resume so I know if it was visited through analytic tools like Mixpanel. However, that's assuming that the person viewing the resume clicks on it.
There's also a "Report Job" button in place for flagging invalid job postings, which you could add a note with the reason for reporting.
However, there is a caveat, since this is community-driven so like another commenter mentioned, there could be bad actors. One way to solve that in the future is to have community moderators / some kind of verification.
I actually started this because I wanted to track my own applications but also wanted to solve the problem of making the process more transparent for applicants. Just like the "static HTML" part, a 2 weeks rule is a general guideline, but surely we can do better than that. Especially when there is no recruiters' contact after applying, going beyond a simple yes/no answer by providing community-driven data (historic and current) would help a lot (as seen in the links I cited). Thanks again for the insights!
modern styling - tailwind css
generating pages - haven't tried these but heard of bolt.new , v0.dev being popular
Though I feel this only works well for tech that are widely used.
It was frustrating to apply for jobs, with no rejection emails and no updates, not knowing whether to keep waiting or move on. The plan is to answer questions like:
1. Has anyone heard back from this role?
2. How long does it usually take to hear back?
3. What are the online assessments/interview rounds like for company X?