[dtgmzac]

Really appreciate the honest and straightforward feedback. You're right that the community-based features are definitely hard to be useful without a community. It's actually one of my main problems right now, exploring who my target audience is and what the main goal should be before the next iteration.

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!

[pogue]

I wonder if you could implement some features used by the advertising industry and when you submit an application, include a tracking pixel/web beacon that would trigger when your application was viewed and returned some analytics like if it was viewed in an email client or web browser. You would then be able to see what's going on with the other end of your job application.

[dtgmzac]

Interesting idea! I'd love to know if that's possible too.

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.

[pogue]

What format do you submit your resume in? In a doc or PDF you should theoretically be able to load an externally accessible beacon. Depending on how the person is viewing it, you could get some interesting results, including if an LLM looks at it first.

[dtgmzac]

PDF format.

> 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!

[pogue]

I kind of went down a rabbit hole trying to figure out how to do this in the modern era. It might be easier to send it via email or some other method.

[trod1234]

The issue with community-based/crowdsourced features as well is that you inevitably have some bad actors that join up to poison your features.

If the noise floor threshold is too high, the signal you are looking for can't be differentiated.

[dtgmzac]

Great point. A moderation system or verification features could definitely help reduce the risk of fake accounts or bad actors. If this gains enough users, it’s definitely something I'll have to tackle. Appreciate the feedback!