Sales Relationship Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "The Role", "How You’ll Help Take Us There", "What We’re Looking For", "What You Can Expect From Us". Also there is salary range. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About Us: description of company. Could be "About the role"? Actually "About Us" is about company, not role. The allowed headings list includes "About the role". We could use that for description of role? But we have separate sections: "The Role" and "How You’ll Help Take Us There" (responsibilities). "What We’re Looking For" (requirements/qualifications/skills). "What You Can Expect From Us" (benefits). Also salary range (Pay). No schedule info. We should not repeat job title as heading. We should not include Job ID. We need to output only HTML fragment, no /. Use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, privacy notices, etc. Also remove navigation/cookie etc. Not present. We need to include sections only when posting has real specific content. So we will include: - About the role? Could combine "About Us" and "The Role"? But "About the role" heading expects description of role. We have "The Role" section describing role. So we can use

  About the role

  and put the content from "The Role" paragraph. - Responsibilities: from "How You’ll Help Take Us There" (list of duties). Use

  Responsibilities

  with
  • items. - Requirements: from "What We’re Looking For" (experience, qualifications). Could split into Requirements and Qualifications and Skills. But we can combine into Requirements heading. However we need to follow allowed headings list; we can use Requirements, Qualifications, Skills as separate if content fits. The posting includes: "6+ years of experience in a sales capacity, fixed income experience required Prior broker/dealer, buy-side firm, or other electronic trading venue experience Detailed knowledge of the fixed income markets, preferably investment grade, high yield, Emerging Markets, leveraged loans, credit derivatives and fixed income ETFs Knowledge of the MarketAxess platform and product suite Series 7 & 63 required Experience working with technology groups, becoming familiar with infrastructure, components and workflow Ability to interact and provide insight to line-traders and trading management Strong leadership qualities with outstanding interpersonal, communication and influencing skills (eg. negotiation, consultative skills) Excellent collaborative skills and ability to successfully partner across functions and lines of business High agency mindset that takes initiative, can handle objections, and create opportunities. Passion for electronic trading and the resilience to effectively promote its continued evolution through MarketAxess products Ability to be in office as needed per company requirements Travel required for training and customer engagement" We could separate: Requirements (experience, qualifications), Skills (leadership, communication, etc). Qualifications maybe same as requirements. But we can just use Requirements heading and include all. However we need to avoid filler like "commensurate with experience". Not present. - Benefits: from "What You Can Expect From Us". Use

    Benefits

    with list. - Pay: salary range. Use

    Pay

    with

    containing salary range. - Schedule: not present, so omit. We also might include "About the company"? Not in allowed headings. Could we add "About the company"? Not allowed. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we can also possibly use other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those. Thus we need to map content to those headings. We have: - About the role: we can put the description from "The Role" (first paragraph after "The Role"). - Responsibilities: the bullet list from "How You’ll Help Take Us There". - Requirements: maybe the experience/knowledge/qualifications from "What We’re Looking For" (the first part up to "Ability to interact..."). - Qualifications: maybe the leadership/communication skills etc. But we could also put those under Skills. Let's split: Requirements: experience, knowledge, certifications. Qualifications: leadership qualities, interpersonal skills, collaborative skills, agency mindset, passion for electronic trading, ability to be in office, travel. Skills: maybe technical skills like AI tools? But we have some AI-related responsibilities already in responsibilities. Could also put "Ability to interact and provide insight to line-traders and trading management" under Skills. However we need to avoid duplication. Let's decide: Requirements: 6+ years sales experience, fixed income experience required; prior broker/dealer, buy-side, or other electronic trading venue experience; detailed knowledge of fixed income markets (investment grade, high yield, EM, leveraged loans, credit derivatives, fixed income ETFs); knowledge of MarketAxess platform and product suite; Series 7 & 63 required; experience working with technology groups, familiarity with infrastructure, components, workflow. Qualifications: Ability to interact and provide insight to line-traders and trading management; strong leadership qualities with outstanding interpersonal, communication and influencing skills (negotiation, consultative skills); excellent collaborative skills and ability to partner across functions and lines of business; high agency mindset that takes initiative, can handle objections, create opportunities; passion for electronic trading and resilience to promote its continued evolution; ability to be in office as needed per company requirements; travel required for training and customer engagement. Skills: maybe we could list "Ability to automate routine tasks such as reporting, account analysis, and meeting preparation; generate tailored insights, summaries, and dealer materials using AI tools; improve speed and quality of decision making by combining AI outputs with market understanding; experiment with new AI enabled workflows to enhance client engagement and execution outcomes; partner with internal teams to support adoption of data driven and AI enabled solutions". But those are more responsibilities. However we could still put them under Skills if we want a Skills section. But we already have Responsibilities covering many of those. To avoid thin sections, we might combine Skills into Responsibilities or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Perhaps we just have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. That's substantive enough. We can put all qualifications under Requirements (or maybe Requirements and Qualifications combined). But we have allowed headings; we can omit Qualifications and Skills if we don't have distinct content. However we have content that could be considered qualifications; but we can merge into Requirements. Thus sections: - About the role: description of role (The Role paragraph). - Responsibilities: list from "How You’ll Help Take Us There". - Requirements: combined experience/knowledge/qualifications from "What We’re Looking For". - Benefits: list from "What You Can Expect From Us". - Pay: salary range. We must not include fluff like "commensurate with experience". Not present. We need to ensure we preserve all substantive information. Let's extract exact text. About Us paragraph: Not needed for About the role? Actually About the role should be about the role, not company. But we have "The Role" paragraph: "We are seeking a Sales Relationship Manager to join our Chicago-based client sales team. This role will be part of a team dedicated to marketing our products and services to this client base with unique needs. The successful candidate will work to remove barriers to adoption, improve execution outcomes, and drive consistent growth in dealer‑initiated activity. Alongside this, the role requires consistent day‑to‑day dealer coverage, including regular interaction with trading desks and structured performance reviews throughout the year. A core part of the role is the active use of AI and data‑driven workflows to identify opportunities, improve efficiency, and scale coverage across the dealer network." We should include that as About the role. Responsibilities: The bullet list after "How You’ll Help Take Us There". Let's capture each line: - Act as a senior advisor internally and externally and provide primary coverage to MarketAxess' largest and most complex customers - Create and execute a business plan for large/important/complex clients, territories or accounts; creates the vision/strategy - Consistently demonstrate long-term year over year revenue and volume growth across new and existing initiatives - Be viewed as a team leader and provide mentorship to Sales Relationship Managers - Sell MarketAxess trading capabilities to current and potential customers, focusing on investment grade and high yield - Be an expert on the market, anticipate customer needs, and pursue opportunities to increase market share - Maintain customer relationships and a sizable book of business; routinely interact with Heads of Trading (Trading management) - Proactively identify solutions that can help customers grow their business and drive new revenue - Present executive level presentations and metrics to communicate team strategy, accomplishments and goals - Develop, pursue and push through to closing, high value opportunities - Conduct detailed needs assessment for prospective partners focused on their business needs and strategic priorities - Oversee daily and weekly activities, pipelines, forecasts and closed deals to ensure above quota results based on successful pipeline management - Automate routine tasks such as reporting, account analysis, and meeting preparation - Generate tailored insights, summaries, and dealer materials using AI tools - Improve speed and quality of decision making by combining AI outputs with market understanding - Experiment with new AI enabled workflows to enhance client engagement and execution outcomes - Partner with internal teams to support adoption of data driven and AI enabled solutions We need to keep them as list items. Requirements: Combine from "What We’re Looking For". Let's extract each bullet (they are separated by line breaks but not bullet points). We'll make list items. - 6+ years of experience in a sales capacity, fixed income experience required - Prior broker/dealer, buy-side firm, or other electronic trading venue experience - Detailed knowledge of the fixed income markets, preferably investment grade, high yield, Emerging Markets, leveraged loans, credit derivatives and fixed income ETFs - Knowledge of the MarketAxess platform and product suite - Series 7 & 63 required - Experience working with technology groups, becoming familiar with infrastructure, components and workflow - Ability to interact and provide insight to line-traders and trading management - Strong leadership qualities with outstanding interpersonal, communication and influencing skills (eg. negotiation, consultative skills) - Excellent collaborative skills and ability to successfully partner across functions and lines of business - High agency mindset that takes initiative, can handle objections, and create opportunities. - Passion for electronic trading and the resilience to effectively promote its continued evolution through MarketAxess products - Ability to be in office as needed per company requirements - Travel required for training and customer engagement We could also include "Ability to be in office as needed per company requirements" and "Travel required for training and customer engagement". Those are requirements. Benefits: from "What You Can Expect From Us". Let's extract each benefit: - Hybrid Environment: Our employees enjoy a mix of working in the office and from home - Free Food: We provide free lunch for employees when they are working in the office. Plus, our offices are stocked with snacks. - Paid Time Off: Competitive PTO package including vacation and personal days, sick leave and charity days - Generous Parental Leave: Up to 20 weeks fully paid leave - 401(k): Dollar-for-dollar employer match up to $1