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.
Canonical template
Section titled “Canonical template”[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-fittingcloser: current project, where based, relevant personal note, or what comes next - optionaland venue-dependent].When to use
Section titled “When to use”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 not to use
Section titled “When not to use”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.
Pairs well with
Section titled “Pairs well with”direct-communicator, storyteller, confident, warm, narrative-case-study
Often confused with
Section titled “Often confused with”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
Anti-patterns
Section titled “Anti-patterns”- 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.
Failure modes
Section titled “Failure modes”- 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.
Instruction
Section titled “Instruction”Write as a bio. The output is a short third-person narrative that introduces a personprofessionally - their current role, notable work, relevant credentials, and the throughline oftheir career - shaped to fit the context in which it will appear. Write in third personthroughout: "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 thisreader; 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 wordcount allow. The goal is to give the reader enough to receive this person well - no more,no less.Template
Section titled “Template”See the Bio template.
Related
Section titled “Related”Pairs well with
Section titled “Pairs well with”Direct Communicator, Storyteller, Confident, Warm, Narrative Case Study
Avoid with
Section titled “Avoid with”Often confused with
Section titled “Often confused with”Examples
Section titled “Examples”- Whether the team should move to async-first standups
- Designing a sustainable morning routine
- Choosing Postgres vs DynamoDB for a new service
- Telling stakeholders a committed feature is being cut this quarter
- Getting a new engineer productive in their first two weeks
- Writing to thank a mentor who shaped your career
- Reflecting on keeping a discipline of rest
- Marking a long-serving colleague's departure
- Marking the team shipping a hard, long project
- Arguing a public position on return-to-office
- Announcing a new product to an outside audience
- A personal year-end reckoning with a difficult year
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.
Jordan Voss is a Program Manager at Aldergate Health Network. They coordinate delivery across concurrent care-access initiatives there, and introduced the decision-record template the team now uses to keep scope changes from being re-litigated after the fact. In May 2026, they pointed that same instinct at their own mornings: a written decision record laid out a four-module protocol - water, light, movement, paper planning - before the trial’s first day, and a version-controlled repository logged wake time, completion, and mood every day for thirty days. The result was 23 of 30 mornings completed in full and phone use deferred until the planning step on 28 of 30 days, tracked in public and written up as weekly retrospectives rather than kept as a private resolution.
Jordan is based in Denver and is currently running Month Two of the protocol, with a travel variant in testing and a controlled one-week removal of the light step scoped to find out which parts of the routine are actually load-bearing.
Team Profile - Lattice Notify Engineering Wiki
Section titled “Team Profile - Lattice Notify Engineering Wiki”wiki.latticenotify.com/team/ana-rivera
Ana Rivera is the tech lead for Lattice Notify’s notification service, and one of eight engineers on the company’s backend team. She has spent three years operating Lattice Notify’s primary Postgres cluster in production, the experience behind most of the runbooks the 4-person on-call rotation still reaches for today. Most recently, she led the team through the decision to build the new real-time notification service on Postgres rather than DynamoDB, a call written up in ADR-0023 that traded a better-fitting access pattern for the operational familiarity an 8-person team could actually carry. The decision came with a documented threshold, 5 million events a day, for revisiting the call once the team has real growth data instead of a guess. Ana writes occasionally for the Lattice Notify engineering blog about calls like this one, where the boring choice turns out to be the correct one.
Maya Chen
Section titled “Maya Chen”Meridian > About > Leadership
Maya Chen is Product Lead at Meridian, where she owns product strategy and stakeholder communication for the platform’s usage-analytics surface. When a mandatory billing-system migration collided with the Q3 commitment for the Insights dashboard, Maya chose to defer the feature rather than ship it without the saved-view and scheduled-report capabilities the committed customers had specifically asked for, and had a CSV export of the same underlying data live for those customers within two weeks. She briefed sales and customer success ahead of the written deferral notice, secured leadership sign-off on the revised target before it reached a single account, and locked the full dashboard scope for next quarter with engineering. The instinct behind that call is not new: at Northlake Software, Maya introduced a quarterly capacity-review checkpoint between engineering and sales leadership to catch exactly this kind of conflict before it reaches a customer, and she has run some version of that check at every team she has led since. She is based in Austin and is now scoping the full Q1 release of Insights with engineering.
Priya Rao
Section titled “Priya Rao”Team directory profile - Backend Services, Northlane Systems
Priya Rao is a Software Engineer on the Backend Services team at Northlane Systems, joining in June 2026 after nearly four years at Larkspur Systems. At Larkspur, she owned the backend systems behind billing and invoicing, redesigning alert routing across two monitoring tools to cut duplicate pages and migrating a legacy nightly batch job to an event-driven pipeline that now runs in minutes instead of hours. She also mentored two newly hired engineers through their first on-call rotations, pairing on incident response until each could run primary solo.
At Northlane, she has moved quickly: she traced her first production request end to end within her opening week and shipped her first change to the service before the end of her second. Priya holds a B.S. in Computer Science from Ridgeline State University and works remotely from the US.
Dana Forsythe is Senior Director of Data Platforms, leading the group that grew out of a migration she sponsored a decade ago. In March 2016, with senior stakeholders watching and a safer option available, she put an unproven analyst forward to lead the Alderton platform migration rather than naming an established mid-level manager to the role. She stayed close for the length of the project, answering the same questions more than once, and did not take the work back the one time it was offered to her in a moment of panic.
That was not a one-time bet. Over the ten years since, Forsythe has kept to the same three moves for developing the people who report to her: nominate before they feel ready, stay visibly available, and let them make the call themselves. Sable Marchetti, the analyst from Alderton, has since carried the pattern to her own team. Earlier this year she nominated a colleague, Priya Osei, to lead the Cassava data-pipeline rebuild, then gave Osei the same room Forsythe had once given Marchetti.
Forsythe is this year’s nominee for the company’s internal mentorship award, put forward by Marchetti. Asked why, Marchetti said she only recognized her own pattern with Osei because she had watched Forsythe run it first, on a project nobody expected her to lead.
Renata Cole
Section titled “Renata Cole”Contributor bio - Ashgrove Partners internal blog, “The Weekly Stop” series
Renata Cole is a director of client services at Ashgrove Partners, where the working assumption for years was continuous availability: a productive week was one in which nothing sat unanswered. She has since committed to a different rule, one full day of rest for every seven, during which she does not produce work, complete tasks, or check messages or notifications. As she wrote in this week’s installment, the day is not a lighter version of a workday; it is a structurally different kind of day.
The rule did not hold the first time. An earlier version of the practice ran six weeks before a deadline pulled it under, and Renata did not return to it for eleven months. The current run has now held for fourteen weeks, including the week she moved her phone into a drawer for a full ten hours, up from four the week before. She is now extending the boundary earlier, from Saturday evening to Friday sundown, and working to name, before July 5, the one channel she is most likely to rationalize checking. Renata is based in Minneapolis.
Howard Thayer
Section titled “Howard Thayer”Retirement spotlight - Crestfield Group Operations
Howard Thayer spent twenty-six years as the Operations Coordinator at Crestfield Group, joining in June 2000 and holding the role, unchanged in title, through his last day on June 27, 2026. In his final months, he worked with Dana Reyes and Marcus Okonkwo across two sessions to write down what had never been written down: the vendor escalation paths, the four utility contacts that existed only in his personal contact list, and the sequence the team should follow when the automated alerts do not tell the full story. The result is the runbook the operations team now uses in his place.
Howard is remembered less for what he managed than for what he prevented. Priya Sandhu, Ben Holter, and four other colleagues he mentored over the years contributed to an internal archive of his method: how he framed a problem for someone who was panicking, how he absorbed a situation before he spoke. None of them describe being supervised by him. They describe him being there.
At the all-hands send-off on June 25, Howard spoke for four minutes. He said he was proud of the team and that he did not want to be the reason anyone felt stuck. It was, colleagues said afterward, exactly the kind of thing he would say.
Priya Vasquez is a Program Lead on the checkout engineering team. She spent the past fourteen months running Project Halyard, the ground-up rebuild of the company’s checkout pipeline, and closed it out herself with the final status report to the wider organization.
The rebuild ran two live checkout systems side by side for the full fourteen months, migrating traffic cohort by cohort from a one percent canary up to a full cutover, while the legacy flow kept processing real orders the entire time. No customer ever saw a degraded checkout during the changeover. Two near-misses surfaced during the parallel run, both caught and resolved before a customer encountered them, and both times the team chose to slip the launch date rather than ship around an unresolved risk - a discipline Priya protected by keeping schedule pressure off the engineers who had to make that call.
The project closed in June 2026: the rebuilt checkout held through its first peak-traffic weekend without a rollback, and the legacy system moved into a scheduled decommission. Priya is now documenting the dual-track migration approach the team used, so the next hard rebuild does not have to start from zero.
About the Author
Section titled “About the Author”Priya Ahluwalia is the Policy Working Group Lead at Brackenridge Group, where she turned an undefined “flexible” work-location policy into a ratified position with a name and a shape: two mandatory anchor days, Tuesday and Thursday, for shared collaboration, and three fully flexible days for everything else. Reaching that position meant chartering a working group across HR, Facilities, Engineering, and Legal, then putting formal answers in writing to the two objections that mattered most: the office-first case for daily proximity, and the remote-only case for talent access and accommodations.
She has since published the reasoning behind that decision as hybrid-anchor, an open framework other companies can adopt directly instead of re-litigating the same office-or-remote binary from scratch. The same instinct ran through her earlier HR roles at Denholm Industries and Ashworth & Vale, where she built the manager-training and accommodation processes that hybrid teams still depend on: a contested policy question gets resolved by writing the position down, not by leaving it ambiguous. Priya is based in Columbus, Ohio, and continues to write and speak about workplace policy design for teams working through the same return-to-office argument Brackenridge already had.
Marisol Veen is Head of Product at Tidemark, where she has led the product from private beta through its June 30 public launch. Before Tidemark, she was a senior product manager at Bramwell Analytics, where she once consolidated four separate feedback channels into a single monthly prioritization review by hand - the same problem Tidemark now solves for other teams.
At Tidemark, Marisol set the launch to lead with that problem, scattered feedback with no shared ranked view, rather than a product-category label. She ran the twenty-two team early-access cohort through the full feedback-to-roadmap workflow ahead of general availability - every team completed it without filing a support ticket - and defined the three-tier pricing model that dropped the sales-call requirement from the free plan.
Marisol holds a B.S. in Business Administration from Brightwater College and is based in Portland, Oregon. She is available for press inquiries at marisol.veen@tidemark.io.
Marcus Delgado
Section titled “Marcus Delgado”marcusdelgado.com - About
Marcus Delgado is an independent consultant based in Columbus, Ohio, advising public-sector and nonprofit clients on operations, program delivery, and technology adoption. He has run his own practice since 2019, following six years as a program manager at Aldergate Infrastructure Partners, where he coordinated regional infrastructure planning across engineering, policy, and community-relations teams. He holds a B.A. in Public Policy from Ashgrove State University.
From September 2023 to March 2025, Marcus led the Meridian Community Broadband Initiative as a volunteer, directing an eleven-person coalition through an eighteen-month effort to plan and propose community broadband infrastructure. The coalition produced a technically sound proposal and held funder confidence for the full engagement; the initiative closed in March 2025 when its primary funder withdrew, before the work reached deployment. Marcus is currently writing a full account of that closure for the coalition members who built the proposal with him, and is not taking on new large initiatives until it is delivered.