Sales Enablement Specialist, Enterprise

We need to output HTML fragment with sections only if real content. The posting includes Company Description, Job Description (with mission etc), Qualifications, Additional Information (Benefits). Also maybe "About the role" etc. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have: - Company Description: could be "About the role"? Actually company description is about company, not role. Could be "About the role" but that's more about role. However we could use "About the role" for description of role and mission. The posting includes "Job Description More about our mission and what we offer." Then a paragraph about mission, role description. So we could put that under

About the role

. - Responsibilities: The "Your Mission" bullet list includes several responsibilities: Top-of-Funnel Support, Deal Project Management, Cross-Functional Alignment, Opportunity Conversion, Deal Governance. Those are responsibilities. So we can have

Responsibilities

with

• each. - Qualifications: There's a "Qualifications" section with bullet points: Proactive Problem Solver, Future BD Manager, Strategic Sales Background, Detail-Oriented & Organized, Cross-Functional Collaborator, Analytically Astute, Tech-Savvy, Industry Experience. Those are qualifications/skills. Could be under

  Qualifications

  or

  Skills

  . The instruction says use headings like Qualifications, Skills. We have both qualifications and skills. We could combine them under Qualifications. Or we could have Qualifications for the bullet list and Skills for maybe tech-savvy? But better to follow instruction: use heading for Qualifications. We'll put the bullet list under

  Qualifications

  . - Benefits: Additional Information includes Benefits: "Find out more about our amazing benefits here. Included is a very generous RSU package, up to 4% 401k match, up to 60 paid days off annually." Also mentions inclusive culture etc. So we have benefits content. So we can have

  Benefits

  with
  • for each benefit: generous RSU package, up to 4% 401k match, up to 60 paid days off annually. Also maybe mention inclusive culture? That's more about culture, not benefit. Could be separate but we can include as bullet. - Pay and Schedule: Not mentioned, so we omit those sections. - Also we might include "About the company" but not required. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can also include "About the company" if we want but not in list; but better to stick to those headings. We have About the role, Responsibilities, Qualifications, Benefits. No Requirements separate; we could treat Qualifications as requirements. No Skills separate. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract all substantive sentences: Company Description: "Wise is a global technology company, building the best way to move and manage the world’s money. Min fees. Max ease. Full speed. Whether people and businesses are sending money to another country, spending abroad, or making and receiving international payments, Wise is on a mission to make their lives easier and save them money. As part of our team, you will be helping us create an entirely new network for the world's money. For everyone, everywhere." Job Description: "More about our mission and what we offer. Wise is building money without borders. To get there faster, our North America Wise Platform team is looking for a highly proactive Sales Coordinator to supercharge our Banks vertical. This isn’t your typical sales role, and it is not a pure lead-generation or hunting position. It is the perfect stepping stone for an ambitious professional who wants to master the operational side of complex, enterprise-level fintech deals before transitioning into a full Business Development role. You will act as the crucial connective tissue between our Business Development (BD) team, internal stakeholders, and prospective partners. By anticipating needs, managing cross-functional workflows, and owning deal governance, you will free up our BDs to do what they do best: sell. You won't just be taking orders; you will be the engine room of the deal-flow process, driving velocity, reducing time-to-revenue, and increasing conversion rates." Your Mission: bullet points: - Top-of-Funnel Support: Collaborate with BDs to research target accounts, build stakeholder maps, and create intelligence briefs to inform initial marketing and sales outreach. - Deal Project Management: Own the project plan for active opportunities. Assign action items, hold internal and external owners accountable, and manage risk registers to prevent deal slippage. - Cross-Functional Alignment: Partner with Compliance, Product, Legal, and Operations to drive due diligence, RFI/RFP responses, and complex partner onboarding workflows. - Opportunity Conversion: Prepare introductory materials, customize engaging sales collateral, and run data analysis on payment routes for prospective partners. - Deal Governance: Maintain pristine Salesforce data, ensure stage gates are followed correctly, and drive internal communication via dedicated opportunity Slack channels. Qualifications bullet points: - Proactive Problem Solver: You don't wait to be told what to do. You naturally anticipate the needs of a busy BD team, identify process gaps, and offer solutions before being asked. - Future BD Manager: You have the ambition and sales mindset to eventually transition into a full Enterprise Business Development role, using this position to master the lifecycle of complex sales. - Strategic Sales Background: A proven track record in sales development (BDR/SDR), sales enablement, or revenue strategy, with a clear understanding that this role extends far beyond just outreach. - Detail-Oriented & Organized: You thrive in a complex environment, easily managing multiple workstreams, RFPs, and deal flow stages simultaneously without letting details slip. - Cross-Functional Collaborator: You excel at bringing diverse groups together and navigating internal teams to achieve a shared goal. - Analytically Astute: You have the ability to interpret large volumes of data and translate it into actionable insights for the sales team. - Tech-Savvy: You are highly comfortable navigating modern revenue tech stacks. Experience with Salesforce and HubSpot is a strong plus. - Industry Experience: Previous experience working in a payment, banking, or fintech environment is highly preferred. Additional Information Benefits: "Find out more about our amazing benefits here. Included is a very generous RSU package, up to 4% 401k match, up to 60 paid days off annually. For everyone, everywhere. We're people building money without borders — without judgement or prejudice, too. We believe teams are strongest when they are diverse, equitable and inclusive. We're proud to have a truly international team, and we celebrate our differences. Inclusive teams help us live our values and make sure every Wiser feels respected, empowered to contribute towards our mission and able to progress in their careers. If you want to find out more about what it's like to work at Wise visit Wise.Jobs. Keep up to date with life at Wise by following us on LinkedIn and Instagram." We need to remove boilerplate like "For everyone, everywhere." repeated? It's part of benefits description but maybe keep. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "For everyone, everywhere." appears twice (once in company description, once in benefits). It's not boilerplate but maybe okay to keep. Duplicated lines: we should avoid repeating same sentence. It appears in company description and benefits; maybe we keep both as they are in different contexts. Not sure if considered duplicated. Safer to keep only one? The instruction says remove duplicated lines. If the exact same line appears twice, we should deduplicate. The line "For everyone, everywhere." appears exactly twice. We should keep only one occurrence. Which context? Could keep in company description (makes sense) and remove from benefits. Or keep in benefits and remove from company description. I'd keep in company description as part of mission statement, and remove from benefits. Also "We're people building money without borders — without judgement or prejudice, too." is not duplicated. We also need to remove application instructions: none present. Now craft HTML. We'll have:

    About the role

    Company description paragraph(s) plus job description paragraph(s) maybe combined.

    But we need to ensure we don't miss any substantive info. Let's combine company description and job description into About the role section. Content for About the role: - Wise is a global technology company, building the best way to move and manage the world’s money. Min fees. Max ease. Full speed. Whether people and businesses are sending money to another country, spending abroad, or making and receiving international payments, Wise is on a mission to make their lives easier and save them money. As part of our team, you will be helping us create an entirely new network for the world's money. For everyone, everywhere. - More about our mission and what we offer. Wise is building money without borders. To get there faster, our North America Wise Platform team is looking for a highly proactive Sales Coordinator to supercharge our Banks vertical. This isn’t your typical sales role, and it is not a pure lead-generation or hunting position. It is the perfect stepping stone for an ambitious professional who wants to master the operational side of complex, enterprise-level fintech deals before transitioning into a full Business Development role. You will act as the crucial connective tissue between our Business Development (BD) team, internal stakeholders, and prospective partners. By anticipating needs, managing cross-functional workflows, and owning deal governance, you will free up our BDs to do what they do best: sell. You won't just be taking orders; you will be the engine room of the deal-flow process, driving velocity, reducing time-to-revenue, and increasing conversion rates. We should keep the sentences exactly as given, preserving punctuation. Now Responsibilities section: list each mission bullet as
  • . Qualifications section: list each qualification bullet as
  • . Benefits section: list benefits: generous RSU package, up to 4% 401k match, up to 60 paid days off annually. Also maybe mention inclusive culture? That's not a benefit per se but could be included as bullet: "Diverse, equitable and inclusive workplace" etc. However the instruction says only include sections when posting has real, specific content for it. The benefits section content includes the RSU package, 401k match, paid days off. The inclusive culture statements are more about culture/values, not benefits. Could we put them under Benefits? Might be stretching. Better to keep only the explicit benefits. The inclusive statements could be omitted? But we must preserve ALL substantive information. If we omit them, we lose substantive info about culture. However we could create another section like "Culture" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; we could also use other headings but they gave examples. Safer to stick to those headings. Where to put culture info? Could be part of Benefits? Not ideal. Could be part of About the role? Not really. Could be its own section with heading like "Culture" but not in list; risk of violating instruction. However instruction says "Use

    for section headings (e.g.