Enterprise Sales Manager

Mistral · New York, NY · 1 mo ago

On-siteBusiness DevelopmentFull-time

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mistral" (company description) then "The Role", "What You Will Do", "What We're Looking For", "What we offer". Also maybe "Privacy Policy" is boilerplate to remove. Also "About Mistral" is company description; we can treat as a section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? They said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings when applicable. We have content: About Mistral (company overview) could be "About the role"? Actually "About Mistral" is about company, not role. Could be "About the role" is not present. But we could still use "About the role" heading for the role description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content accordingly. We have sections: The Role (overview), What You Will Do (responsibilities), What We're Looking For (requirements/qualifications/skills), What we offer (benefits). Also About Mistral (company description) maybe could be included as a brief intro but not required; we could include as a paragraph before headings? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include the About Mistral paragraph somewhere. Could be a
before any heading, or we could make a heading "About Mistral" but not in the list; but they said use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Safer to follow examples: use those headings only when we have content. We have content for About the role? Not exactly; we have "The Role" which is a description of the role. Could map to "About the role". Use

About the role

and put the paragraph from "The Role". Then responsibilities: "What You Will Do" ->

Responsibilities

with list items. Then requirements/qualifications/skills: "What We're Looking For" includes experience, track record, etc. Could split into Requirements and Skills? But we can combine into one section maybe "Requirements". However they said prefer a few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements, Benefits. That's four sections. We need to use

for any list of duties/requirements/benefits. So for responsibilities we need a list. For requirements we need a list. For benefits we need a list. We must not include boilerplate like Privacy Policy, etc. We must not include headings with filler text like "Pay" or "Schedule" if not present. So we omit those. We need to preserve all substantive information: include the About Mistral paragraph, the role description paragraph, the responsibilities bullet points (converted from the "What You Will Do" sections), the requirements bullet points (from "What We're Looking For"), and the benefits paragraph (from "What we offer"). We need to ensure we don't lose any details. Let's extract. About Mistral paragraph: "Mistral provides full-stack AI solutions: from frontier models to developer tools, applications, and compute. We partner with enterprises tackling the hardest problems across high-stakes industries like finance, manufacturing, defense, healthcare, and the public sector, co-creating customized AI systems that they can run on their terms. We are a dynamic, collaborative team passionate about AI and its potential to transform society. Our diverse workforce thrives in competitive environments and is committed to driving innovation. Our teams are distributed between Europe, North America, Asia and the Middle East. We are creative, low-ego and team-spirited." The Role paragraph (under "The Role"): "As a US Enterprise Sales Manager at Mistral AI, you will lead and grow a US Enterprise Sales Team, with a focus on acquiring and expanding high-value new logos and customers in your region. Based in San Francisco or New York City, you will focus on recruiting and developing a team of high-performing Enterprise Account Executives; work closely with the RVP of US Enterprise and cross-functional partners to drive execution against the North America business strategy; and manage your regional business with operational excellence, including revenue forecasting, pipeline analysis, and performance tracking. You will report to the RVP of US Enterprise, and play a key role in accelerating Mistral’s growth in the US market." What You Will Do section includes multiple bullet-like sentences but not formatted as list. We need to convert to
- . Let's parse: - Recruiting * Recruit, hire, and onboard a high-performance and diverse team of Enterprise Account Executives to support growth in your region * Maintain a strong network of talented candidates to accelerate time to hire - Developing * Coach, inspire, and manage performance of the team to drive both individual and team-level performance * Drive accountability to achievement of key performance metrics * Conduct regular performance reviews and career planning sessions with AEs * Conduct regular pipeline reviews, account planning sessions, opportunity reviews, and forecast calls to ensure AEs are in a position to exceed quota - Executing * Own the revenue target for your regional team, ensuring consistent growth in new logo acquisition and customer expansion * Effectively translate North America sales strategy into a set of actionable sales activities for your team and region * Provide accurate revenue forecasting and pipeline analysis to senior leadership * Refine sales plays tailored to your regional context and trends, and share learnings and feedback with leadership and other regional leaders * Support AEs in deals by building executive relationships within key Enterprise accounts * Collaborate effectively internally with cross-functional teams (e.g., legal, finance, product), as well as externally with key members of the partners ecosystem (e.g., cloud partners, SIs, etc.) * Partner closely with Product and Engineering to communicate market feedback and influence product roadmap to support Enterprise customer needs * Work closely with Global Sales Leadership to share market feedback and trends, and ensure continued execution against the global and regional strategies We need to preserve all these as list items. Could flatten into a single list under Responsibilities. What We're Looking For bullet points (each line starts with a number? Actually it's a paragraph with numbered items? Let's extract: "What We're Looking For 10+ years of experience in B2B technology sales, with 2+ years in sales management or team leadership roles Track record of success building and managing high-performing sales teams, consistently exceeding revenue targets Proven experience selling to large enterprise organizations, with multiple stakeholders and complex buying processes Strong understanding of the US AI market, including common use cases, key industries, competitive landscape, and latest developments Deep fluency in value selling best practices, with experience in Command of the Message, or another similar value-based methodology Experience in a highly technical sales environment Expertise with sales forecasting, pipeline management, and business analysis Can clearly articulate a leadership philosophy, with experience motivating teams, managing performance, and establishing a clear operating rhythm" We need to convert each line to
- . Could group as Requirements. What we offer paragraph: "We offer a comprehensive benefits package designed to support your well-being, growth, and work-life balance. Benefits vary by country and may include healthcare coverage, parental leave, retirement plans, relocation support, wellness programs, meal and transportation allowances, and other location-specific perks. For the most up-to-date details on benefits available in your location, please refer to our Benefits page." We need to keep that as a paragraph? But instruction: Use
  - for any list of duties/requirements/benefits. Benefits are listed in the sentence: "may include healthcare coverage, parental leave, retirement plans, relocation support, wellness programs, meal and transportation allowances, and other location-specific perks." That's a list; we should convert to
    - . Also the first sentence about comprehensive benefits package could be a
      before the list. The last sentence about referring to Benefits page could be considered boilerplate? It's not exactly boilerplate but it's a reference; maybe we keep it as part of the paragraph? It's not a list item. We'll keep as a
      after the list? Actually we could incorporate:
      We offer a comprehensive benefits package designed to support your well-being, growth, and work-life balance. Benefits vary by country.
      then
      - healthcare coverage

Enterprise Sales Manager

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? They said "Use

About the role

Responsibilities

About the role

Responsibilities

Requirements

Benefits

Similar jobs