"Networking?" Yeah; passive understanding of what other teams are working on, their challenges, and who the players are in situations likely one or two degrees from oneself helps find out how to get X accomplished when you need it done.
-
Show this thread
-
Speaking of incentive systems: a major internal cultural milestone is "shipping" what your team has been working on. It has the usual meaning *plus* a one page writeup, distributed to basically the entire company via email.
1 reply 3 retweets 30 likesShow this thread -
I love shipped emails. In addition to frequently being great pointers to other written documents (as the folks who've been geeking out on e.g. database snapshot optimization for the last N weeks crank out a research paper, complete with references), they're great for morale.
2 replies 2 retweets 20 likesShow this thread -
(They also get piped to a Slack channel, which encourages folks to react to them with emojis. Lowering the bar to praising colleagues' work is underrated.)
1 reply 1 retweet 52 likesShow this thread -
We aspire to have career paths in place for engineers (and other folks) to increase in impact without having to do the traditional transition into management. These are written down, so that folks can have explicit examples of what to do and how to calibrate on success.
1 reply 0 retweets 25 likesShow this thread -
(If you want engineers to program and mentor but only score/promote/etc them based on story points per quarter then you will experience a persistent shortage of great mentors. So that expectation is on a written rubric, which are broadly available.)
2 replies 4 retweets 15 likesShow this thread -
(This also lets folks at higher levels of seniority specialize a bit in where they get leverage, whether that's bringing projects in, improving technical practices across broad swathes of the org, mentoring, producing broadly useful artifacts, moving industry forward, etc.)
1 reply 0 retweets 8 likesShow this thread -
I have very strong opinions about engineering hiring, which is unsurprising given that I ran a company about it. I think the single biggest improvement most companies could make, tomorrow, is writing a rubric for interviews and then grading against it. IRL example in the guide.
2 replies 2 retweets 24 likesShow this thread -
I'd encourage you to read the rest of the guide. If this broadly sounds like an engineering culture which is interesting, we are hiring *a lot of people*.https://stripe.com/jobs
6 replies 3 retweets 21 likesShow this thread -
Replying to @patio11
I've looked longingly at a bunch of the backend/data/infra postings Patrick, but unfortunately only a couple eng positions are listed as Remote category. Do you know if any of the Foundation Eng are remote-friendly/first teams? Thanks!
1 reply 0 retweets 0 likes
Foundation is *heavily* remote-friendly IIRC. We're working on making that clearer in a systematic fashion on the site, but easiest way is to either ask me about a specific one and I'll ferret out the answer or apply and tell the recruiter about your location requirements.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.