They're all engineering managers generous with their knowledge worth following (I do!) - save for @ebiatawodi who is a product director you should follow :)
If there's one piece of advice I can give to managers with junior-heavy teams: be realistic. Convey this realistic thinking upwards.
Yes, less experienced engineers do learn, and learn quickly. But don't expect miracles like shipping faster, or shipping reliably.
Stay grounded.
Two other contributors I missed mentioning: @__mharrison__ shared his take on (virtual) classroom training and @jstanier mentioned a very cool idea their org does at Spotify on "great for starters" task.
Sorry for missing out, and here are few great thoughts from them:
• • •
Missing some Tweet in this thread? You can try to
force a refresh
More well-known, high-paying companies like Stripe, Twitter, Shopify, etc offer remote positions. Many engineers I know apply, and expect to get interviews at these places. Then get sorely disappointed.
Here's what happens and why it's very competitive even to get an interview:
1. The competition for these places is incredible. They get huge amounts of inbound. Surprise - it's not just you who wants to work remotely at Stripe! Typically thousands of inbounds for some positions.
2. Your current residence. Contrary to popular belief, these companies do not hire in all countries: only in ones they have entities. This typically means US, UK, and a few EU countries. If you're not based in ones they have entities, you're probably out of luck unless...
From an engineer: "I want to do side projects but I'm holding off because of my employer contracts that claim all IP I do at or outside work goes to my employer. What is your take on this?"
There are two major problems with your thinking:
1. If you never start, you will never learn or get to scratch your itch. If you have the bug to do it: do it!
2. On the IP. If you want to build a sideproject for fun: do it! I never worried about Microsoft claiming my Flashlight app or Cocktail site for themselves.
BUT:
3. IF you really are starting a business, you *should* be careful. If it is relevant with what your company is doing, it could fall into the IP. But this is not the "fun sideproject" category.
Either do it in stealth (most people do it), or do it in the open.
A perspective I learned about big tech internships when I was a hiring manager:
Internships are, fundamentally, a very expensive recruitment exercise that big tech does, to place "holds" on the most promising graduates, before those people graduate and start to look for jobs.
As a hiring manager, your goal is to *get interns to return* 1-2 years later.
You pay them top dollar. Do lots of stuff to make them feel great - events+perks new joiners don't have. By the time they'd be really productive, they leave.
There's no more expensive way to hire.
So why do companies do it?
1. B/c they believe they will hire the best of the best out of college.
2. Because they want to hire #1 before their competition does.
3. Because they can. They have the money/resources.
4. (Ok, it's great for morale both for the teams and interns)
Let's talk about high-growing startups or publicly traded companies who have a good (tech) brand, but do not issue equity for most software engineers (e.g. below the software engineering level).
I'll start, and please add ones you know of in the comments:
It's becoming harder and harder to justify that you are a tech company hiring great people if you are venture-funded/publicly traded and do not issue equity to all tech workers (engineers, PMs, designers etc).
Especially as most competitors do give this kind of equity.
Stack Overflow Jobs is shutting down spring 2022. Existing clients have been briefed: public comms is not yet out. There will likely be another product following from SO: stay tuned.
In the meantime, here are other job boards you can consider posting engineering positions: