Strategic Account Executive, Install Base

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include boilerplate like EEO, legal, scam warning, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract: - Intro paragraph about Algolia: "Algolia is the retrieval intelligence layer..." That's about company, maybe "About the role"? Actually "About the role" could be description of role. The posting starts with description of Algolia and then "As an Algolia Strategic Account Manager, you will play a strategic and high-impact role..." That's about the role. So we can put that in

About the role

with paragraphs. - Responsibilities: bullet list under "Your Role Will Consist Of". Items: Own a portfolio of approximately 60 strategic, named accounts. Lead all commercial conversations including contract negotiations, renewals, and expansion opportunities. You are the primary owner of renewal discussions and account strategy. Proactively manage account health by monitoring usage signals, identifying risks early, and developing risk mitigation strategies. Work with CSMs and Solutions Engineers to assess account trajectory and flag concerns. Identify expansion opportunities across customer divisions and business units through deep understanding of their business objectives and organizational structure. Navigate internal cross-functional processes (legal, finance, deal desk) efficiently to keep contracts and renewals moving. Collaborate with our Strategic New Business AE on expansion deals in an overlay structure while owning all renewal business for your accounts. Build repeatable, scalable processes and playbooks in an ambiguous environment, operating independently and shaping sales motions as you go. - Requirements: "You Must Have" list: 7+ years of B2B SaaS sales or account management with direct ownership of renewals and expansion; 3+ years managing and closing multi-million dollar deals; Proven ability to negotiate commercial contracts with customers and internal stakeholders (legal, finance, deal desk); Experience selling SaaS, APIs, or developer-focused products. You grasp how APIs work at a conceptual level.; Conceptual fluency with the AI landscape. Discomfort with AI is a dealbreaker.; Success in complex, consultative enterprise sales with matrixed decision-making structures; Highly organized with systems to track large concurrent pipelines of renewals and expansions; Strong cross-functional collaboration with CSMs, Solutions Engineers, and internal teams; Background in startup or high-growth environments. You navigate ambiguity without needing detailed direction. - Nice To Have: list: Direct sales experience with search, commerce, eCommerce, or technical products sold to technical buyers; Background selling usage-based or consumption-based SaaS; Experience at system integrators in the search space; Track record breaking into divisions or subsidiaries within existing accounts. - "In Practice, This Looks Like Someone Who" list: Could be considered Skills or maybe additional responsibilities. It describes behaviors. Could be placed under Skills or maybe a separate section like "What Success Looks Like". But we only have predefined headings; we could put under Skills. The list includes: Maintains discipline across dozens of concurrent renewals and expansions. Nothing slips. Does research before every conversation... etc. That seems like skills/attributes. We'll put under Skills. - Pay: "On-Target Earnings Pay Range $296,000—$320,000 USD". Also mention "The annual total cash compensation range (base salary and commission) for this role reflects market pay data within this location. The exact compensation offered for this role may vary depending on specific location and job-related knowledge, technical skills, and experience; and is only one part of our Total Rewards philosophy". That's substantive. So we include Pay section with that paragraph and the range. - Benefits: Not explicitly listed besides flexible workplace strategy. There's a section "Flexible Workplace Strategy" describing remote/hybrid options. That could be considered Benefits. Also maybe other benefits not mentioned. We'll include Benefits section with that description. - Schedule: Not explicitly given besides flexible workplace strategy. Could be considered Schedule. But we have Benefits and Schedule separate. The posting mentions flexible workplace model, autonomy to choose where and when. That's schedule. We could put schedule info under Schedule. However we already used flexible workplace for Benefits. Might be better to put under Schedule: "Flexible Workplace Strategy ... autonomy to choose where they want to work and when." Benefits could be empty? But we need to include a section only when posting has real specific content. Benefits: maybe there is no explicit benefits like health, 401k, etc. So we might omit Benefits. Schedule: we have flexible workplace strategy describing remote/hybrid options. That's schedule. So we include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications? Wait Qualifications vs Requirements: The posting has "You Must Have" (requirements) and "Nice To Have" (qualifications?). Usually Qualifications are required, Nice To Have are preferred. We could map Requirements to "You Must Have" and Qualifications to "Nice To Have". Or we could combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have: - About the role: intro paragraph about role. - Responsibilities: list of duties. - Requirements: "You Must Have" list. - Qualifications: "Nice To Have" list. - Skills: "In Practice, This Looks Like Someone Who" list (skills/attributes). - Pay: compensation range and description. - Schedule: Flexible Workplace Strategy description. We should not include Benefits if none. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

About the role

...

Responsibilities

• ...
...

Similarly for Requirements, Qualifications, Skills, Pay, Schedule. Need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warning, application instructions. Also remove duplicated lines. We need to ensure we don't include the "Algolia does not discriminate..." etc. Also remove "READY TO APPLY?" etc. Let's extract exact text for each section. About the role: The paragraph(s) after intro about Algolia? Actually the posting begins: "Algolia is the retrieval intelligence layer that turns intent into trusted, decision-grade outcomes. Powering more than 1.7 trillion queries a year for over 18,000 customers with millisecond latency and 99.999% reliability, we are the recognized leader for Search and Product Discovery by top industry analyst firms. The Algolia platform turns a company's products, content, and business rules into data that humans, applications and AI agents can act upon. The result is trusted customer experiences with stronger conversions for measurable business impact. As an Algolia Strategic Account Manager, you will play a strategic and high-impact role, managing a large book of business across some of the most complex and innovative companies in the world. This role demands someone who can navigate complex contract negotiations and renewals in parallel, stay organized under pressure, and navigate internal processes efficiently, while also identifying and growing expansion opportunities within your accounts. We're looking for someone who thrives in a high-ownership environment, operates with autonomy, and brings a consultative approach to growing customer relationships." We could combine the Algolia description as part of About the role? Might be considered company overview, but still part of role description. We'll include all that as About the role. Now Responsibilities: The bullet list under "Your Role Will Consist Of". Let's capture each sentence as list item. List: - Own a portfolio of approximately 60 strategic, named accounts. - Lead all commercial conversations including contract negotiations, renewals, and expansion opportunities. You are the primary owner of renewal discussions and account strategy. - Proactively manage account health by monitoring usage signals, identifying risks early, and developing risk mitigation strategies. Work with CSMs and Solutions Engineers to assess account trajectory and flag concerns. - Identify expansion opportunities across customer divisions and business units through deep understanding of their business objectives and organizational structure. - Navigate internal cross-functional processes (legal, finance, deal desk) efficiently to keep contracts and renewals moving. - Collaborate with our Strategic New Business AE on expansion deals in an overlay structure while owning all renewal business for your accounts. - Build repeatable, scalable processes and playbooks in an ambiguous environment, operating independently and shaping sales motions as you go. We could split some into separate items if they contain multiple ideas, but it's okay. Now Requirements (You Must Have): - 7+ years of B2B SaaS sales or account management with direct ownership of renewals and expansion - 3+ years managing and closing multi-million dollar deals - Proven ability to negotiate commercial contracts with customers and internal stakeholders (legal, finance, deal desk) - Experience selling SaaS, APIs, or developer-focused products. You grasp how APIs work at a conceptual level. - Conceptual fluency with the AI landscape. Discomfort with AI is a dealbreaker. - Success in complex, consultative enterprise sales with matrixed decision-making structures - Highly organized with systems to track large concurrent pipelines of renewals and expansions - Strong cross-functional collaboration with CSMs, Solutions Engineers, and internal teams - Background in startup or high-growth environments. You navigate ambiguity without needing detailed direction. Now Qualifications (Nice To Have): - Direct sales experience with search, commerce, eCommerce, or technical products sold to technical buyers - Background selling usage-based or consumption-based SaaS - Experience at system integrators in the search space - Track record breaking into divisions or subsidiaries within existing accounts Now Skills (In Practice, This Looks Like Someone Who): - Maintains discipline across dozens of concurrent renewals and expansions. Nothing slips. - Does research before every conversation. Your questions start with "I noticed..." or "I saw in my research..." and are specific enough that only Algolia could answer them. - Ramps quickly on complex technical products and understands how modern web and AI-native platforms are built - Translates between business stakeholders (heads of eCommerce, merchandisers) and technical audiences (engineers, architects), adapting messaging appropriately - Thrives in ambiguity. You build processes and approaches as you go, then document and refine them for the team. - Has successfully turned around at-risk renewals through stakeholder management and strategic problem-solving - Thinks like an owner. You see your book of business as yours to build and protect. Now Pay: Paragraph: "The annual total cash compensation range (base salary and commission) for this role reflects market pay data within this location. The exact compensation offered for this role may vary depending on specific location and job-related knowledge, technical skills, and experience; and is only one part of our Total Rewards philosophy to compensate and recognize employees for their work." Then the range: "On-Target Earnings Pay Range $296,000—$320,000 USD" We could combine into one paragraph or separate. Now Schedule: Paragraph: "Algolia’s flexible workplace model is designed to empower all Algolians to fulfill our mission to power search and discovery with ease. We place an emphasis on an individual’s impact, contribution, and output, over their physical location. Algolia is a high-trust environment and many of our team members have the autonomy to choose where they want to work and when. We have a global presence with offices in Paris, NYC, London, Sydney and Bucharest, however we also offer many of our team members the option to work remotely either as fully remote or hybrid-remote employees. Positions listed as "Remote" are only available for remote work within the specified country. Positions listed within a specific city are only available in that location - depending on the role it may be available with either a hybrid-remote or in-office schedule." We could include that as Schedule. Now ensure we didn't include any boilerplate like "Algolia does not discriminate..." etc. Also remove "WE’RE LOOKING FOR SOMEONE WHO CAN LIVE