Looking for a faster way to participate? Take five minutes to fill out this survey.

Why collect stories?

There are so many different ways that folks reach Staff, Principal and Distinguished Engineer roles. As such, I often find that the best career advice for folks pursuing these roles isn't advice at all, but rather the stories of folks who've already done it. Hearing dozens of folks share their map to a Staff-plus role should be far more useful than what any one person has seen at their company.

The StaffEng project is focused on collecting folks' stories of reaching Staff-plus roles and succeeding once they're there.

Sharing your story

Questions? Reach out to @lethain or lethain[at]gmail

If you've reached a Staff-plus Engineer role, then I'd love to include your story in the collection. The process for sharing your story is:

  1. Review the Creative Commons Attribution 4.0 License. By submitting a story to StaffEng, you are agreeing to have it published under this license.
  2. Create a copy of the StaffEng questions, and share your copy, with edit permissions please, to me at lethain[at]gmail
  3. Write your answers into the copied document. Look at the stories so far for reference points. Do not spend more than four hours on this before moving to the next step! Especially if you're an infrequent writer, it's better to submit an early draft for concept editing before you go too far.
  4. Email me letting me know that your story is ready for comments, and I'll review your story. Please include a link to your copied questions document.
  5. If I believe your story would publish well as it stands, then I'll make some line edits and publish it to staffeng.com in an unlinked post. I'll share this unlinked post back to you for final approval before it's shared publicly.
  6. If I don't believe the post is ready to publish, I'll provide concept-level suggestions on the changes that I believe would be necessary for it to be published. It would then be up to you to decide if you'd like to publish it yourself, or if you're up for incorporating the conceptual edits and letting me know once you're ready for another review. If you do self-publish, send me a link and I'll link out to it!
  7. At this point, I'll schedule your story to publish, at which point it will get emailed out to the email list, published on the RSS feed, and added to the list of stories.

This is all early. If you have suggestions for different questions, how this approach of project can be improved, or what not, please send a note.

Would you like an email when new stories are posted?