Technical Coordinator

About the Role
The Technical Coordinator keeps projects aligned and moving. You work across product, design, and engineering, catching gaps early, writing the documentation that prevents repeated questions, managing the boards that keep work visible, and building the automations that eliminate busywork. All written output is published from the CTO's Office, so clarity and accuracy are non-negotiable.

Key Responsibilities
- Review PRDs before they reach design and flag ambiguities, edge cases, and undefined behavior

- Cross-reference Figma designs against requirements and implementations to surface gaps early

- Write and maintain technical documentation across all active projects: READMEs, PRDs, API guides, SOPs, and runbooks

- Own project boards in Linear or Jira milestones, owners, due dates, blockers, and weekly status summaries

- Draft, test, version, and organize prompts for AI assistants, agents, and automation workflows

- Identify repetitive tasks and ship automations using n8n, Zapier, Make, or custom scripts

- Attend cross-functional syncs and document every decision, action item, owner, and deadline

- Support rapid prototyping sessions by scaffolding projects, capturing ideas, and turning rough direction into structured specs

Requirements
- Strong technical writing ability: you can produce a PRD, a README, and an SOP with equal confidence

- Fluency with project management tools, specifically Linear or Jira

- Working knowledge of Git and comfort operating in a developer environment

- Hands-on experience with prompt engineering and LLM-based workflows

- Ability to build and maintain automations without engineering support

- Detail-oriented enough to catch a missing screen in a Figma file or a scope mismatch in a ticket

- Async-first communicator who writes clearly and follows through without being chased

- Familiarity with Python, Bash, or JavaScript at a scripting level is a plus

What You'll Own
- A living alignment tracker per project mapping requirements to design to implementation

- All technical documentation across active repositories and projects

- A versioned, organized prompt library by project and use case

- Every active project board groomed, current, and fully accountable

- A central automation registry documenting every workflow the team runs on

- Weekly status summaries surfacing what shipped, what's blocked, and what needs a decision

- An idea backlog with enough context to resurrect any concept weeks after it was first raised

Work Location: In person