Account Director, Client Strategy (Remote US) - Future Opening
Directive · San Francisco, CA · 1 mo ago
RemoteRemoteMarketingFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Directive" (company description) then "Role Summary", "Key Responsibilities", "Success Metrics (KPIs)", "Who You Are" (Experience & Background, Core Competencies, Cultural Fit & Traits), "What We Offer" (benefits, salary, etc.), "Work Environment Requirements". We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we need to map headings appropriately. The instruction: use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we need to map headings appropriately. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings like About the role
, Responsibilities
, Requirements
, Qualifications
, Skills
, Benefits
, Pay
, Schedule
. However we should only include sections when posting has real specific content. We must not repeat job title as heading. Also we should not put Job ID etc.
We need to decide which sections to include based on content.
We have:
- About Directive (company description) could map to "About the role"? Actually "About the role" is about the role, not company. But we have "Role Summary". Could treat that as "About the role". So we can have About the role
with the Role Summary paragraph.
- Responsibilities: we have "Key Responsibilities" list.
- Requirements: we have "Who You Are" includes Experience & Background, Core Competencies, Cultural Fit & Traits. Could combine into Requirements and Qualifications? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide which to include based on content. We have experience/background (requirements), core competencies (skills), cultural fit (maybe qualifications). Could split: Requirements
for Experience & Background (7-12 years etc). Skills
for Core Competencies. Qualifications
for Cultural Fit & Traits? Or maybe combine.
But we must not create thin sections. We need substantive content.
We also have "Success Metrics (KPIs)" maybe could be part of Responsibilities or separate? Could be its own section but not in list of headings. The instruction says use those headings as examples, but not limited? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. However we have Success Metrics; maybe we can incorporate into Responsibilities or a separate section like "Performance Metrics" but not in list. Safer to include as a Success Metrics
? The instruction didn't forbid other headings, but gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we could also use others if needed, but better to follow examples. However Success Metrics is important; we could put under Responsibilities as a sub-list? But we need to preserve all substantive info. Could create a Success Metrics
as it's substantive. The instruction didn't explicitly forbid other headings; it just gave examples. I'd include it.
Similarly "What We Offer" includes salary, benefits, etc. We can map to Benefits, Pay, maybe Schedule? There's no schedule info besides remote-first, unlimited PTO etc. Could treat as Benefits and Pay sections.
We have salary range: $100,000- $160,000 USD with bonus eligibility. That's Pay.
We have benefits: medical, dental, vision, disability, life insurance, mental health access, physical therapy, One Medical membership, unlimited PTO, holidays, birthday off, end of year recharge, parental leave, 401(k) match, annual bonus, annual company-wide retreat. That's Benefits.
Work Environment Requirements: remote-first, need laptop, reliable internet, etc. Could be Schedule? Not exactly schedule. Could be "Work Environment" but not in list. Could be omitted? But we need to preserve all substantive info. Could create a Work Environment
but not in examples. Might be okay. However instruction says "Prefer a few substantive sections over many thin ones." So we could combine work environment details into Benefits or Requirements? Probably better to have a separate section "Work Environment". But to stick to examples, maybe we can treat as "Requirements" (since they are requirements). Actually the work environment requirements are about remote work, equipment, etc. Could be part of Requirements.
Thus we could have sections:
- About the role (Role Summary)
- Responsibilities (Key Responsibilities)
- Success Metrics (KPIs)
- Requirements (Experience & Background)
- Skills (Core Competencies)
- Qualifications (Cultural Fit & Traits)
- Pay (Salary range + bonus)
- Benefits (list of benefits)
- Work Environment (remote-first, equipment, etc.)
That's many sections but each substantive.
We must not include boilerplate like EEO, legal, etc. Already removed.
We must not include duplicated lines.
We must not include application instructions.
We must not include cookie/navigation/legal/EEO etc.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We must preserve all substantive information.
Now produce HTML fragment: only the HTML, no /, no markdown fences.
We'll use headings, then content:
About the role
,Responsibilities
,Requirements
,Qualifications
,Skills
,Benefits
,Pay
,Schedule
. However we should only include sections when posting has real specific content. We must not repeat job title as heading. Also we should not put Job ID etc. We need to decide which sections to include based on content. We have: - About Directive (company description) could map to "About the role"? Actually "About the role" is about the role, not company. But we have "Role Summary". Could treat that as "About the role". So we can haveAbout the role
with the Role Summary paragraph. - Responsibilities: we have "Key Responsibilities" list. - Requirements: we have "Who You Are" includes Experience & Background, Core Competencies, Cultural Fit & Traits. Could combine into Requirements and Qualifications? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide which to include based on content. We have experience/background (requirements), core competencies (skills), cultural fit (maybe qualifications). Could split:Requirements
for Experience & Background (7-12 years etc).Skills
for Core Competencies.Qualifications
for Cultural Fit & Traits? Or maybe combine. But we must not create thin sections. We need substantive content. We also have "Success Metrics (KPIs)" maybe could be part of Responsibilities or separate? Could be its own section but not in list of headings. The instruction says use those headings as examples, but not limited? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. However we have Success Metrics; maybe we can incorporate into Responsibilities or a separate section like "Performance Metrics" but not in list. Safer to include as a Success Metrics
? The instruction didn't forbid other headings, but gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we could also use others if needed, but better to follow examples. However Success Metrics is important; we could put under Responsibilities as a sub-list? But we need to preserve all substantive info. Could create a Success Metrics
as it's substantive. The instruction didn't explicitly forbid other headings; it just gave examples. I'd include it.
Similarly "What We Offer" includes salary, benefits, etc. We can map to Benefits, Pay, maybe Schedule? There's no schedule info besides remote-first, unlimited PTO etc. Could treat as Benefits and Pay sections.
We have salary range: $100,000- $160,000 USD with bonus eligibility. That's Pay.
We have benefits: medical, dental, vision, disability, life insurance, mental health access, physical therapy, One Medical membership, unlimited PTO, holidays, birthday off, end of year recharge, parental leave, 401(k) match, annual bonus, annual company-wide retreat. That's Benefits.
Work Environment Requirements: remote-first, need laptop, reliable internet, etc. Could be Schedule? Not exactly schedule. Could be "Work Environment" but not in list. Could be omitted? But we need to preserve all substantive info. Could create a Work Environment
but not in examples. Might be okay. However instruction says "Prefer a few substantive sections over many thin ones." So we could combine work environment details into Benefits or Requirements? Probably better to have a separate section "Work Environment". But to stick to examples, maybe we can treat as "Requirements" (since they are requirements). Actually the work environment requirements are about remote work, equipment, etc. Could be part of Requirements.
Thus we could have sections:
- About the role (Role Summary)
- Responsibilities (Key Responsibilities)
- Success Metrics (KPIs)
- Requirements (Experience & Background)
- Skills (Core Competencies)
- Qualifications (Cultural Fit & Traits)
- Pay (Salary range + bonus)
- Benefits (list of benefits)
- Work Environment (remote-first, equipment, etc.)
That's many sections but each substantive.
We must not include boilerplate like EEO, legal, etc. Already removed.
We must not include duplicated lines.
We must not include application instructions.
We must not include cookie/navigation/legal/EEO etc.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We must preserve all substantive information.
Now produce HTML fragment: only the HTML, no /, no markdown fences.
We'll use headings, then content:
Success Metrics
as it's substantive. The instruction didn't explicitly forbid other headings; it just gave examples. I'd include it. Similarly "What We Offer" includes salary, benefits, etc. We can map to Benefits, Pay, maybe Schedule? There's no schedule info besides remote-first, unlimited PTO etc. Could treat as Benefits and Pay sections. We have salary range: $100,000- $160,000 USD with bonus eligibility. That's Pay. We have benefits: medical, dental, vision, disability, life insurance, mental health access, physical therapy, One Medical membership, unlimited PTO, holidays, birthday off, end of year recharge, parental leave, 401(k) match, annual bonus, annual company-wide retreat. That's Benefits. Work Environment Requirements: remote-first, need laptop, reliable internet, etc. Could be Schedule? Not exactly schedule. Could be "Work Environment" but not in list. Could be omitted? But we need to preserve all substantive info. Could create aWork Environment
but not in examples. Might be okay. However instruction says "Prefer a few substantive sections over many thin ones." So we could combine work environment details into Benefits or Requirements? Probably better to have a separate section "Work Environment". But to stick to examples, maybe we can treat as "Requirements" (since they are requirements). Actually the work environment requirements are about remote work, equipment, etc. Could be part of Requirements. Thus we could have sections: - About the role (Role Summary) - Responsibilities (Key Responsibilities) - Success Metrics (KPIs) - Requirements (Experience & Background) - Skills (Core Competencies) - Qualifications (Cultural Fit & Traits) - Pay (Salary range + bonus) - Benefits (list of benefits) - Work Environment (remote-first, equipment, etc.) That's many sections but each substantive. We must not include boilerplate like EEO, legal, etc. Already removed. We must not include duplicated lines. We must not include application instructions. We must not include cookie/navigation/legal/EEO etc. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must preserve all substantive information. Now produce HTML fragment: only the HTML, no /, no markdown fences. We'll useheadings, then content:
for prose,
- for lists.
We need to ensure we don't create empty sections.
Let's draft.
First, About the role: combine Role Summary paragraph(s). The Role Summary includes two paragraphs: "The Account Director, Client Strategy is the senior strategic and commercial owner..." and "You’ll act as a trusted advisor..." We'll combine into one
maybe with line breaks? Could keep as one
with both sentences. Second, Responsibilities: list items from Key Responsibilities. Each bullet starts with bold heading? We'll keep the text as is. Third, Success Metrics: list KPIs. Fourth, Requirements: Experience & Background bullet points (maybe as
- ). The text includes multiple sentences; we can make each bullet.
Fifth, Skills: Core Competencies bullet points.
Sixth, Qualifications: Cultural Fit & Traits bullet points.
Seventh, Pay: salary range paragraph.
Eighth, Benefits: list items from What We Offer (including bullet points with emojis? We'll strip emojis maybe keep text). We'll need to capture each benefit.
Ninth, Work Environment: paragraph(s) from Work Environment Requirements.
Let's extract details.
From posting:
About Directive (company description) - we might not need to include because it's not about the role. But we might include as part of About the role? The instruction says About the role heading for section about the role. The company description is not about the role but could be considered background. However we might omit it to avoid thin section? It's substantive but not about role. Could we include under About the role? Might be okay to include as part of role summary? The Role Summary already describes role. The company description is extra. The instruction says preserve ALL substantive information. So we need to include company description somewhere. Could create a section "About the company" but not in examples. Could we incorporate into About the role? Might be okay to add a brief paragraph before role summary. But the heading "About the role" might be misleading if we include company description. However we could still include both under About the role: first paragraph about company, second about role. That would still be substantive.
Alternatively we could create a heading "About Directive" but not in examples. But we can still use
About Directive
. The instruction didn't forbid other headings, just gave examples. I'd rather keep to examples but we can still add a heading not listed if needed. However to be safe, we could incorporate company description into About the role section. Let's extract company description paragraph: "About Directive Directive Consulting is the leading B2B marketing agency for brands that are serious about the metrics that matter most. With over a decade of expertise and 420+ B2B brands under our belt, we've earned our reputation on real outcomes. We run through 3 divisions: Performance, Communications, and Commerce, all wired to share intelligence and answer to revenue. That system spans everything from Paid Media and Content Marketing, to PR and Paid Social, to Marketplace and Lifecycle Marketing. Tying it all together is our methodology, DiscoverabilityOS™, which aligns brand and demand to guide your ICP to choose you across every decision point. We move fast. We think boldly. We hire people who challenge the status quo, build campaigns worth talking about, and make bold brands impossible to ignore. If you live for performance, love solving hard problems, and want your work to actually mean something, you'll fit right in. At Directive, we’re always looking ahead to connect with talented professionals who excel at crafting strategies that elevate search visibility, developing compelling content, and delivering value to audiences. As we continue to grow, we’re always seeking forward-thinking individuals who thrive in fast-paced environments, are obsessed with analytics and storytelling, and are eager to make their mark in B2B tech and SaaS marketing. If you're ready to explore future opportunities and be part of a team that values creativity, strategy, and results, we’d love to connect with you!" That's a lot. We'll include as a paragraph. Now Role Summary paragraph(s): "Role Summary The Account Director, Client Strategy is the senior strategic and commercial owner of a portfolio of Directive’s most valuable and complex client relationships. This role sits at the intersection of strategy, growth, and execution, serving as the primary point of accountability for retention, expansion, and client experience across a high-value portfolio. You’ll act as a trusted advisor to VP- and C-suite stakeholders, while aligning Paid Media, SEO, CRO, Creative, and RevOps teams around unified business outcomes. Account Directors are expected to operate with autonomy, commercial rigor, and executive presence, owning the full lifecycle of the client relationship and directly influencing Directive’s Net Revenue Retention." We'll combine into one. Now Key Responsibilities list: - Own Strategic Client Relationships: Serve as the senior, day-to-day strategic lead for enterprise and high-growth clients, owning executive communication and long-term partnership value. - Drive Retention & Expansion: Develop and execute renewal, upsell, and cross-sell strategies tied directly to NRR performance. - Architect Cross-Channel Strategy: Design integrated growth plans across Paid Media, SEO/Content, CRO, Creative, and RevOps, ensuring cohesive execution and reporting. - Commercial Ownership: Own portfolio economics including forecasting, margin health, scope control, and renewal negotiations. - Lead QBRs & Executive Storytelling: Translate performance data into clear business narratives that connect marketing execution to revenue impact. - Cross-Functional Leadership: Partner with channel leads, PMs, and operations to align priorities, manage risk, and maintain delivery excellence. - Risk & Escalation Management: Proactively identify client risks and mitigate issues before escalation to executive leadership. - Team Leadership: Mentor strategists, analysts, and project teams to elevate strategic thinking and commercial accountability. We'll output each as
- . Success Metrics (KPIs): - Net Revenue Retention (NRR) - Renewal Rate - Customer Satisfaction (CSAT) Now Experience & Background (Requirements):
- ). The text includes multiple sentences; we can make each bullet.
Fifth, Skills: Core Competencies bullet points.
Sixth, Qualifications: Cultural Fit & Traits bullet points.
Seventh, Pay: salary range paragraph.
Eighth, Benefits: list items from What We Offer (including bullet points with emojis? We'll strip emojis maybe keep text). We'll need to capture each benefit.
Ninth, Work Environment: paragraph(s) from Work Environment Requirements.
Let's extract details.
From posting:
About Directive (company description) - we might not need to include because it's not about the role. But we might include as part of About the role? The instruction says About the role heading for section about the role. The company description is not about the role but could be considered background. However we might omit it to avoid thin section? It's substantive but not about role. Could we include under About the role? Might be okay to include as part of role summary? The Role Summary already describes role. The company description is extra. The instruction says preserve ALL substantive information. So we need to include company description somewhere. Could create a section "About the company" but not in examples. Could we incorporate into About the role? Might be okay to add a brief paragraph before role summary. But the heading "About the role" might be misleading if we include company description. However we could still include both under About the role: first paragraph about company, second about role. That would still be substantive.
Alternatively we could create a heading "About Directive" but not in examples. But we can still use