As a Knowledge Engineer, your role is to help transform a complex and evolving technical ecosystem into something engineers can successfully navigate, understand, and build on top of.

You will be a founding member of the Builder Enablement team at the intersection of architecture, engineering, and enablement - partnering with architects and builders to capture not just what systems exist, but how they fit together, why they work the way they do, and how other teams can effectively use them.  

This is not a traditional documentation role, although you will be responsible for Technical Writing. You won’t simply document decisions after they’re made - you’ll help shape how technical knowledge is structured, communicated, and consumed across the organization. That means asking the right questions, identifying missing context, and turning fragmented information into clear, actionable understanding.  

Your output may take many forms: architecture narratives, onboarding guides, technical playbooks, diagrams, knowledge maps, or AI-friendly documentation structures. The goal is always the same: reduce ambiguity, improve discoverability, and help engineers move effectively through complex systems.  

As AI becomes an increasingly important interface for engineering work, you’ll also help ensure our technical knowledge is organized and expressed in ways that are consumable not just by humans, but by intelligent tooling and agent-based workflows as well.  

Part technical writer, part information architect, part systems translator: you’ll help create the connective tissue that turns architecture into shared understanding.  

Responsibilities

• Partner with architects, engineers, and platform teams to capture and communicate:

  • System architectures and interactions   

  • Engineering patterns and implementation approaches   

  • Platform capabilities and constraints  

  • The reasoning and tradeoffs behind technical decisions   

• Create and maintain clear, consumable technical artifacts such as:   

  • Architecture overviews   

  • Technical narratives and roadmaps   

  • Reference documentation   

  • Knowledge maps and information hierarchies   

  • Engineering onboarding and enablement materials   

• Conduct interviews, workshops, and collaborative discovery sessions with engineering teams to extract institutional knowledge and translate it into reusable understanding   

• Help structure technical information in ways that are:   

  • Easy for engineers to navigate and apply   

  • Consistent across related systems and domains   

  • Increasingly consumable by AI-assisted tooling and agent-based workflows   

• Work with Builder Enablement architects and engineers to transform evolving architectural concepts into practical, actionable guidance for development teams   

• Identify ambiguity, gaps, or fragmentation in technical knowledge and proactively improve clarity, discoverability, and consistency across engineering artifacts   

• Create lightweight diagrams, workflows, and visual representations that improve comprehension and system understanding, prioritizing clarity and usability over presentation polish   

• Help ensure that architectural guidance, standards, and paved paths are clearly articulated, internally consistent, and practically adoptable   

• Leverage modern AI tools and workflows to accelerate knowledge synthesis, organization, and maintenance   

• Act as a steward of engineering knowledge and information hierarchy, helping ensure that teams can effectively discover, understand, and apply shared architectural guidance over time