The majority of experienced developers who responded to this thread applied for a job or joined a company after learning more about it at a corporate engineering blog. u/improbablywronghere wrote, “Finding a blog post from a company is like you an interviewer at some company finding a public GitHub repo from a candidate.” Writing a blog is Hard Work, Plus, and Do Things, Tell People, at scale. If you face challenges with recruiting, your team needs more people to know about the work they’re doing.
Every team needs a blog. If your team hasn’t started a blog, and isn’t sure what kind of ideas to move forward with, this post contains 6 types of posts as a starter pack. It’ll mostly cover engineering blogs (as the title suggests!), though the structures can be applied to all sorts of industry blogs written by teams. Consider these types as starting points, not ending points.
These writing structures can also be useful for teams who have recently started or rebooted their engineering blog and are stuck on what to write about next:
1. What the interview and hiring process looks like
Naturally, passive or active job candidates you reach out to will wonder “What does the interview process look like?” You can anticipate this and write a blog post about what they can expect, and how they can succeed. How many rounds will there be? What kinds of questions will the interviewer ask?
- Shopify’s Technical Interview Process: What to Expect and How to Prepare
- How we improved our interview process at Flipp
- How to prepare for your Discord interview
- What it’s like to interview at GitLab: A peek inside the recruitment process
- 5 ways recruiters and job seekers can have a better hiring experience
Fly.io also puts this in their documentation.
This post could also include information on how the team thinks about a specific position and the ideal candidate in this role.
You could also write about your team’s opinions on interviewing and hiring in general; for example, Honeycomb has an interesting piece here.
2. How we built ___
These posts show what engineering culture and process looks like. The idea is to build in public: to share the process of a feature recently shipped. Choose something your team is excited about, and write about it while the memory is fresh! Even just a few weeks will be too late; people’s contexts will have shifted and memory will be fuzzy. Anyone reading this will learn more about the details—e.g., how you deploy front end web apps, who makes decisions, how many teams were involved, etc.
- How We Built Fly Postgres
- How We Built Hydrogen: A React Framework for Building Custom Storefronts
- How We Build Code at Netflix
- How We Built Virtual Accounts
- Creating the Notion API
Also, explaining why your team built something can show a similar thought process, which is what job candidates will want to learn more about:
- Why We Built Ledgers
- Why we built our core engineering team outside of Silicon Valley
- Why We Built Cloudflare Workers
3. Share your technology stack
Show readers what kind of technology stack you’re working with.
- Rebuilding our tech stack for the new Facebook.com
- The Trello Tech Stack 2016
- The Uber Engineering Tech Stack, Part I: The Foundation
4. Why your team made a technical decision
Share your opinions and decision-making process on specific technology. More often than not, you’ve actually already written the words in memos or Slack or Threads, you just need to compile it together and put it into a blog post.
- Why we chose Kafka for the Trello socket architecture
- Why we’re leaving the cloud
- React Native is the Future of Mobile at Shopify
- Carcinisation of mirrord (or: why we use Rust)
- We Fast-Tracked Our App Development With Kotlin Multiplatform Mobile
- Why Discord is switching from Go to Rust
5. Culture and lifestyle
Show what a day in the life of working at the company is like, and what the responsibilities and scope of a specific role is.
- A Day in the Life of 3 Postlight Engineers
- Day in the life: Data Analyst at incident.io
- A Day in the Life of a Content Analytics Engineer
Alternatively, also highlight a team member who works at the company (interview or first-person); great engineers want to work with other great engineers.
- Data Engineers of Netflix — Interview with Kevin Wylie
- Ben Fathi: Why I Joined CloudFlare
- My Name Is John Bohn — This Is Why I Joined Aha!
Share your industry advice and perspectives, and showcase the best practices you’ve developed.
- The startup guide to sensible incident management
- The Serverless Server
- Guardians of the Wealthsimple Galaxy
- 8 website monitoring best practices to keep your site running smoothly
- How Data Science Informs Strategy & Innovation at Discord
- Best practices while developing a React Native App
You could even write a whole book on this topic! See Postman’s recent work with The API-First Transformation, authored by evangelist Kin Lane. (The team also wrote a “How we built ___” on the writing process!)
- How experienced developers use corporate engineering blogs
- So, you want to start an engineering blog?
- “We should really write a blog post about that”
- Why you should turn your conference talk into a blog post
- Your future, one post at a time
- Contentions: “People don’t actually know that…”
- Treat promoting your work as its own craft
- Time to ship
- How to Write Faster
- Writing culture
- Contentions: Culture turned outwards is brand, turned inwards is product