liveBook · Manning

Speaker bio

As explained in Writing for Developers: Blogs that get read

A short biographical description of a proposed conference speaker's background, experience, and interests.

A speaker bio helps conference organizers judge your experience, background, and interests. Replace a bare job title with specific evidence of what you have learned and built. section 16.3.2

Strengthen a bio by:

  • Connecting your background and interests to the proposed topic. section 16.3.2
  • Naming relevant experience rather than lazily repeating your job title. section 16.3.2
  • Linking to an up-to-date portfolio containing posts, talks, GitHub, social handles, and the bio itself. section 16.3.2

A stronger pattern

“I started learning Rust for fun in 2017. I’ve now worked full-time with Rust for five years at ACME A and ACME B, writing high-performance and high-availability API servers and internet proxies.” This combines motivation, duration, employers, technology, and concrete work. section 16.3.2

How Writing for Developers: Blogs that get read covers it

How deep it goes
Explains what to include, contrasts it with a bare job title, and supplies one concrete example.
Examples
Uses a Rust engineer’s experience and a portfolio containing posts, talks, GitHub, and social handles.
What it assumes
Assumes a conference proposal context and teaches writers to turn experience and interests into specific evidence.
What you can do after
Build a concise, evidence-based bio and support it with an up-to-date portfolio link.
How it connects
Connects speaker bios with conference proposals, abstracts, portfolios, and blog posts.
Cover of Writing for Developers: Blogs that get read
liveBookmanning.com
Read Writing for Developers: Blogs that get read on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Writing for Developers: Blogs that get read. The section links point to the parts of the book it draws on.