Director, Technical Account Management
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. The posting includes: - About the Company (paragraph) - The Role You Play (description) - What You'll Do (list of responsibilities) - Experience You Bring (list of qualifications/experience) - Compensation info: base salary range, mention of performance bonus, benefits, etc. - Also mention "It is the Company's intent to pay all Team Members competitive wages..." etc. That's compensation details. - Also mention "Have we piqued your curiosity?" etc (application encouragement) - that's boilerplate/application instruction, should be removed. - EEO statement - remove. - Consent for emails - remove. - California Applicant Privacy Notice - remove. - Note about description outlines key responsibilities - maybe keep? It's a note but not boilerplate? It's a disclaimer about responsibilities; could be considered boilerplate but it's about the description. Might be safe to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The note about description outlines key responsibilities is not exactly those categories, but it's a generic note. Might be considered boilerplate? It's not EEO, not legal, not scam-warning. It's a note about the description. Could keep but it's not substantive. Probably better to drop as it's not adding value. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The note is not substantive; it's a disclaimer. Could drop. Thus sections: About the Company (maybe as
About the Company
with). The Role You Play could be considered "About the role" but we already have About the Company. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the Company (maybe not in list but okay). Could also treat "About the Company" as a heading. Then Responsibilities: from "What You'll Do". That's a list. Then Requirements/Qualifications: from "Experience You Bring". That's a list. Then Pay: we have base salary range and mention of performance bonus, benefits. So we can include Pay section with
containing that info. Benefits: The posting mentions benefits generally but not specific. It says "The total compensation package for this position may also include a performance bonus, benefits and/or other applicable incentive compensation plans". That's vague; not specific benefits. According to instruction, never create Benefits section unless posting actually states them. It does mention benefits but not specific. Might be considered not specific enough; better to not create Benefits section. Instead include that info in Pay section. Schedule: not mentioned. Thus we will have sections: About the Company, Responsibilities, Requirements (or Qualifications), Pay. We need to use
- for any list of duties/requirements/benefits. So for Responsibilities and Experience You Bring we will use
- .
We need to preserve all substantive information. Let's extract.
About the Company paragraph:
"At Playlist, life's richest moments happen when people step away from screens to move, connect, explore, and play. We're building the definitive platform for intentional living, connecting people with inspiring experiences in fitness, wellness, and beyond. With popular brands like Mindbody and ClassPass, Playlist empowers businesses and individuals, making it effortless for aspirations to become actions. Join us in reshaping technology's role to foster meaningful, real-world connections."
That's the About the Company.
The Role You Play paragraph:
"The Director of Technical Account Management leads the team responsible for technical client relationships, product adoption, and long-term customer value across our enterprise portfolio. This leader drives retention and growth of our largest customers while building operational excellence across the Technical Account Management (TAM) function. This is a hands-on, high-impact leadership role that requires significant in-person presence with customers. You will spend a meaningful share of your time with key accounts — building executive relationships, leading onsite business reviews, and running strategic planning sessions — and you will be technical enough to earn credibility in the room, whether the conversation is about an API integration, a data migration, or a complex multi-location rollout on Mindbody. The ideal candidate pairs deep technical fluency with a strategic, analytical mindset and a proven record of leading and scaling enterprise SaaS customer-facing teams. They are a dynamic people leader who inspires teams, moves quickly in a changing environment, and builds relationships customers genuinely rely on. Deep, hands-on experience with the Mindbody platform and the fitness and wellness industry sets a candidate apart."
That's a description; could be considered part of About the role. We could include it as a paragraph under a heading "About the role". But we already have About the Company. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role section. However we also have About the Company; maybe we can combine? The instruction didn't forbid having both About the Company and About the role. It gave examples; we can include both. Thus we could have:
About the Company
...
About the role
...
Then Responsibilities: from "What You'll Do". Let's extract bullet points: - Lead and scale the Technical Account Management organization through a layer of managers — hiring, developing, and holding a high bar for performance, accountability, and collaboration. - Define and communicate clear role expectations, KPIs, and career paths, supported by robust coaching and leadership frameworks. - Own revenue retention across the enterprise customer portfolio — renewals, expansions, and forecast accuracy — ensuring alignment with broader business objectives. - Build executive-level relationships through frequent, high-touch engagement: onsite business reviews, strategic planning sessions, escalation leadership, and industry events. - Serve as the senior technical voice for enterprise customers, guiding integration architecture, API and data strategy, migration planning, and complex configurations across Mindbody and the broader Playlist ecosystem. - Establish the operational processes, tooling, and reporting that elevate the enterprise function and allow it to scale without growing headcount linearly. - Partner closely with Product and Engineering to represent customer needs, influence the roadmap, drive product improvements, and ensure smooth integration support. - Anticipate risk before it surfaces — get ahead of at-risk accounts, fragile customer configurations, and gaps in the support model rather than reacting to them. - Operate with agility — reprioritizing as the business shifts, making decisions with incomplete information, and personally rolling up your sleeves on the highest-stakes accounts. That's a list. Then Experience You Bring (requirements/qualifications): - 8–12+ years of progressive leadership experience in client-facing, revenue-driving roles within enterprise SaaS — customer success, technical account management, solutions, or sales. - Experience managing managers, not only individual contributors, in a technical customer-facing organization. - Deep, hands-on experience with the Mindbody platform and its data model, APIs, integrations, and how enterprise fitness and wellness operators actually run their businesses on it. - Strong technical depth: fluency with APIs and webhooks, data models and reporting, SQL, integration and migration patterns, and the ability to translate between customer requirements and engineering realities. - Experience overseeing technical customer support, implementation, or technical account management functions. - Demonstrated success leading and developing teams that manage large, strategic enterprise accounts with measurable impact. - Track record of driving revenue growth and retention, including ownership of renewals, expansions, and forecast accuracy. - Willingness and ability to travel frequently for onsite customer meetings, strategic reviews, and industry events. - Strong operational mindset — structured problem-solving, data-driven decision-making, and process optimization. - Ability to influence senior executives and navigate complex customer organizations, driving alignment and long-term partnerships. - A proactive, high-ownership operator: you set the pace, close the loop, and bring relentless energy to the work. - Industry knowledge of, or genuine passion for, fitness, wellness, and the boutique studio ecosystem. That's a list. Pay section: The posting includes: "It is the Company's intent to pay all Team Members competitive wages and salaries that are motivational, fair and equitable. The goal of the Company's compensation program is to be transparent, attract potential employees, meet the needs of all current employees, and encourage Team Members to stay with our organization. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to skill set, depth of experience, certifications, and specific work location. The base salary range for this position in the United States is $$131,475.00 MIN to $$175,300.00 MID. The total compensation package for this position may also include a performance bonus, benefits and/or other applicable incentive compensation plans" We need to preserve all substantive information. So we include that paragraph. Note there is a double dollar sign $$ before numbers; likely a formatting artifact. We should keep as is? Probably keep the numbers as given: $$131,475.00 MIN to $$175,300.00 MID. Might be weird but we preserve. We should not create Benefits section separately; we can include benefits mention in Pay paragraph. Thus final HTML:About the Company
At Playlist, life's richest moments happen when people step away from screens to move, connect, explore, and play. We're building the definitive platform for intentional living, connecting people with inspiring experiences in fitness, wellness, and beyond. With popular brands like Mindbody and ClassPass, Playlist empowers businesses and individuals, making it effortless for aspirations to become actions. Join us in reshaping technology's role to foster meaningful, real-world connections.
About the role
The Director of Technical Account Management leads the team responsible for technical client relationships, product adoption, and long-term customer value across our enterprise portfolio. This leader drives retention and growth of our largest customers while building operational excellence across the Technical Account Management (TAM) function. This is a hands-on, high-impact leadership role that requires significant in-person presence with customers. You will spend a meaningful share of your time with key accounts — building executive relationships, leading onsite business reviews, and running strategic planning sessions — and you will be technical enough to earn credibility in the room, whether the conversation is about an API integration, a data migration, or a complex multi-location rollout on Mindbody. The ideal candidate pairs deep technical fluency with a strategic, analytical mindset and a proven record of leading and scaling enterprise SaaS customer-facing teams. They are a dynamic people leader who inspires teams, moves quickly in a changing environment, and builds relationships customers genuinely rely on. Deep, hands-on experience with the Mindbody platform and the fitness and wellness industry sets a candidate apart.
Responsibilities
- Lead and scale
- .
We need to preserve all substantive information. Let's extract.
About the Company paragraph:
"At Playlist, life's richest moments happen when people step away from screens to move, connect, explore, and play. We're building the definitive platform for intentional living, connecting people with inspiring experiences in fitness, wellness, and beyond. With popular brands like Mindbody and ClassPass, Playlist empowers businesses and individuals, making it effortless for aspirations to become actions. Join us in reshaping technology's role to foster meaningful, real-world connections."
That's the About the Company.
The Role You Play paragraph:
"The Director of Technical Account Management leads the team responsible for technical client relationships, product adoption, and long-term customer value across our enterprise portfolio. This leader drives retention and growth of our largest customers while building operational excellence across the Technical Account Management (TAM) function. This is a hands-on, high-impact leadership role that requires significant in-person presence with customers. You will spend a meaningful share of your time with key accounts — building executive relationships, leading onsite business reviews, and running strategic planning sessions — and you will be technical enough to earn credibility in the room, whether the conversation is about an API integration, a data migration, or a complex multi-location rollout on Mindbody. The ideal candidate pairs deep technical fluency with a strategic, analytical mindset and a proven record of leading and scaling enterprise SaaS customer-facing teams. They are a dynamic people leader who inspires teams, moves quickly in a changing environment, and builds relationships customers genuinely rely on. Deep, hands-on experience with the Mindbody platform and the fitness and wellness industry sets a candidate apart."
That's a description; could be considered part of About the role. We could include it as a paragraph under a heading "About the role". But we already have About the Company. The instruction says use