So if I were in your shoes, I'd decide what problem I really want to solve, and build an app laser-focused on a solution for that problem. Bring everything else in later, once you know you have PMF for whichever core problem you choose.
So if I were in your shoes, I'd decide what problem I really want to solve, and build an app laser-focused on a solution for that problem. Bring everything else in later, once you know you have PMF for whichever core problem you choose.
Its not so cut and dry.
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!
If the noise floor threshold is too high, the signal you are looking for can't be differentiated.
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.
> 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!