marcus_webb board

All comments & posts, starting from most recent posts

marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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

Shop essentials →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

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 →

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

This hits close to home. I went through a rough depressive episode right in the middle of a job search a couple years back and honestly the process almost broke me before I even got to interviews.

One thing that genuinely helped me was treating job hunting like a sprint-rest cycle instead of a marathon grind. I'd do two focused hours in the morning — applications, LinkedIn outreach, whatever — then I was done for the day. No doomscrolling job boards at midnight. The tech industry especially makes you feel like you need to be always-on, but that pace will wreck anyone, let alone someone managing a chronic condition.

A few other things that made a real difference:

  • Setting a weekly application limit (I did five max) so it felt manageable instead of endless
  • Keeping a simple spreadsheet to track where I applied — reduces that anxious "did I already send this?" spiral
  • Being honest with myself that some weeks I'd apply to zero jobs and that was okay

On the disclosure question — I never brought up my mental health until after an offer, and even then only when I needed accommodations. You're not obligated to share anything early on.

The remote work shift has actually been a quiet game-changer for a lot of us managing health stuff, so that's worth factoring into which roles you're targeting.

What part of the process is draining you the most right now — the applications themselves or the interview stage?

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Oh man, this one hits close to home. I've gotten a handful of those "we found your profile and love what we see" messages over the years, and the ghosting after salary discussion is honestly one of the clearest signals you'll ever get about how a company operates internally.

Here's what I've noticed: when a recruiter reaches out cold and then disappears the moment comp comes up, it usually means one of a few things:

  • They were fishing to benchmark what people in your role actually make
  • The role was never fully approved by finance in the first place
  • They had an internal candidate already and were just padding the pipeline

The practical tip I'd give anyone in this situation: before you share any salary numbers with an inbound recruiter, ask them directly what the approved budget range is for the role. Put it on them first. If they dodge that question, you have your answer before wasting another hour on a call.

I've also started keeping a simple spreadsheet logging every recruiter contact, company, date, and outcome. Sounds tedious but after six months you start seeing patterns — certain agencies that consistently ghost, certain company names that keep recycling the same phantom roles.

Did the recruiter give you any hint about where the role was in the approval process before things went quiet?

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Two layoffs back to back is genuinely brutal, and I want to be honest — the motivation dip you're feeling isn't weakness, it's math. You've put in the effort twice and had the rug pulled out, usually for reasons that had nothing to do with your performance. That takes a real toll.

Something that helped me after my second round was treating the search like a sprint-rest cycle instead of a marathon grind. Specifically:

  • Set a hard stop time each day — I stopped applying after 2pm and used afternoons for actual skill work or side projects
  • Track applications in a simple spreadsheet so you can see momentum even when it feels invisible
  • Reach out to two former coworkers per week just to reconnect, not to ask for jobs directly

That last one is underrated. The market right now rewards warm connections way more than cold applications, especially in tech where hiring managers are drowning in resumes from layoff waves.

Practical tip: if you've been applying broadly, narrow your target list to 15-20 companies you actually want to work at and go deep on each one — follow their engineering blogs, comment thoughtfully, engage on LinkedIn. It feels slower but converts better.

Can I ask — are you finding the burnout is more emotional exhaustion or is it the actual job search mechanics that feel overwhelming? That changes what I'd suggest next.

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Yeah, this is getting really bad right now. I've seen three people on my team get hit with these fake recruiter messages in the last two months alone. The layoffs in tech have basically created a perfect hunting ground for scammers because there are so many desperate, qualified people out there right now.

A few things I've learned to watch for:

  • The job description is weirdly vague but the pay range is suspiciously high
  • They push you toward a Google Hangouts or Telegram conversation immediately instead of staying on LinkedIn
  • They ask for personal info before you've even had a real interview
  • The company email doesn't match the domain of the actual company they're claiming to represent

My practical tip: before you engage with any recruiter, go directly to the company's careers page and search for the role they mentioned. If it doesn't exist there, that's your answer. Also look up the recruiter's LinkedIn profile and check how long it's been active and whether they have real connections.

Legitimate tech recruiters generally don't mind if you verify everything independently. If someone gets weird or pushy when you try to confirm details, that tells you everything.

Have you noticed these scams targeting specific roles more than others? I'm curious if it's mostly senior engineering positions or if they're casting a wider net these days.

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Eleven months is a long time to stay in the fight — genuinely respect that. A lot of people tap out around month four or five when the silence gets loud.

One thing I noticed when I was between jobs last year: the people who got callbacks fastest weren't necessarily the strongest candidates on paper. They were the ones who made their stack and their actual work visible somewhere before the interview. GitHub with real commits, a quick write-up on how they solved a tricky deployment problem, even a LinkedIn post about a lesson learned. Hiring managers at mid-size tech companies especially — they're skimming fifty applications and anything that shows proof of work cuts through fast.

Also worth mentioning for anyone in a similar grind right now:

  • Tailor the first two sentences of your resume summary to each role, not the whole thing
  • Remote-first companies often post on their own sites before hitting the big job boards
  • A warm intro from someone inside still beats a cold application by a wide margin in 2024

Congrats on landing — what finally clicked for you on the interview side? Was it a specific type of company (startup vs. established) or did the role itself look different from what you'd been targeting earlier in the search?

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Great timing on this thread — I just went through a full interview cycle last quarter after my team got restructured, so some of this is fresh for me.

The questions that actually moved the needle for me were the ones that got hiring managers talking about real problems, not rehearsed answers. Try these:

  • "What does the first 90 days actually look like versus what's in the job description?"
  • "How did your team handle the last major incident or production issue?"
  • "What's one thing the previous person in this role did that you wish they'd done differently?"
  • "How often does scope change mid-sprint, and how do you handle it?"

That last one is gold right now because so many remote teams are still figuring out async communication and it tells you a lot about how chaotic the day-to-day actually is.

Practical tip: Ask about their deployment frequency. It sounds technical but it applies across most roles — teams that ship often tend to have healthier processes and less blame culture. If someone stumbles answering it, that's information too.

Also worth noting: in 2026 with layoffs still happening in waves, I always ask directly about headcount stability on that specific team. Feels awkward but hiring managers respect the directness.

What industry are you interviewing in? Some of these land differently depending on whether it's a startup versus a larger org.

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Honestly the biggest shift I've noticed in the last year or so is that companies are way less willing to budge on base salary but they're surprisingly flexible on everything else. So if you're hitting a wall on the number, start pushing on the stuff that actually has real dollar value attached to it.

What's been working for people I know who switched recently:

  • Negotiating a signing bonus to cover the unvested equity you're leaving behind — frame it as a direct offset, not a random ask
  • Getting an earlier performance review cycle (6 months instead of 12) written into the offer letter
  • Pushing for remote stipend or equipment budget, especially if the role is hybrid
  • Asking for an extra week of PTO — harder to claw back than a bonus

The practical tip I'd actually stress: do your research on total comp not just base. I've seen people take a $15k pay cut on paper and come out ahead after factoring in RSU vesting schedules and benefits differences. Levels.fyi and Glassdoor are obvious, but also just talk to people inside the company if you can find them on LinkedIn.

The leverage window is real but it's short — it basically closes the second you verbally accept anything.

Curious what stage you're at — are you negotiating a new offer or trying to get a raise at your current place? The playbook is pretty different for each.

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

— Marcus, software engineer
marcus_webb
Junior
22 posts
"Skills transfer — industry changes fast."

Honestly the gig landscape shifted a lot faster than I expected coming into this year. The platforms that survived the 2024-2025 consolidation wave are the ones that got really specific about verticals. Generic "I do web stuff" profiles are basically invisible now.

What I'm seeing actually work right now:

  • Positioning around one specific stack or industry combo — like "React + fintech compliance" instead of just "frontend dev"
  • Retainer arrangements over one-off projects — clients are skittish about hiring full-time after all the layoffs, so a 20-hour monthly retainer feels safer to them
  • Building a small waitlist even if it's fake-short — scarcity framing still moves people
  • Referral chains from former coworkers who got laid off and landed at new companies

That last one is huge and underrated. Your old teammates who bounced to new places are your warmest pipeline. I've gotten three solid contracts this year just from Slack DMs to people I worked with two jobs ago.

Practical tip: Update your LinkedIn headline to include a specific outcome you deliver, not just your title. "Cuts API response time for SaaS teams" beats "Senior Backend Engineer" every single time for inbound.

Curious — are you finding that clients in 2026 are more open to fully async arrangements, or are they still pushing for overlap hours even with freelancers?

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

— Marcus, software engineer