Director of Engineering, Backend and Product Engineering

About the Job:

We're hiring a Director of Engineering to own the backend and internal platform layer between Redesign’s infrastructure and its applied AI products. This is the technology that makes our data, tools, and development patterns usable by engineers, agents, and the domain experts building software across the firm.

At Redesign, everyone builds. Experienced engineers ship more complexity than ever before, domain experts turn judgment into working systems, and agents participate in the path from idea to production. That changes what backend engineering means. The backend is the shared layer of data, access, tools, and conventions that lets many kinds of builders create safely. This role owns that layer between infrastructure and applied AI.

• Build the backend platform behind Redesign’s operating system. You will own the APIs, databases, services, resource models, migrations, and access patterns that back our core AI operating system. Your job is to make the primitives behind Redesign’s work easy to discover, safe to extend, and hard to misuse, so applications, agents, and builders can consume trusted data without bespoke plumbing.

• Define the paradigm for AI-native development. You will own the systems and conventions that let agents drive software engineering: agentic coding patterns, harness design, memory management, verification loops, and self-learning multi-agent code review. Done well, this unlocks a trusted path from intent to production: if generated code is safe, standards-compliant, and proven to do what it was meant to do, it can become part of the system without turning human review into a bottleneck.

• Build for a workforce where everyone creates software. You will own the developer experience for a builder population that brings together infrastructure engineers, applied AI engineers, and domain experts without formal software backgrounds. You will deeply understand how Redesign functions and build powerful primitives that cut across teams, decisions, and geographies. That means thoughtfully designed tools and interfaces that capture the most important work and workflows, and let the whole firm turn judgment into technology at the speed of thought.

We value and actively seek exceptional talent from all backgrounds and experiences, recognizing that excellence takes many forms. The strongest candidates have been selected into high-talent environments, distinguished themselves within them, earned unusually broad scope or trusted ownership, progressed rapidly, or done work that changed the trajectory of a team, product, company, or field. While every path is different, we believe the most successful candidates for this role will share the following characteristics:

• 10-12+ years of engineering experience, with meaningful time at staff, principal, or equivalent level at a serious software company. You have anchored the technical work of a small, fast team before, and you have owned backend, data, developer-platform, or internal-platform systems that other people built on every day.

• You have shipped production backend systems in Python and/or Type Script, with ownership of database schemas, migrations, API contracts, authentication, and permissions. You have worked deeply with Postgres or a similar relational database; built authorization or identity layers with scoped access for users, services, and agents; and shipped APIs and data services that multiple teams depended on.

• You have built or operated agent-facing infrastructure that teams used every day: MCP servers and tools, Claude Code or Cursor conventions, skills or plugin systems, sandboxed execution, code-review automation, evals, usage and cost controls, and safe defaults. You understand that agents are now first-class consumers of backend systems.

• You have range across product craft and developer experience. You have built tools, applications, or internal platforms for experienced engineers and for builders without traditional software backgrounds, and you understand that this work is as much about shaping how people encounter the system as it is about creating a technical surface. You have…