marcus_webb board

All comments & posts, starting from most recent posts

marcus_webb
Newbie
9 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
Newbie
9 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
Newbie
9 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
Newbie
9 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
Newbie
9 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
Newbie
9 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
Newbie
9 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
marcus_webb
Newbie
9 posts
"Skills transfer — industry changes fast."

Hey everyone, Marcus here. I've been in tech for about twelve years now, mostly backend and cloud infrastructure, and after my second layoff in three years I finally made the jump to full-time freelancing back in late 2024. Figured I'd share what I'm seeing on the ground in 2026, because honestly a lot of the advice floating around still reads like it was written in 2019.

The Gigs That Are Actually Paying Well

I'll be straight with you — not everything in the freelance market is thriving. Short-term content gigs and basic web builds have gotten brutally competitive and the rates reflect that. But a few areas are genuinely strong right now:

  • AI integration work: Companies want engineers who can wire AI tools into their existing systems. If you know your way around APIs and can work with Python or TypeScript, there is real money here.
  • Cloud cost optimization: Businesses scaled up fast and now they're panicking about AWS and Azure bills. Freelancers who can audit and fix that are getting repeat contracts.
  • Fractional engineering leadership: Startups that can't afford a full-time CTO or engineering manager are hiring experienced people on a part-time retainer basis. This has been a game-changer for me personally.
  • Security and compliance consulting: With more remote teams and data regulations tightening, this niche keeps growing.

How Remote Teams Are Changing the Client Relationship

One thing I didn't expect was how much easier it is to land international clients now. Remote work normalized async communication, so a startup in Berlin or a scale-up in Toronto doesn't blink at hiring a freelancer based in the US. That opens up your market significantly. The catch is you have to be really good at written communication and setting expectations upfront. Clients who are used to distributed teams will drop you fast if you go quiet for 48 hours without a heads-up.

What I've Learned About Switching From Salaried to Freelance

The hardest part isn't finding clients — it's the mental shift. When you're at a company, someone else is handling sales, admin, and your benefits. When you freelance, that's all on you. A few things helped me make the transition smoother:

  • Line up at least one anchor client before you quit your job. Even a small retainer changes everything psychologically.
  • Treat your rate like a product price, not a salary negotiation. Research what the market pays, not just what feels comfortable to ask for.
  • Build a simple system for tracking invoices and expenses from day one. I ignored this early on and it cost me real stress come tax time.
  • Keep your skills current. The stack that got you hired two years ago may not be what clients are searching for today.

Finding the Right Opportunities

One thing that's helped me stay visible is keeping my profiles updated on job boards that also cater to contract and freelance work. If you haven't already, it's worth browsing CareerPlace's job search — there's a solid mix of contract, part-time, and project-based listings alongside full-time roles, which is useful when you're trying to build a pipeline rather than land one job.

The Honest Reality

Freelancing in 2026 is not passive income and it's not a side hustle fantasy. It's running a small business. The upside is real flexibility, better hourly rates if you position yourself well, and no more waiting to see if your name is on a layoff list. The downside is income can be lumpy and you carry all the risk yourself.

So I want to hear from this community — whether you're a freelancer, considering the jump, or an employer who hires contractors. What is actually working for you in the gig economy right now, and what has completely flopped? Drop your experience below.

Products people often ask about

Shop essentials →

— Marcus, software engineer
marcus_webb
Newbie
9 posts
"Skills transfer — industry changes fast."

Hey everyone, Marcus here. I've been in tech for about eleven years — mostly backend work, some team lead stuff, a little cloud infrastructure. I got laid off four months ago and I want to be honest with you all because I feel like nobody talks about the real emotional weight of a job search until it's already crushing them.

The Job Search Was Breaking Me

I applied to somewhere around 80 positions over the first two months. I optimized my resume. I practiced system design questions until I could answer them in my sleep. And the rejections still kept coming — or worse, total silence. I started waking up at 3 a.m. running through everything I might have done wrong. My partner noticed before I did. She started walking on eggshells around me, and I felt this overwhelming guilt every time she paid for dinner or covered a bill without saying a word about it. That guilt turned into shame, and shame made the depression worse. It was a cycle I couldn't break.

Why I Turned to Freelancing

A former coworker reached out about a short contract — three weeks, Python-heavy, remote team based in Austin. I almost said no because I thought taking it would somehow signal that I'd given up on finding a full-time role. That thinking was wrong. Taking that contract was the best decision I made. It gave me income, yes, but more importantly it gave me structure and a reason to open my laptop that wasn't just refreshing job boards. The guilt in my relationship started to ease because I was contributing again, even if it wasn't the stable W-2 situation either of us wanted long-term.

What Freelancing Actually Looks Like Mid-Career

I want to be real — freelancing in tech at this level isn't the same as it was ten years ago. Clients expect you to hit the ground running. You're often dropping into a codebase you've never seen, working with a remote team across three time zones, and delivering something useful before they've even fully explained the project. It's not for everyone, but if you've got the stack depth and you can communicate clearly, you can make it work. I've picked up two more short contracts since that first one.

  • Start with your existing network before cold-pitching platforms
  • Be upfront about your availability and rate — lowballing yourself leads to resentment fast
  • Treat each contract like an audition for a longer relationship, not just a paycheck
  • Block time for your actual job search so freelancing doesn't become avoidance
  • Talk to your partner or whoever is in your corner — the isolation makes everything worse

The Mental Health Part Nobody Posts About

I'm not going to pretend I'm fully out of the dark. Some mornings are still hard. But having work — even contract work — gave me something to point to. It changed the conversation in my relationship from "when are you going to find something" to "how is the project going." That shift mattered more than I expected. If you're in the middle of a brutal search right now and you're feeling the same guilt and low-grade depression I was, please know you're not alone and you're not failing. The market is genuinely difficult right now and that's not a reflection of your worth.

If you're ready to start exploring what's out there — full-time, contract, or somewhere in between — search open roles on CareerPlace and filter by remote or contract to see what fits your situation right now.

Let's Talk About It

I'm curious how others are handling this. Have you turned to freelancing or gig work during a job search to keep yourself afloat financially and mentally? Did it help, or did it make the full-time search harder to stay focused on? Drop your experience below — I think this community needs this conversation.

Products people often ask about

Shop essentials →

— Marcus, software engineer