Stop giving recruiters your target salary on phone screens. Use this exact phrase instead.

We have all been trapped in that awkward standoff during the initial 15-minute recruiter phone screen. You have a great chat, vibes are good, and then right around minute twelve they drop the dreaded anchor question: "So before we move you to the hiring manager round, what are your salary expectations?" If you throw out a number too low, you screw yourself out of tens of thousands of dollars before even speaking to the team. If you throw out a number too high, they quietly toss your resume into the reject pile without ever telling you their actual budget. For months I tried dancing around it with wishy-washy answers like "I am open to market rate," and every single time the recruter would press until I choked and blurted out a number that anchored me to the floor.

An executive talent lead gave me the exact phrase to flip the script, and it has completely changed my interview process. The second they ask for your number, pause for a second and say this in a warm, collaborative tone: "I want to make sure we are fully aligned before we take up the hiring team's time with multiple interview rounds. What is the approved budgeted compensation band for this specific headcount?" That sentence works magic because of how it is worded. By using internal corporate terminology like "budgeted compensation band for this headcount," you are subtly signaling that you know how corporate requisitions work. You know finance locked in a specific payroll bracket before the job was even posted, and you are framing the question as saving their team valuable time.

Since switching to this phrasing, I have done 12 recruiter screens. Exactly 10 of them answered immediately with the exact base salary range, and two of those roles were budgeted $20k to $30k higher than what I was initially planning to lowball myself with. If you get a stubborn recruiter who pushes back with "Well, the compensation is flexible depending on candidate experience," do not fold. Just smile through the phone and reply: "Completely understand, what is the approved range for someone who meets the core baseline requirements on the posting?" They fold 95% of the time and give you the number. Stop bidding against yourself before you even get an interview.

Jobadvisor

The core advice is sound, but the post oversells it.

What's right: Getting the employer's range before naming yours is standard negotiation advice. Whoever names a number first usually anchors the conversation, and a recruiter almost always knows the budget. Asking for it is reasonable, and framing it as respecting everyone's time is a good touch.

What to be skeptical of:

• The stats are anecdotal. Twelve screens, "10 answered immediately," and "they fold 95% of the time" is one person's experience, not data. The "$20-30k higher" story may be real, but it's a sample of two.
• It isn't magic wording. The jargon ("budgeted compensation band for this headcount") isn't what works. Asking directly works because recruiters have the range in front of them. The phrase can also come across as rehearsed or slightly adversarial, especially the "core baseline requirements" follow-up, which can sound like you're probing for a lowball.
• Some recruiters won't share. Some companies forbid it, or the range genuinely isn't set. Then you need a fallback.
• Local law matters. Many jurisdictions now require pay ranges in postings or on request, which makes this easier. Check what applies where you're applying.

A more natural version:
"Happy to talk numbers. Could you share the range budgeted for this role first, so I can tell you whether we're in the same ballpark?"

If they still won't budge, don't leave it at "open to market rate." Give a researched range instead, with your target near the bottom of it: "Based on my research and experience, roles like this are typically in the X to Y range, and I'd be looking at the upper half of that depending on the full package." Use Levels.fyi, Glassdoor, or salary surveys for your field and location to set X and Y.

I can help tailor a script to your industry and seniority, or draft a reply for a recruiter who dodges the question.

What are people actually doing when they say they “networked” their way into a job?

I keep seeing networking mentioned as one of the best ways to find a job, but most of the advice seems to stop at “connect with people on LinkedIn.”

That sounds simple until you actually have to message someone you’ve never met.

Sending a stranger “Hi, I’d love to connect” feels awkward when there’s an unspoken reason behind the message: you’re looking for work and hoping the person might know someone hiring.

I’ve been trying to approach it differently by paying attention to people in the same industry, following conversations around the kind of roles I want, and making sure my resume is ready before reaching out. I’ve been keeping different resume versions organized in Kickresume too, because the last thing I want is for someone to ask for my resume and then realize it needs another round of editing.

What still feels unclear is where the actual opportunity comes from.

Some people seem to build relationships naturally and eventually get referred. Others send dozens of LinkedIn messages and never get a response. There has to be more to “networking” than collecting connections.

For anyone who actually got an interview or job through networking, what was the specific interaction that opened the door?

Jobadvisor

Most of the time, it's not a stranger saying yes to a "let's connect" note. The people who "networked their way in" usually did one of a handful of things.

1. They reactivated people who already knew them. This is the most common story by far. A former coworker, classmate, or manager hears you're looking, or hears from you, and says "we're hiring, let me pass your name along." Research on job searching (Granovetter's "weak ties" work is the classic) suggests opportunities often come from people you know a little or haven't talked to in a while, not close friends. If you have a dormant list of 50 people you've worked or studied with, that's usually a better starting point than 50 strangers.

2. They asked for advice, not a job. The cold-message version that gets replies is small and specific: "I saw you moved from X to Y. I'm considering a similar path. Could I ask you two questions about how you made the switch?" People like talking about their own experience, and a 15-minute chat is a low-stakes yes. The job lead comes later, when they say "you should talk to my colleague" or "we actually have an opening on my team." You never ask for the job in the first message.

3. They attached themselves to a specific role. Someone sees a posting, finds an employee on the relevant team, and writes: "I'm applying for the data analyst role. I noticed your team works on X. What's the team like, and is there anything the posting doesn't tell me?" If the conversation goes well, a referral often follows, which usually gets your application looked at by a human instead of sitting in an ATS pile.

4. They showed up where the work is discussed. Commenting thoughtfully on someone's post, contributing to an open-source project, answering questions in a Slack or Discord community, speaking at a meetup, or writing something useful. Later, a message that says "I really liked your point about X" isn't cold anymore. This is slower, but it's the "natural relationship" route you're noticing in others.

5. They used shared-identity groups. Alumni networks, former-employer groups, professional associations, and school clubs have an unspoken rule that people help each other, so response rates are noticeably higher than for pure strangers.

Why some people get replies and others don't:

• Cold outreach with a generic message has a low response rate, and that's normal. Personalized, specific, easy-to-answer messages do much better.
• The ask is small. "Would you be open to a 15-minute call?" beats "Do you know anyone hiring?"
• They follow up once, politely, and say thank you afterward, sometimes with an update ("I took your advice and applied, here's how it went"), which is what turns one chat into an ongoing relationship.

A message that works better than "Hi, I'd love to connect":
"Hi Sam, I saw your talk/post on [specific thing] and found the point about [X] useful. I'm exploring roles in [field] and would love to ask you a couple of questions about how you got into [company/team]. Would you have 15 minutes in the next couple of weeks? Totally fine if not."

On the resume: having a couple of versions ready is smart, but don't lead with it. It should come out only when someone asks or when you're applying through a referral. Leading with a resume makes the message read as an application, which is what makes it feel awkward.

If you tell me your field and the kind of role you want, I can help draft a message or a short list of who to reach out to first.

Rejected because the interviewer called 1 minute early and hung up immediately

I had a phone interview scheduled today for 11:00 AM.

At 10:59 AM, my phone starts ringing. Because I have automated spam/screen call turned on, the phone takes a few seconds to process the call before it actually rings through. I tapped the screen immediately to open the screening chat and accept the call, but they hung up right as I did.

I immediately called the number back, but it went straight to voicemail. I waited 15 minutes just in case the interviewer had something important come up or was planning to try calling me back.

When they didn't, I messaged the recruiter to explain what happened, told them I was still excited to chat, and offered to reschedule whenever worked best for the hiring manager.

A couple of hours later, the recruiter replied saying the hiring manager decided not to move forward with my application. The reason given was that because the call was scheduled for 11 AM and he wasn’t able to reach me at the agreed time, they decided to move forward with other candidates.

It is incredibly discouraging to be disqualified from a role simply because a hiring manager called early and couldn't wait a single minute for a connection to go through. This level of rigidity over a 60-second technical delay makes me feel like I avoided a very difficult work environment.

Jobadvisor

That's frustrating, and the reasoning doesn't hold up. The call came in at 10:59, before the agreed time, and you tried to answer it. You then called back, waited 15 minutes, and proactively offered to reschedule. That's a reasonable, professional response to a technical hiccup.

Is it a red flag about the workplace? Possibly, but I'd hold that loosely. A hiring manager who treats one missed connection as disqualifying, without a single reschedule attempt, may be rigid or dismissive. But there are other explanations: they may have had a strong pipeline and used this as a convenient tiebreaker, or the recruiter may have simplified the reason. Either way, you got a small preview of how they handle minor friction, which is useful information. Just don't let it turn into "I was rejected for nothing." You did nothing wrong here.

One thing you can still try: a short, low-pressure reply to the recruiter, something like: "Thanks for letting me know. I wanted to flag that the call came in at 10:59 and I tried to answer immediately and called back right away. If there's any flexibility for a quick reschedule, I'd really appreciate it. Either way, thanks for your time." Odds are modest, and if the manager has already moved on, it won't change anything. But it costs nothing, and recruiters sometimes advocate when the reason is thin.

For future interviews, a few cheap safeguards:

• Turn off call screening and Do Not Disturb for the interview window, and be sitting with the phone in hand 5 to 10 minutes early. Some interviewers do call early.
• Save the recruiter's number, and ask which number the interviewer will call from so you can whitelist it.
• Send a quick confirmation the day before, and ask if they prefer a specific number or a video link. Video calls avoid this whole problem.

This one is on them more than you. It's worth being annoyed about for a day, then moving on.

Should I just accept reality?

I am 35 year old man with a wife and two kids. My wife occasionally works part time, and I have been the sole provider for my family for a little over a decade.

I love my wife and kids more than anything in the world, but I absolutely HATE my job. I work in manufacturing management and even though I have been doing it forever, each day is worse than the last.

I’d love to do something is public service or hospitality, but there isn’t enough money in those jobs to support my family. I’ve changed companies, but still hate the work.

Should I just accept the reality that I’m stuck working a job I hate, or are there alternatives out there that I haven’t considered? Right now my thought is to just save as much as I can and retire early, but I’d like to spend my days doing something that doesn’t feel like dragging my face across the asphalt.

Thoughts?

Jobadvisor

No, I wouldn't accept it yet. "Stuck in this job or take a big pay cut for public service or hospitality" is a false binary, and there's a lot of space between the two.

Figure out what exactly you hate. You've changed companies and it's still miserable, which suggests the problem isn't one bad employer. It could be:

• the industry (the environment, the product, the pace)
• the management role itself (being the buffer between upper management and the floor, constant firefighting, on-call stress)
• the lack of a sense that your work matters

The answer changes what you should look for. If it's the role, a similar-paying individual-contributor or specialist job might fix a lot. If it's the industry, your management skills can move.

Your skills are more portable than they feel. Running a team, budgets, schedules, safety and compliance, and process improvement all transfer. Some directions that often pay decently:

• Public-sector operations: water and wastewater utilities, public works, transit, municipal facilities, state or federal agencies. Pay is often lower on paper, but pensions, benefits, and stability can close much of the gap. This is probably your best bet for "public service" without wrecking your income.
• Hospitality and institutional operations: hotel or resort operations, university and hospital food service, and stadium or venue operations. Operations managers are valued there, and corporate and regional roles pay better than front-line jobs.
• Healthcare or nonprofit operations: hospitals and large nonprofits need people who can run logistics and facilities, and the work has a visible purpose.
• Adjacent paths: EHS and safety, training and teaching (technical colleges often hire industry veterans), and supply chain or logistics for organizations you'd care more about.

Get the real number. Work out your household's true minimum income, not what you earn now. Then compare total compensation (pension, health insurance, hours, commute), not just salary. Some "lower-paying" jobs look different once you do.

Test before you leap. Use the informational-interview approach we talked about earlier. Talk to three or four people doing the jobs you're curious about and ask what a bad day looks like and what they'd earn at your level. Cheap tests beat imagining the grass is greener.

Your savings plan is still good, but change the goal. Retiring early is a long, grim road if every day feels like asphalt. Instead of only saving to escape decades from now, save a 6-12 month runway. That gives you the option to take a pay cut, switch fields, or get through a gap, and it will likely improve how you feel in the meantime.

Also, "each day is worse than the last" is worth taking seriously. If the dread is affecting your sleep, mood, or home life, talking to a doctor or therapist is worthwhile. Burnout and depression can look alike, and it's easier to make a good career decision when you're not running on empty.

What part of the job wears on you most: the people-management, the environment, or the sense that the work is pointless? That would help narrow down which direction to explore first.

Movers Tip Rant

Moved in last week and paid some guys in a truck to move the big furniture and shit.

Paid him in cash and he goes "just so you know, we accept tips"

Seriously bro? Fuck off with that nonsense. I just paid you $160/hr. I literally paid you for your service. We had a CONTRACTUAL agreement before services were rendered on how much your time was worth. Why do you think you deserve more on top of that?

Jobadvisor

The frustration is fair. Saying "we accept tips" right after you hand over cash is a pushy nudge, and if you agreed on a rate up front, you don't owe anything more. Tipping is a custom, not a contract term, and skipping it isn't wrong.

Some context, though. The $160/hr is usually the rate for the whole crew plus the truck, not one guy's wage. If it was a company, the workers often see a fraction of that after fuel, insurance, equipment, and the company's cut. If it was an independent guy with a truck, the rate really is his, and a tip is much less warranted. Movers also do hard physical work, and tipping them is a deeply ingrained norm in the US, typically $20-50 per mover for a half day. That's why he felt comfortable hinting, even if the delivery was awkward.

The real issue is the broader system that ties fair pay to customers' voluntary top-ups, which is what r/EndTipping is about. But that's a beef with the industry, not with the guy who moved your couch. The clean way to handle it is to decide beforehand, tip if the service was good and you feel like it, and not if you don't. A polite "the rate covered it, thanks for the work" ends the exchange without drama.

Did they do a good job otherwise? That might be the deciding factor for whether it's worth being annoyed about.