Budget guidelines

// Tell me the budget first

Share the budget or hourly rate

A range is enough.

Please include a budget or rate range in your first message. I need that before discussing a role or project, so we can see whether it's a fit.
Full hiring requirements
Details and examples

How not to reach out

Every now and then, a conversation goes like this:

[13:00] Recruiter: Hi, are you interested in this job [DETAILS]
[14:40] Me: Hi. Thanks for reaching out! What is the approximate budget or hourly rate?
[14:55] Recruiter: It depends on the project and position. I can't give you a specific number.
[15:30] Me: I'm not interested if I don't know the budget or hourly rate.
[15:50] Recruiter: This job is really good, and we're sure they would offer you a worthy rate.
[17:25] Me: I'm still not interested without knowing the budget or hourly rate.
[17:30] Recruiter: Approximate budget is $XX,XXX to $XX,XXX. Hourly rate is $XX to $XXX.
[18:35] Me: My final answer: yes or no.

Result: 5+ hours of back-and-forth for nothing.

How to reach out

[13:00] Recruiter: Hi, are you interested in this job [DETAILS]. Approximate budget is $XX,XXX to $XX,XXX. Hourly rate is $XX to $XXX.
[13:30] Me: Hi. Thanks for reaching out! Yes, I am interested. How do I get started?

Result: 30 minutes, and both of us know where we stand.

When I consider an offer

I am interested in job postings when:

  1. It's a .NET project and you specified the rate or budget
  2. Someone recommended the job or company
  3. Someone recommended the person who posted the job
  4. Someone recommended me to contact the person who posted the job

I do not proceed with any offer until I know the budget or hourly rate.

Why this matters

Knowing the range early saves us both a long back-and-forth.

Chasing a job without knowing the pay is like shopping for a car on a fixed budget with no price tags.

Recommended reading

"Do They Deserve The Gift Of Your Keystrokes?" by Scott Hanselman
Back to the homepage