Skip to content

Bio

A short third-person summary introducing who a person is professionally, shaped to fit a context.

A bio is a short third-person summary of who a person is professionally - their role, notable work, credentials, and the throughline of their career - written to introduce them in a program, byline, panel, or about page. Unlike a list of credentials, a bio is narrative and curated: it selects the details that matter for this reader in this context and arranges them into a brief story that gives the audience what they need to receive the person well.

The bio’s defining move is selection. A professional accumulates far more roles, projects, and credentials than any bio can carry; the writer chooses the two or three that explain who this person is in the context at hand. A speaker bio for a technology conference foregrounds different work than a byline for a literary journal - same person, different selections, because the reader arriving at each venue needs different context. The format earns its place by doing this work that a list cannot: a list of all credentials leaves the reader to construct the throughline themselves; a bio hands them the throughline already drawn.

Third person is not convention for its own sake. It signals that someone else is vouching for this person, which is the social function a bio performs. A conference program bio reads as the organization introducing the speaker; a book jacket bio reads as the publisher presenting the author. First person would shift that register from curated introduction to personal statement, which changes how a reader weighs the claims.

[Full name] is [current role or title] at [organization or affiliation]. [He/She/They]
[notable work or defining achievement in one sentence]. [Second notable credential, project,
or career move that completes the throughline - optional for short bios]. [Context-fitting
closer: current project, where based, relevant personal note, or what comes next - optional
and venue-dependent].

Introducing a speaker, panelist, or guest host in a program, event guide, or on-screen lower-third; writing an author byline for an article, essay, or book jacket; creating an About page or professional profile on a personal site or platform; submitting a contributor profile or media kit one-sheet for a publication or event; providing background on a podcast guest, webinar presenter, or conference keynote.

When an evaluator needs a comprehensive, scannable credentials record to assess hiring fit - use a resume; when the reader must compare qualifications across multiple candidates simultaneously; when the format explicitly calls for structured sections, labeled headers, and parallel evidence.

direct-communicator, storyteller, confident, warm, narrative-case-study

resume: A resume is a structured, scannable record of a person’s professional experience, skills, and qualifications, organized for a recruiter to assess fit in seconds. It presents credentials through reverse-chronological roles, bulleted accomplishments, and labeled sections so a screener can locate signal without reading prose - its defining quality is factual density and compression, not narrative. A bio is a flowing paragraph that tells a brief story for a reader who needs context, selecting and framing a handful of details into a throughline rather than inventorying the full record.

  • Written entirely in third person - “She leads…” not “I lead…”
  • A flowing paragraph or short block of prose, not sections or bullets
  • Opens with the person’s name, current role, and primary affiliation
  • Selects two to four specific works, results, or achievements rather than listing everything
  • Uses connective prose to draw a throughline, not parallel structure to inventory credentials
  • Length and detail calibrated to the venue - shorter for bylines, fuller for speaker pages
  • May close with a brief personal or contextual note relevant to the reader’s setting
  • Listing every past role in reverse-chronological order instead of selecting a narrative throughline - This collapses the bio into a resume. A resume is a structured, scannable record of professional experience organized for a recruiter to assess fit - its value is factual density, parallel bullets, and labeled sections. A bio’s value is curation: it tells a brief story for a reader who needs context, not a full accounting. Giving the screener’s document to the audience member loses both formats.
  • Writing in first person throughout (“I built…” or “My practice focuses on…”) - A bio performs a social introduction - it signals that someone is vouching for this person. First person shifts that register to personal statement, which changes how readers weight the claims and removes the implicit endorsement the format carries.
  • Using the same fixed bio text unchanged across all venues - A bio is defined by context-fit: the same person needs a different selection of details for a technical conference, a literary journal, and a LinkedIn about section. A single fixed bio either says too much for short slots or too little for full speaker pages, and in either case fails the reader who needed context, not a standard block of copy.
  • Stacking credential abbreviations and title strings without any prose that connects them - A bio structured as a credential list has the shape of a bio but performs a different function. The value the format adds is the throughline - the brief connective narrative that tells a reader not just what someone has done but why it coheres. Without that connection, the bio is a resume excerpt without the resume’s scannability.
  • Over-curates until substance disappears - the bio becomes a sequence of polished, context-appropriate phrases that could describe anyone in the field and reveals nothing specific about this person’s actual work - Anchor the bio with at least one specific work, project, or result a reader could look up or follow. Curation should select the most relevant detail, not sand away all particular content.
  • Over-narrativizes into self-promotional rhetoric - the throughline becomes a personal brand arc (“driven by a passion for…”, “on a mission to…”) that replaces concrete work with story posture, making the bio indistinguishable from marketing copy - If removing the specific works and credentials still leaves a coherent-sounding narrative, the bio has crossed from curated introduction into brand rhetoric. Reground every narrative claim in a verifiable specific: a project name, a role, a publication, a result.
Write as a bio. The output is a short third-person narrative that introduces a person
professionally - their current role, notable work, relevant credentials, and the throughline of
their career - shaped to fit the context in which it will appear. Write in third person
throughout: "She leads..." not "I lead...". Open with the person's name, role, and affiliation.
Select two to three specific works or achievements that explain who this person is for this
reader; do not attempt a comprehensive accounting. Use connective prose to draw a throughline,
not bullets or labeled sections. Calibrate length to the venue: a byline may be 50 to 80 words;
a speaker page may reach 300 words. Close with a brief contextual note if the venue and word
count allow. The goal is to give the reader enough to receive this person well - no more,
no less.

See the Bio template.

Direct Communicator, Storyteller, Confident, Warm, Narrative Case Study

Skeptical, Urgent, Reverent

Resume

Jordan Ellis is an engineering manager at Fernbridge Software, where they lead an eleven-person engineering team spread across four time zones: US Pacific, US Eastern, the UK, and India. Over the past eighteen months, Jordan grew the team from six engineers to eleven and rebuilt how it communicates, replacing a daily synchronous standup at 9am Pacific (9:30pm IST) with an async, Slack-based update format and a single Thursday working session reserved for conversation that actually needs everyone live. The redesign is documented in the team’s ADR and process README, making the reasoning and the rollout discoverable to new hires joining the distributed team.

Before Fernbridge, Jordan spent nearly five years as a senior software engineer at Warrenton Analytics, where they led the migration of the company’s primary billing service off a monolithic deployment. Jordan writes and speaks occasionally about distributed team management and async-first process design, drawing on the standup redesign at Fernbridge and the results from its first 30-day trial. Jordan is based in Seattle.