DEV Community

Cover image for Devs are inspecting Greenhouse payloads to find hidden salary caps
Aditya Agarwal
Aditya Agarwal

Posted on

Devs are inspecting Greenhouse payloads to find hidden salary caps

Next time a job portal asks for your "desired salary," just open your DevTools and you might find the answer sitting right in the payload. Recently, developers have been peeping into application forms. The JSON they hide says far more than the recruiter ever will. 🕵️

The field that pretends to ask

Here's how it goes. You complete an application on a platform such as Greenhouse. There is a box that says: "What are your salary expectations?" It seems non-threatening. It seems like a direct question. No, it's not. Pop open the network tab, watch the request fire, and sometimes you'll spot a number the form never showed you. An upper limit. A maximum threshold. The actual budget hidden in the reply.

Guess high, disappear

In certain systems, candidates are automatically filtered out if they mention a number above the predefined budget threshold. You enter a number, which is then compared to an invisible limit.

If your price is too high, you will simply disappear. No return call, no explanation that they chose someone else, just radio silence.

The question was never asked with good intentions. It was a snare disguised as interest.

Consider the implications of that. They have all the information. You're the only one who has to guess.

Leaky frontends are doing the work laws couldn't

This is what I actually find funny. We spent years discussing pay transparency, but what made a difference was poorly written client-side code.

The number was meant to be kept on the server. But instead, someone sent it to the browser.

→ The "desired salary" box is a filter, not a conversation.
→ The budget often exists before you apply.
→ The frontend sometimes hands you the answer for free.

Companies patching these leaks are telling on themselves. If the industry were a fair playing field, there would be no secrets to keep.

These leaks expose the bias, so of course they rush to fix them.

What this changes for you

I'm not going to pretend inspecting payloads makes you a hacker. It's the network tab that you get with every browser. But knowing the game changes how you play it. If a portal is silently comparing numbers to a wall, you want to know where the wall is. Not every form leaks. Some companies handle it elegantly, server-side, so you don't notice anything. But the question is weaponized. Now you know why it feels off. The box that asks about your value may have a good idea of what it's willing to give you. Have you ever exposed the DevTools on a form and found something you shouldn't have? Share the payload inside.

Top comments (0)