Vice President of Sales

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Intro about Kickmaker: description of company, vertical markets, culture, etc. This could be "About the role"? Actually "About the role" is typical heading for role description. But we have a description of company and the adventure at Kickmaker. Could be "About the role" or maybe "About the company". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We need to include sections only when posting has real specific content. Let's identify sections: - About the role: Could include description of what you'll do at Kickmaker: "Your adventure at Kickmaker At Kickmaker you’ll work on 5–10 projects annually, choosing from a wide range of industries : from robotics, medical devices, fitness tech, and automotive, to micro-mobility, beauty tech, sports exoskeletons, and AI-driven hardware. Your path evolves with your curiosity: we help you grow where your professional ambitions and personal passions meet, always connected to the latest tech breakthroughs." Also earlier description of Kickmaker: "Kickmaker is a high-tech product design and industrialization agency..." That's about company, could also go under About the role or maybe a separate "About the company" but not in list. We could incorporate into About the role. - Responsibilities: The posting lists many responsibilities under "Within Kickmaker, the employee will assume the role of VP Business, with the following main responsibilities:" then bullet list under headings: Strategy & Organisation, Sales Management & Contracting, Sales Team Management, Recruitment & Staffing, Administrative Management & Compliance, Cross-Functional Collaboration, General Responsibilities. Those are subheadings but we can treat them as list items under Responsibilities. So we need a

• for each duty. - Requirements: Experience Required: 10 to 15 years in a relevant field. Also maybe qualifications: VP Business role. Could include "Experience Required: 10 to 15 years in a relevant field." Also maybe "Location: Seattle, Washington, USA" but location is not a requirement per se but could be included under Requirements or maybe separate? The instruction says we can include Requirements section for experience, qualifications, etc. So we can put experience. - Qualifications: Not explicitly listed besides experience. Could be same as Requirements. But we could combine. - Skills: Not explicitly listed. Could infer from responsibilities: strategic thinking, sales, leadership, etc. But we should not invent. So we should not create Skills section unless explicit. - Benefits: The posting mentions: "We offer a benefits package designed to support you and your family while keeping costs low. This includes health and dental coverage, paid time off and 5 sick days for rest and renewal. You can also join our 401(k) plan to invest in your future." That's specific benefits. So we can create Benefits section with list. - Pay: The posting includes Base Salary: $250 000 / year, Annual Bonus: $100 000, Total Compensation: Up to $350 000 / year. That's specific pay info. So we can create Pay section. - Schedule: Not mentioned. No schedule info (full-time, etc). So we should not create Schedule section. We also need to avoid boilerplate: cookie/navigation/legal/EEO etc. There's a paragraph about AI tools in hiring process; that's boilerplate-ish but maybe considered part of posting? It's about hiring process, could be considered boilerplate but it's not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools paragraph is not exactly those but could be considered hiring process info; it's not application instructions. Might keep? It's not about the job itself. Safer to remove it as it's generic. Also the line about "If you would like more information about how your data is processed, please contact us." That's also generic. Remove. Also the line about "We may use artificial intelligence (AI) tools to support parts of the hiring process..." Remove. Also the line about "If you’ve ever looked at a product and thought, “I could build this better,” let’s talk!" That's fluff but maybe keep as part of About the role? It's a call to action; could be considered application instruction? It's not exactly instruction to apply but encouraging. Might be okay to keep but it's not substantive detail about role. Safer to keep only substantive info. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all specifics: company description, vertical markets, cross-disciplinary skills, maker culture, locations, number of kickers, adventure description (5-10 projects, industries list), benefits specifics, responsibilities details, pay details, experience required. We must not repeat the job title as a heading. The job title is VP Business. Not to repeat as heading. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  Kickmaker is a high-tech product design and industrialization agency... (company description) ... Present in France, China and the United States, our community counts over 250 passionate kickers and keeps growing. It is in this context that we are looking to strengthen our team in Boston, Seattle and San Fransisco. Your adventure at Kickmaker At Kickmaker you’ll work on 5–10 projects annually, choosing from a wide range of industries : from robotics, medical devices, fitness tech, and automotive, to micro-mobility, beauty tech, sports exoskeletons, and AI-driven hardware. Your path evolves with your curiosity: we help you grow where your professional ambitions and personal passions meet, always connected to the latest tech breakthroughs.

  But we need to avoid duplication: The paragraph about Kickmaker description appears at start; we can include that. We need to ensure we preserve all specifics: vertical markets list: medical, new mobility, electrification, agrotech, robotics, IOT and consumer devices. Cross-disciplinary skills: embedded AI, high-tech manufacturing automation, eco-design, industrial design and WEB 3.0 for the economy of functionality. Maker culture pillars: Passion, excitement and kindness. Also mention "real maker culture!" etc. We also need to include the video mention? That's fluff; maybe not needed. We need to include the benefits: health and dental coverage, paid time off, 5 sick days, 401(k) plan. Pay: Base Salary: $250 000 / year, Annual Bonus: $100 000, Total Compensation: Up to $350 000 / year. Experience Required: 10 to 15 years in a relevant field. Responsibilities: list each bullet. We need to decide how to format responsibilities: Could be a
  • each responsibility grouping. The posting has headings like Strategy & Organisation, then bullet points under each. We could flatten: each bullet point as a
  • . Or we could keep subheadings inside
  • ? Simpler: each responsibility bullet as
  • . We'll capture all bullet points. Let's extract bullet points: Under Strategy & Organisation: - Define and implement US commercial and organizational strategy - Monitor key performance indicators: revenue, bookings, and contribution margin - Participate in strategic decisions regarding the region and resource allocation - Contribute to the continuous improvement of management tools and sales processes - Stay informed about R&D initiatives that may impact offerings or the commercial approach Sales Management & Contracting: - Develop the US’ commercial strategy in coordination with Executive Management and ensure its execution - Lead the full sales cycle, from lead qualification to contract signature - Oversee pricing strategies and ensure offer consistency with margin targets and the company’s commercial policy - Monitor the sales pipeline, organize opportunity reviews, and manage prioritization - Manage the collective objectives of the sales team - Ensure the quality of client contracts and their compliance with standard Terms & Conditions - Update and optimize contract templates on an annual basis - Monitor and manage commercial KPIs Sales Team Management: - Structure and lead the sales team - Recruit, train, and support them in their professional development and in the development of new offerings - Ensure a high level of professionalism in client relationships, presentations, and proposals - Manage potential commercial crises in coordination with company leadership Recruitment & Staffing: - Identify commercial resource needs - Lead recruitment and onboarding of sales team members - Ensure compliance with onboarding processes, performance monitoring, and continuous training Administrative Management & Compliance: - Ensure the accuracy of commercial data in internal tools (PSA, CRM, etc.) - Guarantee the integration and updating of contractual information - Approve timesheets, expense reports, and leave requests for Sales team Cross-Functional Collaboration: - Work closely with cross-functional teams to ensure a consistent and aligned approach - Actively participate in company transformation initiatives - Act as a representative of Management for strategic clients and key accounts General Responsibilities: - More generally, as VP Business, the employee shall fully carry out their responsibilities to ensure the proper development and execution of the company’s operations, contribute to building and maintaining the company’s brand image with clients and employees, and ensure compliance with applicable procedures, both in the performance of their own duties and in relation to the employees under their supervision. We need to keep all these. Now Benefits: list: health and dental coverage, paid time off, 5 sick days for rest and renewal, 401(k) plan. Pay: list: Base Salary: $250 000 / year, Annual Bonus: $100 000, Total Compensation: Up to $350 000 / year. Experience Required: 10 to 15 years in a relevant field. We might also include Location: Seattle, Washington, USA (but location is given earlier as "Location: Seattle, Washington, USA". That's specific. Should we include it? Could be part of About the role or a separate section? Not in list headings but we could include as a paragraph under About the role. It's substantive. We'll include it. Now we need to avoid duplication: The posting also mentions "Present in France, China and the United States, our community counts over 250 passionate kickers and keeps growing. It is in this context that we are looking to strengthen our team in Boston, Seattle and San Fransisco." That's location info for hiring. We'll include. Now we need to ensure we don't include any boilerplate like "We may use artificial intelligence (AI) tools..." Remove. Also remove the line about "If you would like more information about how your data is processed, please contact us." Remove. Also remove the line about "Final hiring decisions are ultimately made by humans." That's also generic; remove. Also remove the line about "If you’ve ever looked at a product and thought, “I could build this better,” let’s talk!" Might be considered fluff; but it's not boilerplate. However it's a call to action; could be considered application instruction? It's not exactly instruction to apply but encouraging. Safer to remove as it's not substantive detail about role. Also remove the line about "An image is worth a thousand words, and this one will give you the full vibe" etc. That's fluff. Now we need to output only HTML fragment. Let's craft:

    About the role

    Kickmaker is a high-tech product design and industrialization agency. We support our customers from prototype to production run in our main