Staff Product Architect

Summary

You design and own the reusable component layer that powers Cadre AI’s AI systems, turning bespoke client builds into configurable modules to maximize reuse and margin.

About Cadre AI

Cadre AI is an AI strategy and integration firm that builds production AI systems for B2B companies in private equity, wholesale lending, real estate, and SaaS. We do not build decks about what AI could do. We ship systems that move revenue, compress costs, and automate the work that used to take entire teams.

The Role

Cadre sells solutions as blocks: productized engagements that clients buy from a library spanning things like document analysis, data and pipeline solutions, scoring engines, and conversational systems. You will own the technical layer beneath that library. Every block decomposes into components, and you decide how to ensure that those components get built once, configurably, and reused across every client who buys them.

Day to day, you will be in the repos and in the pricing sheets. You will decompose blocks into named components, track how often each one attaches to a sold engagement, and prioritize what gets productized next based on what that reuse is actually worth. When a client asks for something new, you hold the final call on whether it is an existing block, an assembly of existing components, or genuinely net-new engineering. That call sets the hours, and the hours set the margin.

You will start as an individual contributor inside Product and Research, then work directly with the head of product engineering and the engineering team directly to build out these reusable components. This role suits someone with strong opinions about abstraction boundaries who is equally comfortable defending an estimate to a sales team and a client in the same conversation.

What You'll Do

Component Taxonomy and Module Architecture

Decompose every block in Cadre's library into named technical components + product requirements, each with a defined configuration surface, an owner, and a maturity rating.
Define the classification framework that determines what qualifies as a reusable module versus a client-specific build.
Establish naming, versioning, and documentation standards so any engineer can find, make updates to, or deploy an existing component without asking anyone.
Maintain the component catalog as the single source of truth for what Cadre can assemble versus what it must build from scratch.

Reuse Economics and Prioritization

Track attachment rate for every component: how many sold engagements include it, and what that reuse is worth in engineering hours.
Prioritize which components get built configurably next, weighing attachment rate, build cost, and margin impact.
Report net-new engineering hours as a percentage of total quoted hours, by block and by quarter, as the primary measure of portfolio leverage.
Identify blocks that are configuration variants of one another and consolidate them into a single parameterized component.

Pre-Sale Solution Assessment

Hold final sign-off on how every new client request is scoped: an existing block, an assembly of existing components, or net-new engineering.
Act as the ultimate responsible party for guiding the Solution Architecture and engineering teams on when a new technical component should be built, and work closely with Engineering to architect specifically how to build those components.
Partner with Strategy and Sales during client deep dives to translate requirements into component-level scope before pricing is set, attending client meetings as needed for direct feedback.
Approve engineering hours on pricing sheets so Cadre never quotes a build for infrastructure that already exists in the catalog.
Push back when a request is being scoped as bespoke work that existing components already cover.

Configurable Build Standards

Define what parameterized means at Cadre: the bar a component must clear before it counts as reusable rather than forked.
Drive high-attachment components from bespoke implementations to productized, configurable modules alongside the engineering organization.
Identify which existing builds are strong candidates to be turned into components, but also map new builds against the catalog to identify opportunities for reuse at the outset of building.
Own the process for versioning and updating components as client deployments surface new configuration requirements.
Recommend upgrades to existing deployments when components are enhanced; partner with Service Expansion team to do so.

Establishing the Product Architecture Flow

Operate hands-on, reading code and performing the decomposition work directly.
Partner tightly with the engineering team to rapidly assess the current state of configurability and establish a clear future state vision.
Raise the reuse instinct across Cadre's engineering organization so solutions are built from component configurability.
Over time, work with a small team of engineers to build out the highest-leverage components, setting technical direction and reviewing standards as needed.

What You Need to Succeed

10+ years building production software, including at least 3 in a role where you owned architecture decisions across multiple products or client engagements rather than a single codebase.
Proven experience turning bespoke, one-off builds into reusable configurable components, plus the judgment to know which ones were worth productizing and which were not.
Deep fluency with modern AI application patterns including LLM orchestration, retrieval, document processing pipelines, voice agents, and agentic workflows, with production systems you can point to.
Comfort working directly in the codebase. You will read repos, evaluate abstraction boundaries, and make calls that engineers live with, so technical credibility is non-negotiable.
Strong command of the stack Cadre builds on, including TypeScript and Node, Python, Next.js, Postgres or Supabase, and cloud deployment across Vercel, Render, or AWS.
Ability to translate technical architecture into commercial terms (hours, cost, scope, and margin) and defend an estimate to a sales team and a client in the same conversation.
A track record of establishing standards that people actually follow, rather than documentation that gets written once and ignored.
Willingness to hold the line. This role carries final sign-off on scoping, which means telling experienced colleagues that the bespoke build they want is not necessary.
Comfort making prioritization calls with incomplete information. Cadre's library grows every week and you will not have every data point before you decide.
Appetite to grow into a leadership role. You will start hands-on and build a team as the catalog matures, so both modes need to appeal to you.
Excellent written communication. Your taxonomy, standards, and decisions live as documentation that the entire company depends on.

Why Cadre AI

Real ownership. You own the component layer end to end: the framework, the catalog, the standards, and the sign-off. Nobody else is making these calls.
Compounding leverage. Every component you productize pays off across every client engagement Cadre sells from that point forward.
AI-native culture. We do not just build AI for clients. We use it to run our own operations. You will work with people who are as obsessed with the tools as you are.
Access to the frontier. Through partnerships with Anthropic and OpenAI, you will be among the first to experiment with new models and capabilities.
Upside. We are bootstrapped, profitable, and growing fast. Growth means new teams and new initiatives, and room to move into them.
No bureaucracy. Small, scrappy team. Clear accountability. The best idea wins, regardless of who says it.

If you have spent your career watching the same system get rebuilt under a different name for the fifth time, and you want the authority to stop it, we should talk.

Show