I really appreciate that I can use it without needing a business or work account. A lot of people want to analyze job data even if they aren’t a business or currently employed, and this approach makes it much more accessible.
I also like that the pricing is published up front with no sales call required. The fact that credits roll over for 12 months, along with cancel-anytime billing, makes it genuinely workable for a self-funded project—not just for teams going through a procurement process. Review collected by and hosted on G2.com.
The web app doesn’t feel built for analysis so much as for lookup. There’s no way to apply include/exclude keyword logic across job descriptions, and exports are capped at 200 jobs per company. So if you want to do any real study, you end up pulling records into a local database and doing the analysis there. That’s fine once you understand the limitation, but nothing in the product makes it clear up front.
The API has a similar documentation gap. Broad queries—like many OR title terms over a long date range, especially with include_total_results—don’t return an error; they just hang until they time out. That comes across as a broken product rather than an expensive request. Time-bucketing is the workaround for both that issue and deep pagination, but I lost a working session figuring it out empirically. A simple “how to pull a large corpus” page would have prevented that.
One smaller thing: API credits recharge in full every time you re-run a query, while company credits give 90 days of unlimited re-access after a single reveal. The part of the product that’s meant for iteration is the one that penalizes iteration. Review collected by and hosted on G2.com.