Jobs · Human Resources · California

Training and Enablement Specialist

Cadre AI · San Diego, CA · 1 mo ago
HybridHuman Resources$80k–$90k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Cadre AI" then "The Role", then "What You'll Do", "What You Need to Succeed", "Why Cadre AI", "Compensation". We need headings using

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use headings that match content: "About Cadre AI", "The Role", "What You'll Do", "What You Need to Succeed", "Why Cadre AI", "Compensation". However guidelines: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings if applicable, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we map content to those headings where appropriate. But we have sections: About Cadre AI (maybe "About the role"? Actually "About Cadre AI" is company description, not role. Could map to "About the role"? Might be okay to use "About Cadre AI" as heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. So we can use those headings that match content. We'll produce sections: About Cadre AI, The Role (maybe "About the role"?), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What You Need to Succeed), Benefits? Not present. Why Cadre AI maybe "Benefits"? Not exactly. Could treat as "Why Cadre AI" as a section about company culture, maybe "Benefits"? But we should not create sections without real content. There's content about why join: product building, AI-native culture, access to frontier, upside, no bureaucracy. That's like benefits/why join. Could map to "Benefits". But they said only include section when posting has real, specific content for it. There is content about why join, so we can include a section like "Why Cadre AI". Use heading

Why Cadre AI

. Then Compensation: we have pay range, so include

Pay

with that info. We must not repeat job title as heading. No job ID. Remove boilerplate. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve all substantive information. Let's extract content. About Cadre AI paragraph: "Cadre AI is an AI strategy and integration firm that partners deeply with organizations to transform workflows, streamline operations, and deliver measurable business outcomes. We operate at the intersection of strategy, engineering, and adoption, ensuring AI delivers real, lasting impact for the B2B companies we serve." The Role: paragraph: "Cadre AI works with clients ranging from private equity portfolio companies to enterprise SaaS teams, and training is how we turn AI adoption into a business result instead of a workshop. You will lead the sessions that make that happen: live, high-stakes training with client teams from the C-suite to the front line, delivered well enough that clients ask for more of it. Most weeks split two ways. Some days you are in front of a client delivering a session. Other days you are heads-down building and refining the training methodology, templates, and product that make the next session better and more repeatable. You thrive here if you like being in the room with executives, can translate technical AI concepts into plain language on the fly, and get real satisfaction from building a repeatable system instead of reinventing every deck. You will report to Cadre's VP of Learning & Enablement and be part of the team that builds the reusable assets and libraries that come out of the sessions you deliver. As Cadre's training practice grows into a standalone product line, you will be one of the people building what that product actually is, not just running someone else's material." What You'll Do: bullet list? It's paragraphs with bold headings: "Client Training Delivery", "Training Product Development", "Training Design & Process Improvement". Each has sub-bullets. We need to turn each bullet into

    • . The content includes multiple sentences; we can keep as prose inside li. Let's extract: Client Training Delivery: - Lead live AI training sessions for client teams ranging from executive leadership to front-line staff, adapting delivery style and depth to the audience in the room. - Facilitate hands-on workshops that get participants using AI tools directly, not just watching a demo, since adoption is measured by what people do after the session, not how it felt. - Manage the run-of-show for each engagement: pre-session prep, materials, timing, and follow-up, so sessions land on schedule and on message. - Gather what happens in the room, prompts, questions, sticking points, and route it back into Cadre's training content so future sessions get sharper. Training Product Development: - Contribute to building Cadre's standalone, sellable training products, not just custom one-off engagements for a single client. - Help define what a repeatable training offer looks like: what is templated, what is client-specific, and what can be sold at a set price. - Bring what you learn from live delivery back into the product so it keeps improving instead of going stale. Training Design & Process Improvement: - Apply adult learning and skill transfer principles to how Cadre designs training, so sessions are built to change behavior, not just deliver content. - Build and refine templates, run-of-show docs, and delivery playbooks so training quality does not depend on any one person being in the room. - Identify where Cadre's training process is slow, or inconsistent, and fix it. What You Need to Succeed: list of requirements. We need to turn each bullet into
      • . Let's extract: - 3-5+ years designing and delivering corporate training or enablement programs, with real experience facilitating live sessions in front of senior or executive audiences, not just building self-paced content. - Working knowledge of adult learning and skill transfer principles (action mapping, Kirkpatrick, or similar), or the instinct to seek them out, since content that does not change behavior on the job does not count as a win here. - Experience contributing to or building a training curriculum, workshop series, or certification product, not just delivering someone else's material. - Experience with AI tools, Claude specifically, both as the subject you teach and as a tool you use daily to prep sessions, build assets, and iterate on content. - Comfortable with ClickUp or similar project tools to track a delivery pipeline across several concurrent client engagements without dropping a ball. - Strong verbal and written communication, with the ability to translate a technical or strategic AI concept for a non-technical executive without dumbing it down. - A bias toward building systems and templates over one-off heroics, since this role is being built to scale past any single person's calendar. - Self-directed and comfortable with ambiguity: you will help define parts of Cadre's training playbook, not just execute one that already exists. - Based in San Diego with a willingness to travel since in-person facilitation and team collaboration are part of the role. Why Cadre AI: paragraph list: - Build the product, not just deliver it. You will help shape Cadre's standalone sellable training offerings from the inside, not just run sessions someone else designed. - 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 want a seat where you're in the room with real executives one day and helping build the product the next, this is that seat. Compensation: "The base pay range for this role is $80,000 – $90,000 per year." We need to output HTML fragment only. We'll structure:

        About Cadre AI

        ...

        The Role

        ...

        Responsibilities

        • ... (Client Training Delivery bullets)
        • ...
        But we have three subcategories; maybe we keep headings inside? Could also have

        Client Training Delivery

        etc. But instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map to those standard headings. So we need sections: About the role? Actually we have About Cadre AI, but we could treat as About the role? Might be okay to use About Cadre AI as heading but not in list. However they gave examples; not strict. Safer to follow examples: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (maybe combine About Cadre AI and The Role). But we need to preserve all info; we can't lose details. We could have About the role heading containing both About Cadre AI and The Role paragraphs. That might be okay. Then Responsibilities heading for What You'll Do. Then Requirements heading for What You Need to Succeed (maybe also Qualifications and Skills). Could split: Requirements (experience), Qualifications (education?), Skills (specific). But we have all in one list; we could put all under Requirements. Then Benefits heading for Why Cadre AI (benefits of working there). Then Pay heading for compensation. Schedule not present, so omit. We must not create empty sections. Thus output:

        About the role

        Cadre AI is an AI strategy and integration firm that partners deeply with organizations to transform workflows, streamline operations, and deliver measurable business outcomes. We operate at the intersection of strategy, engineering, and adoption, ensuring AI delivers real, lasting impact for the B2B companies we serve.

        Cadre AI works with clients ranging from private equity portfolio companies to enterprise SaaS teams, and training is how we turn AI adoption into a business result instead of a workshop. You will lead the sessions that make that happen: live, high-stakes training with client teams from the C-suite to the front line, delivered well enough that clients ask for more of it. Most weeks split two ways. Some days you are in front of a client delivering a session. Other days you are heads-down building and refining the training methodology, templates, and product that make the next session better and more repeatable. You thrive here if you like being in the room with executives, can translate technical AI concepts into plain language on the fly, and get real satisfaction from building a repeatable system instead of reinventing every deck. You will report to Cadre's VP of Learning & Enablement and be part of the team that builds the reusable assets and libraries that come out of the sessions you deliver. As Cadre's training practice grows into a standalone product line, you will be one of the people building what that product actually is, not just running someone else's material.

        Responsibilities

        • Lead live AI training sessions for client teams ranging from executive leadership to front-line staff, adapting delivery style and depth to the audience in the room.
        • Facilitate hands-on workshops that get participants using AI tools directly, not just watching a demo, since adoption is measured by what people do after the session, not

Similar jobs