Senior Technical Writer

The Senior Technical Writer is the documentation architect for a product's external docs - the senior individual contributor who sets the information model, the docs-as-code toolchain, and the editorial governance the whole writing function builds to, and who personally leads the hardest documentation. Core ownership is the doc set's architecture and standard: the content model and taxonomy that decide how every topic is typed, structured, and found; the docs-as-code pipeline and automation the writers author in; the style, terminology, and quality bar that make many hands read as one; and the strategy and metrics that define what "good docs" means for the org. This is a senior individual-contributor seat reporting to a docs / content manager or an engineering leader, with architecture-decision ownership of how the doc set is built, deep partnership with engineering and product leadership, and a mentoring relationship to the writers. It is not the base Technical Writer (../../024_Technical_Writer/), who writes and maintains excellent docs to the information model, tooling, and style standard and owns the docs for their features - this seat sets that architecture and governance across the set and leads the doc no one else can. It is not a Content Designer / Senior Content Designer (../../012_Content_Designer/), who owns the in-product text - labels, empty states, error messages, onboarding microcopy - and the interface's information architecture that shapes the interaction itself; this seat architects the external documentation the reader steps away to consult, a different surface and craft. It is not a Developer Advocate / DevRel, who owns community, advocacy, and evangelism (this seat owns the reference and how-to of record the community is pointed to). And it is not a Docs / Content Manager: this seat sets the technical and editorial direction and mentors, but owns no people, no headcount, and no budget - it recommends and escalates those. Performance is visible in the coherence and scale of the doc set the architecture produces, the success of the hardest doc sets led, and the level the writers mentored operate at. What separates great from average at this altitude is setting an architecture and a standard that multiply across every writer and every product, rather than writing one more excellent guide: a content model and taxonomy that hold as the product grows tenfold, a docs-as-code toolchain that is the easy path so writers actually work in it, a style and terminology standard enforced in the pipeline so the whole set reads as one voice, a new-product or major-API doc set led so it lands complete and correct on day one, and writers who leave a mentoring relationship structuring and reasoning at a higher bar. A mediocre senior hoards the hard doc sets and becomes the writing snowflake-of-one; a great one turns the hardest documentation problem into a model and a paved road the whole team can run.