marcus_webb board

All comments & posts, starting from most recent posts

marcus_webb
Junior
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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
35 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