Paste "$45/hr" into TailorFit last week and the app would divide it by 1000 and slap a "K" on it. Forty-five dollars an hour, rendered on screen as "$0K." Nobody wrote that bug on purpose. The formatting logic just had no concept that a job could pay anything other than an annual salary, so it ran salary math on a number that was never a salary.
Where it actually broke
The dashboard computes a median target compensation across your saved applications. One hourly gig in the mix, and its number got averaged in right next to six-figure salaries, quietly dragging the whole "typical target" toward nonsense. Add a job description quoting a day rate and the same thing happened to the auto-filled comp field on the application itself.
None of this was a user complaint. It surfaced during an internal audit, the kind where you actually sit down and look hard at your own product instead of waiting for someone to report it.
Why it mattered more than a formatting glitch
Contract work, consulting, agency gigs, freelance stints between full-time roles: a lot of real job searches include at least one listing that isn't quoting an annualized number. A tool that only understands salary is telling anyone in that situation, without saying it out loud, that they weren't really who it was built for.
We'd just published a post about supporting every career path, not only software engineering. Making that case while our own comp fields silently assumed one lump annual number for everyone would have been embarrassing.
What shipped
Every application now carries an explicit pay type: salary, hourly, or contract. The form has a toggle that changes field labels and units to match, so a "Rate min" priced in dollars per hour looks like what it is.
The real fix is upstream. When you paste a job description, the AI analysis now identifies whether it's quoting a salary, an hourly rate, or a day rate, and carries that forward. The auto-filled comp field matches what the posting actually said, in the right unit, without you correcting it afterward. And the salary-target dashboard now only averages actual salaried roles, so an hourly gig you're tracking on the side stops skewing a number meant to represent your salary search.
What's still rough
Offer evaluation still labels its main field "Base salary" with no unit selector. Evaluate an hourly or day-rate offer there today and you'll need to type the number as-is, knowing our AI reads it as free text rather than doing unit conversion for you. It works. It's just not as polished as the rest of this yet.
Better to say that plainly than let you find out by getting a strange answer back.