Technical Architect

Job Description

About the Company

DevDocs hires developers to build documentation and docs tooling for clients like Qualcomm, American Express, and C3 AI.

We don't hire writers, and we don't just crank out docs: our close-knit team is full of technical experts who can deeply understand a client's products, consult on their problems, then design tools and systems to automate their docs processes (and write the most important docs).

Position Overview

We are looking for a hands-on Technical Architect, someone who sits at the intersection of engineering, product thinking, and business direction. This is a deeply collaborative role for someone who enjoys writing real code, shaping systems, and helping define where the company is going, not just how features get implemented.

This is not a title-driven role. It’s for someone who wants long-term ownership, meaningful influence, and the opportunity to help shape both the technology and the organization as it grows.

What You’ll Spend Your Time Doing

Rather than a fixed list of responsibilities, this role evolves with the company. In practice, that means:

• Working hands-on in the codebase, contributing directly to core systems
• Helping shape and evolve our technical architecture as products and ideas take form
• Partnering closely with leadership to translate business direction into technical decisions
• Exploring and reasoning through complex systems, even when documentation is incomplete
• Helping the team think clearly about tradeoffs, sequencing, and long-term implications
• Using modern tools (including AI) to explore ideas, accelerate understanding, and improve how we build

The Kind of Background That Fits Well

There is no single “right” resume. People who thrive here often have experience like:

• Building full-stack systems using tools such as Next.js, React, TypeScript, Python, Postgres, and graph-oriented data models
• Designing or evolving systems where requirements were unclear or changing
• Moving fluidly between code, architecture discussions, and business conversations
• Being the person others turn to when the system feels messy and needs clarity

·       Taking ownership because they care not because they were told to

What matters most is how you think, how you collaborate, and how you approach uncertainty.

Impact You’ll Have

• Help shape the technical foundation of the company
• Influence product and business direction through engineering insight
• Create systems that scale thoughtfully, not prematurely
• Raise the level of technical conversation across the team
• Build software that directly supports real people doing meaningful work

How We Work Together

• Fully remote, with intentional collaboration
• Sustainable pace no grind culture
• High trust, high ownership
• Space to learn, reflect, and grow alongside the company
• Roles evolve as people and ideas evolve