How some good corporate engineering blogs are written
My company [1] writes technical blog posts as a service [2]. We mostly work with Bay Area startups. Some key observations and learnings:<p>- Many companies have tried to create engineering blogs, but you&#x27;d never know because the first post was so unpleasant to create that the whole effort got called off.<p>- If a company does manage to publish a first post, the experience is often so personally traumatic to the engineer that they never try again and&#x2F;or tell their team members to avoid the process. This is especially true when PR&#x2F;Comms insists on reviewing posts. (Legal review typically goes more smoothly.)<p>- Coming up with ideas for posts is WAY easier said than done. Nobody, engineers included, likes staring at a blank page. A significant part of our work is refining ideas and creating outlines.<p>- Lest you thought otherwise, company engineering blogs are almost always justified as candidate lead gen. Posts are frequently used by recruiters in outreach emails. When a post and email are well written, response rates can easily double—effectively doubling the candidate pool for a growing team. (This assumes that engineers aren&#x27;t applying to jobs unprompted, which is true for about 80% of startups in the Bay Area.)<p>- In our research with job seekers, we found that when senior engineers research a company, they seek the company&#x27;s engineering blog before they seek the careers page, let alone a job description. This is probably obvious to folks here, but in the recruiting world this blows everyone&#x27;s mind.<p>- Technical blog posts are expensive whether you DIY or work with someone like us. A detailed post, let&#x27;s say 1500 words, can easily consume 25 hours of time from everyone involved. 50 hours isn&#x27;t rare. And this is when the process works well. (Our value prop: we shift time from engineers to our writers.) Here&#x27;s the process we&#x27;ve found works best. Everything here happens in Google Docs.<p>1. One of our writers, all former journalists, sits down with an engineer who has an idea for a post. In a 1 hour conversation, they work together to refine the idea and create a bare-bones outline. Assuming you&#x27;re doing this yourself, my point is that pairing is helpful. This conversation gets recorded and transcribed by a transcription service. (4 hours total time)<p>2. The writer reviews the transcript and fleshes out an outline. They note locations for graphics and code snippets. The engineer then reviews the outline and leaves comments. (4–6 hours total time)<p>3. The writer creates a complete first draft, with assistance from 1–2 editors on our team. They leave space for graphics&#x2F;code for the engineer to add on their own. (8–10 hours)<p>4. The engineer brings in 1–3 other engineers to review the post. The team adds illustrations and&#x2F;or code. More comments&#x2F;feedback. (6+ hours)<p>5. Our writer incorporates feedback. An editor on our team proofreads the post for clarity, grammar, etc. (2–4 hours)<p>6. Legal and&#x2F;or team leaders review the post. (2+ hours)<p>7. Whomever runs the blog puts everything in the CMS and hits publish. (1 hour)<p>End of the day, we&#x27;ve ideally consumed fewer than 10 engineer hours. The rest is on us—anywhere from 15–30 hours.<p>Feel free to email me directly about any of this :) jackson@jobportraits.com<p>[1] <a href="https:&#x2F;&#x2F;www.jobportraits.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.jobportraits.com&#x2F;</a>, 
[2] <a href="https:&#x2F;&#x2F;www.jobportraits.com&#x2F;services&#x2F;tech-blog-post-subscription" rel="nofollow">https:&#x2F;&#x2F;www.jobportraits.com&#x2F;services&#x2F;tech-blog-post-subscri...</a>