Staff Forward Deployed AI Engineer | San Diego, CA
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map headings accordingly. We have sections: About Cadre AI (maybe "About the role"? Actually "About Cadre AI" is about company, not role. Could be "About the role"? But we have "The Role". Could use "About the role" heading for that. However we must only include sections when posting has real specific content. We have content for each.
We need to avoid repeating job title as heading. So no heading for "Staff Forward Deployed AI Engineer". Also no Job ID.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. There's no explicit application instructions.
We need to include sections only when posting has real specific content. So we will include sections: About the company? Could be "About Cadre AI". But the allowed headings list includes "About the role". Not "About the company". However we could still use "About Cadre AI" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Probably we should stick to those headings where appropriate. We have content that fits: "About Cadre AI" could be considered "About the role"? Not exactly. Maybe we treat it as "About the role" (the role description). But we also have "The Role" separate. Could combine? Better to follow examples: Use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content.
We have:
- About Cadre AI (company description) -> could be "About the role"? Not ideal but maybe we can use "About the role" to describe the role and company? However we also have "The Role" section describing role. Could treat "About Cadre AI" as part of "About the role". But we might also add a heading "About Cadre AI" even if not in list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Safer to use those examples.
Thus we need to map:
- About Cadre AI -> maybe "About the role" (though it's about company). Could also omit if not needed? But we need preserve all substantive info. Could include as a
under a heading like "About the role". We'll put heading
About the role
and then include paragraph about Cadre AI.
- The Role -> could be "Responsibilities"? Actually "The Role" describes role overview. Could be "About the role" again but we already used. Maybe we use "Responsibilities" for What You'll Do. And "Requirements" for What You Need to Succeed. "Qualifications" maybe similar. "Skills" maybe for technical skills. "Benefits" for Why Cadre AI? Actually Why Cadre AI is about company culture, could be "Benefits". Pay is compensation. Schedule maybe not present.
We need to avoid filler sections. We have no explicit schedule info, so omit Schedule.
We have compensation: base pay range $165k-$200k. So we need Pay section.
We have benefits? Not explicit benefits like health etc. Why Cadre AI includes culture, leadership, AI-native, access to frontier, upside, no bureaucracy. Those could be considered benefits. We'll put under Benefits.
We need to ensure we don't create sections with placeholder text.
Thus sections:
About the role
(contains About Cadre AI paragraph)
Responsibilities
(contains What You'll Do content)
Requirements
(contains What You Need to Succeed content)
Benefits
(contains Why Cadre AI content)
Pay
(contains Compensation)
We need to use - for any list of duties/requirements/benefits. So within Responsibilities, Requirements, Benefits we should convert bullet points to lists.
Let's extract content.
About Cadre AI paragraph:
"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."
We'll put that in
.
The Role paragraph maybe not needed as separate; but we already used About the role heading for company description. The Role paragraph: "As Staff AI Engineer, you are the technical leader and backbone of Cadre's San Diego engineering team. At this level, your job is no longer just what you build; it is making sure every engineer around you builds better. You mentor and manage engineers, set the standard for how the team designs, reviews, and ships AI systems, and own their growth as deliberately as you own your own code. You pair that leadership with serious technical depth. You stay hands-on with the hardest builds in our client portfolio: multi-step agent systems, complex document processing pipelines, and automations that touch core revenue operations. When a problem has ambiguous requirements or no obvious solution, the team looks to you, and clients measure the result in EBITDA impact, not demos. You report to the Head of Client Engineering, and you will occasionally join client calls to walk stakeholders through what we are building and why. You thrive here if leveling up the people around you energizes you as much as shipping the system yourself."
We could include this under About the role as well, or maybe under Responsibilities? But we already have Responsibilities for What You'll Do. The Role is more overview; we could merge with About the role. To avoid duplication, we can include both paragraphs under About the role.
Now What You'll Do content includes bullet points under headings: Team Leadership and Mentorship, Technical Direction, Build and Ship Production AI Systems, Client Collaboration. Each has sub-bullets.
We need to turn those into
- . We'll preserve each bullet as
- . For sub-bullets, we can nest
inside - or just keep as separate
- with dash? Probably better to nest.
We'll produce:
Responsibilities
- Team Leadership and Mentorship
- Manage and mentor two engineers on the San Diego team, owning their technical growth, code quality, and delivery.
- Set the engineering bar through rigorous code review, pairing, and reference implementations the rest of the team builds on.
- Serve as the first escalation point when engineers hit problems they cannot solve alone, teaching as you unblock.
- Build the habits, patterns, and practices that make every engineer on the team measurably better quarter over quarter.
- Technical Direction
- Drive architecture decisions across client builds: agentic workflows, RAG pipelines, document processing, and automation running in production.
- Evaluate new models, frameworks, and techniques as they emerge, and decide what enters Cadre's production toolkit.
- Turn hard-won lessons from client builds into reusable internal tooling, templates, and documentation that compound across engagements.
- Build and Ship Production AI Systems
- Stay hands-on with Cadre's most complex client systems, owning delivery end to end from LLM orchestration and evaluation to data pipelines, APIs, and cloud infrastructure.
- Make pragmatic build decisions under real constraints: client timelines, legacy systems, messy data, and measurable business outcomes on the line.
- Ship fast without sacrificing reliability; design systems that keep working long after the engagement ends.
- Client Collaboration
- Join client calls when the conversation needs technical depth, walking stakeholders through system designs, trade-offs, and progress.
- Translate ambiguous business problems into concrete system designs and delivery plans clients can commit to.
- Flag risks, trade-offs, and scope realities directly and early, protecting both the client outcome and the team's delivery.
Now What You Need to Succeed content: list of requirements.
We'll put under Requirements
with - .
Items:
- 8+ years of software engineering experience, including 2+ years building LLM-powered systems (RAG, agents, structured extraction) that run in production, not just prototypes or internal experiments.
- Demonstrated technical leadership: engineers you have mentored or managed got measurably better because of your code review, pairing, and guidance, and you want direct reports as part of your role.
- Expert-level Python and strong full-stack fundamentals, with the judgment to choose boring, reliable technology when the problem calls for it.
- Production cloud experience (AWS, GCP, or Azure), including deploying, monitoring, and maintaining systems that clients depend on daily.
- Deep working knowledge of the modern AI stack: prompt and context engineering, evaluation, embeddings, vector search, and agent orchestration frameworks.
- A track record of owning ambiguous, high-stakes projects end to end, from problem framing through architecture, build, and post-launch iteration.
- Fluent English and clear communication on client calls; you can explain an architecture decision to a non-technical executive without losing them.
- Consulting-environment adaptability: comfort switching between client contexts, industries, and codebases without losing momentum.
- Based in San Diego, CA with reliable overlap with Colombia business hours for client and team collaboration.
- An AI-first working style: you use these tools daily to multiply your own output and teach the team to do the same.
We'll put each as
- .
Now Why Cadre AI content: benefits.
We'll put under
Benefits
with - .
Paragraphs:
- Real leadership. You will be the technical backbone of a growing engineering team, with engineers who level up because of you and the autonomy to make the calls that matter.
- 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. Early team members share in the success they help create.
- No bureaucracy. Small teams. Clear accountability. The best idea wins, regardless of who says it.
- If you want your next five years to be measured in systems running in production, businesses that work differently because you shipped, and a team of engineers who are better because you led them, this is that role.
We'll make each a
- .
Now Compensation: base pay range $165,000 – $200,000 per year.
We'll put under
Pay
with .
Now ensure we don't include any filler like "commensurate with experience". Not present.
We must output only HTML fragment, no markdown fences.
Let's craft final HTML.
We'll
for prose. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. There's no explicit application instructions. We need to include sections only when posting has real specific content. So we will include sections: About the company? Could be "About Cadre AI". But the allowed headings list includes "About the role". Not "About the company". However we could still use "About Cadre AI" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Probably we should stick to those headings where appropriate. We have content that fits: "About Cadre AI" could be considered "About the role"? Not exactly. Maybe we treat it as "About the role" (the role description). But we also have "The Role" separate. Could combine? Better to follow examples: Use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content.
We have:
- About Cadre AI (company description) -> could be "About the role"? Not ideal but maybe we can use "About the role" to describe the role and company? However we also have "The Role" section describing role. Could treat "About Cadre AI" as part of "About the role". But we might also add a heading "About Cadre AI" even if not in list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Safer to use those examples.
Thus we need to map:
- About Cadre AI -> maybe "About the role" (though it's about company). Could also omit if not needed? But we need preserve all substantive info. Could include as a
. Safer to use those examples. Thus we need to map: - About Cadre AI -> maybe "About the role" (though it's about company). Could also omit if not needed? But we need preserve all substantive info. Could include as a
under a heading like "About the role". We'll put heading
About the role
and then include paragraph about Cadre AI. - The Role -> could be "Responsibilities"? Actually "The Role" describes role overview. Could be "About the role" again but we already used. Maybe we use "Responsibilities" for What You'll Do. And "Requirements" for What You Need to Succeed. "Qualifications" maybe similar. "Skills" maybe for technical skills. "Benefits" for Why Cadre AI? Actually Why Cadre AI is about company culture, could be "Benefits". Pay is compensation. Schedule maybe not present. We need to avoid filler sections. We have no explicit schedule info, so omit Schedule. We have compensation: base pay range $165k-$200k. So we need Pay section. We have benefits? Not explicit benefits like health etc. Why Cadre AI includes culture, leadership, AI-native, access to frontier, upside, no bureaucracy. Those could be considered benefits. We'll put under Benefits. We need to ensure we don't create sections with placeholder text. Thus sections:About the role
(contains About Cadre AI paragraph)Responsibilities
(contains What You'll Do content)Requirements
(contains What You Need to Succeed content)Benefits
(contains Why Cadre AI content)Pay
(contains Compensation) We need to use- for any list of duties/requirements/benefits. So within Responsibilities, Requirements, Benefits we should convert bullet points to lists.
Let's extract content.
About Cadre AI paragraph:
"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."
We'll put that in
. The Role paragraph maybe not needed as separate; but we already used About the role heading for company description. The Role paragraph: "As Staff AI Engineer, you are the technical leader and backbone of Cadre's San Diego engineering team. At this level, your job is no longer just what you build; it is making sure every engineer around you builds better. You mentor and manage engineers, set the standard for how the team designs, reviews, and ships AI systems, and own their growth as deliberately as you own your own code. You pair that leadership with serious technical depth. You stay hands-on with the hardest builds in our client portfolio: multi-step agent systems, complex document processing pipelines, and automations that touch core revenue operations. When a problem has ambiguous requirements or no obvious solution, the team looks to you, and clients measure the result in EBITDA impact, not demos. You report to the Head of Client Engineering, and you will occasionally join client calls to walk stakeholders through what we are building and why. You thrive here if leveling up the people around you energizes you as much as shipping the system yourself." We could include this under About the role as well, or maybe under Responsibilities? But we already have Responsibilities for What You'll Do. The Role is more overview; we could merge with About the role. To avoid duplication, we can include both paragraphs under About the role. Now What You'll Do content includes bullet points under headings: Team Leadership and Mentorship, Technical Direction, Build and Ship Production AI Systems, Client Collaboration. Each has sub-bullets. We need to turn those into
- . We'll preserve each bullet as
- . For sub-bullets, we can nest
- inside
- or just keep as separate
- with dash? Probably better to nest.
We'll produce:
Responsibilities
- Team Leadership and Mentorship
- Manage and mentor two engineers on the San Diego team, owning their technical growth, code quality, and delivery.
- Set the engineering bar through rigorous code review, pairing, and reference implementations the rest of the team builds on.
- Serve as the first escalation point when engineers hit problems they cannot solve alone, teaching as you unblock.
- Build the habits, patterns, and practices that make every engineer on the team measurably better quarter over quarter.
- Technical Direction
- Drive architecture decisions across client builds: agentic workflows, RAG pipelines, document processing, and automation running in production.
- Evaluate new models, frameworks, and techniques as they emerge, and decide what enters Cadre's production toolkit.
- Turn hard-won lessons from client builds into reusable internal tooling, templates, and documentation that compound across engagements.
- Build and Ship Production AI Systems
- Stay hands-on with Cadre's most complex client systems, owning delivery end to end from LLM orchestration and evaluation to data pipelines, APIs, and cloud infrastructure.
- Make pragmatic build decisions under real constraints: client timelines, legacy systems, messy data, and measurable business outcomes on the line.
- Ship fast without sacrificing reliability; design systems that keep working long after the engagement ends.
- Client Collaboration
- Join client calls when the conversation needs technical depth, walking stakeholders through system designs, trade-offs, and progress.
- Translate ambiguous business problems into concrete system designs and delivery plans clients can commit to.
- Flag risks, trade-offs, and scope realities directly and early, protecting both the client outcome and the team's delivery.
Requirements
with- . Items: - 8+ years of software engineering experience, including 2+ years building LLM-powered systems (RAG, agents, structured extraction) that run in production, not just prototypes or internal experiments. - Demonstrated technical leadership: engineers you have mentored or managed got measurably better because of your code review, pairing, and guidance, and you want direct reports as part of your role. - Expert-level Python and strong full-stack fundamentals, with the judgment to choose boring, reliable technology when the problem calls for it. - Production cloud experience (AWS, GCP, or Azure), including deploying, monitoring, and maintaining systems that clients depend on daily. - Deep working knowledge of the modern AI stack: prompt and context engineering, evaluation, embeddings, vector search, and agent orchestration frameworks. - A track record of owning ambiguous, high-stakes projects end to end, from problem framing through architecture, build, and post-launch iteration. - Fluent English and clear communication on client calls; you can explain an architecture decision to a non-technical executive without losing them. - Consulting-environment adaptability: comfort switching between client contexts, industries, and codebases without losing momentum. - Based in San Diego, CA with reliable overlap with Colombia business hours for client and team collaboration. - An AI-first working style: you use these tools daily to multiply your own output and teach the team to do the same. We'll put each as
- .
Now Why Cadre AI content: benefits.
We'll put under
Benefits
with- . Paragraphs: - Real leadership. You will be the technical backbone of a growing engineering team, with engineers who level up because of you and the autonomy to make the calls that matter. - 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. Early team members share in the success they help create. - No bureaucracy. Small teams. Clear accountability. The best idea wins, regardless of who says it. - If you want your next five years to be measured in systems running in production, businesses that work differently because you shipped, and a team of engineers who are better because you led them, this is that role. We'll make each a
- .
Now Compensation: base pay range $165,000 – $200,000 per year.
We'll put under
Pay
with. Now ensure we don't include any filler like "commensurate with experience". Not present. We must output only HTML fragment, no markdown fences. Let's craft final HTML. We'll
- Team Leadership and Mentorship