Mission and Vision

FAQs

Table of Contents:
1. Why contribute to EMHub
2. How much time (articles)?
3. How much time (podcasts)?
4. Choosing a topic
5. Publication date

1. Why contribute to EMHub?

We're all here because we believe that engineering management matters. Great managers lead great teams, ship great code, and empower great engineers.

Most engineering leaders we talk to love mentoring others—especially new and aspiring leaders. Our mission at EMHub is simple: to help curate these key learnings for the benefit of the broader engineering community. We can't wait for you to join us in this journey!

There are a few more perks of contributing to EMHub:

• Build your personal brand – The floor is truly yours to discuss any engineering leadership topic that inspires you!
• Promote your company – most EMs we talk to are actively hiring; you are always encouraged to share your team's work and culture.
• Access a global dev community – EMHub is powered by Educative, a rapidly growing learning platform founded by developers and engineering leaders. Educative hosts over 350+ interactive courses with a user base of 1M devs and engineering teams. 
• Help us shape EMHub – join us on the ground floor and help EMHub become the best resource it can possibly be.

Note that EMHub will always be 100% free and accessible to anyone who hopes to become a better leader. We look forward to partnering with you!

2. What is the time commitment to write an article?

We know how much work goes into being an EM. We know you're extremely busy. That's why our experienced ghostwriters and editors make contributing to EMHub as fast and easy as possible.

Depending on your desired level of involvement, you can expect the entire process to take 15-45 minutes

1. 10 -15 minute intro call to select a topic OR asynchronously submit a topic and brief outline
2. 30 minute informal interview with a ghostwriter
3. Asynchronous final review with our editorial team

3. What is the time commitment to participate on a podcast?

This takes even less time than writing an article — in total, about 40 - 60 minutes

1. Submit a topic
2. Receive questions
3. 40-minute formal podcast interview

4. What topics would I write or talk about?

The short answer: Whatever inspires you most about software engineering leadership!

The slightly less short answer:

• Tell your engineering management story
• Share your favorite tools, tips, and best practices related to successful engineering leadership
• Promote your company or team's achievements
• If the content might be useful to an EM (or aspiring EM) then it has a home on EMHub!

The longer answer:

• Discuss initiatives you tackled and challenges you faced—what worked and what didn’t (sometimes those moments of unsuccessful engineering leadership can be even more illuminating than the successes!) 
• Offer battle-tested advice on hiring, upskilling, and mentoring developers and scaling dev teams
• Comment on topics in technology, leadership, or organizational development that are relevant to engineering managers
• Share the most impactful leadership lessons you have received
• Promote your favorite leadership resources (books, podcasts, blogs, workshops, etc. — there's a big world of learning out there beyond EMHub!)
• Anything else that a current or aspiring engineering manager would benefit from learning

5. How long does it take for my article to be published?

Speak with our lead editor to get an accurate time estimate.