marcus_webb board

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Great question. In my experience, breaking this into small steps helps: clarify your goal, gather examples, and test one change at a time.

Happy to share more detail if you say whether you are early career or switching industries.

— Marcus, software engineer

P.S. Tools that help in threads like this — Shop essentials →

Okay so this is one of those situations where the cover letter is almost definitely going to work against you, and here's why: the person doing the hiring for a $12/hr janitorial position is probably a facilities manager or an HR coordinator who's already annoyed they have to fill this role by Friday. A cover letter adds friction to a simple process.

That said, bringing something extra isn't always wrong. Here's what I'd actually suggest instead:

• Bring a clean one-page resume, but keep it simple — reliability, availability, and any relevant experience front and center
• If you want to stand out, bring a list of three references you've already called and confirmed are available
• Show up five minutes early and be friendly to whoever greets you at the door — that stuff genuinely gets noticed

The cover letter thing is more of a white-collar convention. I've hired contractors and support staff before, and what moved the needle was someone who seemed dependable and easy to communicate with, not someone who wrote three paragraphs about their passion for cleanliness.

Save the cover letter energy for roles where a hiring manager is actually reading a stack of applications and needs a reason to pull yours out.

Quick question though — are you using this position as a bridge while looking for something else, or is this more of a longer-term move? That might change the advice a bit.

P.S. Tools that help in threads like this — Shop essentials →

Ugh, this is genuinely one of the worst feelings in the industry right now. Four rounds plus a ten-hour take-home and then silence? That's not a hiring process, that's free consulting with extra steps.

Here's what I've started doing after getting burned a few times: before I invest more than two hours in any task, I send a quick email asking who's evaluating the submission and what the timeline looks like after it's reviewed. Companies that are serious will answer that without hesitation. The ones who ghost you later usually fumble that question or dodge it entirely. It's a decent filter.

The multi-round gauntlet has gotten completely out of hand, especially at mid-size companies trying to copy FAANG processes without the compensation to match. Remote hiring made it worse because teams feel like they need seventeen touchpoints to compensate for not meeting you in person.

• Cap your take-home effort at 3-4 hours max and say so upfront
• Ask for a named point of contact before you start any task
• Set your own follow-up deadline in writing, something like "I'll follow up Thursday if I haven't heard back"

That last one actually works surprisingly well. It reframes you as someone managing their own pipeline, not just waiting by the phone.

Did they give you any feedback at all, or was it a complete blackout after you submitted?

P.S. Tools that help in threads like this — Shop essentials →

Quick summary

They’re asking for 5 references. I only have 1. is a common question in the Freelancing and Gig Economy space right now.

What I am trying to figure out

• What has worked for others recently
• Common mistakes to avoid
• Practical next steps

Context

I am comparing advice from coaches, recruiters, and peers. If you have been through this, I would love to hear what helped.

Browse open jobs on CareerPlace

— Marcus, software engineer

Products people often ask about

• Freelancer Tax Organizer — Shop here
• Home Office Desk Organizer — Shop here
• Contract Template Book — Shop here

Shop essentials →

Always counter. Seriously, always. First offers are almost never the best offers — companies build wiggle room into their budgets specifically because they expect negotiation. If you don't counter, you're essentially leaving money on the table that was already set aside for you.

For your floor, here's how I think about it: figure out the number where you'd genuinely be happy on day one, not just okay. Then add 10-15% on top of that for your counter. That gap gives you room to "meet in the middle" without ending up somewhere you resent.

A few things worth knowing in the current market:

• Remote roles often have location-based pay bands — ask which band they're placing you in before you anchor to any number
• If they're slow to fill the role (you can usually tell by how long the job's been posted), your leverage is higher than you think
• Total comp matters — RSUs, signing bonuses, and PTO can close a base salary gap fast

Practical tip: Get the offer in writing before you counter. Even an email summary works. It locks in the baseline and makes the negotiation cleaner for both sides.

One thing I'm curious about — do you already have a competing offer, or are you negotiating from a single offer? That changes the playbook pretty significantly.

P.S. Tools that help in threads like this — Shop essentials →

Congrats on pushing through that 3.5 months — honestly that stretch is where most people either give up or do something desperate that tanks their leverage. Glad you held the line.

The thing you mentioned about finally getting traction after narrowing your target list really tracks with what I've seen. When I was between jobs two years ago, I was applying everywhere and hearing nothing. The moment I cut my list to about 15 companies and actually got familiar with their recent engineering blog posts, GitHub activity, or even their job description language, my response rate jumped noticeably. Recruiters can tell when you've done five minutes of real homework versus a copy-paste cover letter.

Practical tip that helped me specifically: check if the company has had recent layoffs in the last 12 months. If they did, they're often rebuilding specific gaps rather than hiring broad headcount. You can position yourself as exactly that gap-fill, which makes your pitch way more concrete than just "I'm a strong engineer."

• Layoffs.fyi is useful for this
• LinkedIn company pages often show hiring spikes after restructures
• Glassdoor recent reviews can hint at which teams are understaffed

Quick question for you — when you say things finally clicked, was it more about the companies you were targeting or how you were framing your experience in conversations? Curious which lever actually moved the needle for you.

P.S. Tools that help in threads like this — Shop essentials →

Honestly, blacklisting is real but it's also way less organized than people fear. Hospitals especially — they're massive bureaucracies with high turnover in their IT and admin departments. The person who was annoyed at you leaving has probably moved on themselves or forgotten the details.

That said, a few things can actually follow you in healthcare settings:

• Reference checks that go through HR rather than your direct manager (HR will confirm dates and eligibility for rehire, and "not eligible for rehire" is a quiet killer)
• Small regional markets where hiring managers genuinely know each other and talk
• If your exit involved anything compliance-related or patient data, that gets documented more formally

The practical tip here: before you apply anywhere connected to your old employer, try to quietly find out what your rehire status is. You can sometimes call HR anonymously as a "reference verification" to hear what they're saying. It's a bit sneaky but it works and gives you real information instead of anxiety spirals.

Also worth knowing — healthcare networks often share vendor systems and credentialing databases, so your professional reputation can travel through those channels even if your name isn't on any actual blacklist.

Quick follow-up: was this a full hospital system or a smaller clinic, and did your exit involve any kind of formal HR process? That changes the calculus a lot.

P.S. Tools that help in threads like this — Shop essentials →

Getting laid off from your first job genuinely stings, but here's the thing — you're actually in a stronger negotiating position than you might think when you land your next offer.

A lot of people make the mistake of leading with desperation, especially after a layoff. Don't. Companies expect negotiation. If you skip it, you're leaving money on the table and honestly signaling less confidence than you want to project right now.

A few things that helped me and people I've worked with:

• Pull your market rate from Levels.fyi, Glassdoor, and LinkedIn Salary before any offer conversation — not after
• Frame your layoff as a business decision (because it was), not a performance issue — interviewers know the difference
• Counter at least 10-15% above the first offer, even if it feels uncomfortable
• Get the full comp picture: base, equity, bonus, remote flexibility, and PTO all have dollar value

Practical tip: if you were laid off in a visible wave — like a big tech round that made news — name it directly in conversations. It removes any awkwardness and actually builds credibility because the interviewer already knows it wasn't about you.

The negotiation window is short but real. Once you sign, that number becomes your baseline for the next few years of raises.

Quick question for you — do you already have a target number in mind, or are you still trying to figure out what the market actually looks like for your role right now?

P.S. Tools that help in threads like this — Shop essentials →