Senior Customer Support and Market Data Specialist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real specific content. Prefer few substantive sections over many thin ones.
We need to parse the job posting.
Key sections:
- Position Summary (could be "About the role"): description of role.
- Position Details: Salary range, location, full-time, hybrid, reporting to.
- Primary Responsibilities: list of duties.
- Minimum Qualifications: list.
- Preferred Qualifications: list.
- Overview: About Yes Energy (company description) maybe not needed? Could be "About the company" but not required; we can include if substantive.
- Culture: description.
- Compensation And Benefits: description.
We need to decide which sections to include. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some.
We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can map:
- About the role: Position Summary (maybe also overview of company? but we can keep role summary).
- Responsibilities: Primary Responsibilities list.
- Requirements: Minimum Qualifications (maybe also Preferred Qualifications? Could be Qualifications section includes both minimum and preferred? But we have separate Qualifications and Skills headings. Could treat Qualifications as minimum qualifications, Skills as preferred qualifications (skills). Or we could combine.
- Benefits: Compensation And Benefits description.
- Pay: Salary range from Position Details.
- Schedule: Location, full-time, hybrid, reporting to maybe? Actually schedule could be hybrid - 2 days in office, full-time.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid.
Schedule: we have full-time, hybrid - 2 days in office. That's specific.
Benefits: we have description of benefits package.
Requirements: Minimum Qualifications list.
Skills: Preferred Qualifications list (skills like SQL, Python, etc.)
We also have About the role: Position Summary.
We also might include About the company? Not required but could be under About the role? Probably not needed.
We must remove boilerplate: EEO, legal, etc. Also remove "At Yes Energy, we value connecting directly with candidates..." etc. Also remove "Overview ABOUT YES ENERGY" etc? That's company overview; could be considered substantive but maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." Could include a short paragraph about company under About the role? But we already have role summary. Might be okay to include a brief "About Yes Energy" as part of About the role? However the instruction says use headings for sections like About the role, Responsibilities, etc. So we should stick to those.
Thus output:
About the role
... position summary ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Pay
Salary range: $60,000 - $90,000 plus bonus
Schedule
Full-time, hybrid – 2 days in the office
Benefits
- Medical insurance
- 401(k) Plan with matching
- Flexible vacation
- Flexible work schedules
- Professional development funding (formal and informal)
We might also include location? Could be under Schedule or separate but we have no heading for location. Could add location under Schedule? Or we could add a short paragraph under Schedule: "Location: Yes Energy Core Offices (Boulder, CO HQ; Boston, MA; Chicago, IL; Glendora, CA; Richmond, VA; London, UK; Auckland, NZ; Bucharest, Romania). Reporting to: VP, Customer Experience." But we have no heading for location or reporting. Could incorporate into Schedule or maybe under About the role? Better to add a short paragraph under Schedule: include location and reporting.
But we must not invent sections; we can add details inside existing sections.
Thus Schedule section could contain: "Full-time, hybrid – 2 days in the office. Located at Yes Energy Core Offices (multiple locations). Reports to VP, Customer Experience."
Now ensure we preserve all substantive info: we need to include details from Position Details: Salary range, location, full-time, hybrid, reporting to. We have captured salary range in Pay, location and reporting in Schedule, full-time/hybrid also in Schedule.
We need to include the part about "Position Details Salary range: $60,000 - 90,000 plus bonusLocation: Yes Energy Core Offices Full-timeHybrid - 2 days in the officeReporting to: VP, Customer Experience". We have that.
Now Responsibilities: need to list all bullet points from Primary Responsibilities. Let's extract them:
- Serve as a key member of Yes Energy’s Customer Support Team - providing exceptional customer service, answering questions, troubleshooting issues and providing technical support to internal and external customers.
- Assist with onboarding new support personnel through shadowing to help them develop product and technical knowledge.
- Lead and facilitate troubleshooting calls with customers.
- Help customers understand optimal workflows to meet their needs.
- Serve as a subject matter expert for products within the assigned product lines.
- Build skills working with Yes Energy software, including our API and SQL data products.
- Serve as a subject matter expert on the team within assigned product line and able to provide training and coaching for newer team members when asked.
- Work directly with users to understand and resolve their application-related issues.
- Manage, track, and resolve support inquiries and issues via a Client Relationship Management (CRM) system per service level agreements.
- Clearly and thoroughly documents customer issues for development staff.
- Coordinate with the technical writer to create and maintain internal knowledge base documentation for the broader support team and facilitate knowledge sharing between internal subject matter experts and Tier 1 support staff.
- Create, update, and close Client Relationship Management (CRM) inquiries/cases and other problem resolution tickets within designated timeframes.
- Work closely with the Yes Energy Customer Success team to communicate trends, customer risks, and opportunities.
- Facilitate communication amongst the broader support team for known issues and new products and features.
We need to preserve all; we can combine some sentences but must not lose info. We'll keep each as separate - .
Now Requirements (Minimum Qualifications):
- Minimum of 3 years experience in technical customer support, helpdesk, and technical sales roles.
- Comfortable communicating solutions to customers across various communication mechanisms: IM, phone, email, formal presentations, etc.
- Exceptional customer service with the ability to digest complex technical information and translate that back to customers concisely.
- Ability to troubleshoot and resolve advanced technical support and application issues.
- Proven ability to deliver effective customized training based on customer needs and use cases.
- Leadership skills are necessary to set a standard of excellence and guide teams through change.
- A mind for process improvement as opposed to making do with inefficiencies.
Now Skills (Preferred Qualifications):
- Energy industry experience or experience in equities/commodities trading.
- Proficiency in SQL and Python and familiarity with APIs.
- Data science and analysis experience.
- Experience interacting with CRM software (Freshdesk, Jira, Salesforce, etc.).
- Experience with Yes Energy’s products will set you apart from other candidates.
Now Benefits: from Compensation And Benefits:
- Highly competitive salaries and real bonuses that are achievable and that you can impact.
- Benefits package: medical insurance, a 401(k) Plan with matching, flexible vacation, and flexible work schedules.
- Yes Energy encourages and funds investment in both formal and informal professional development.
- Dedicated to building a diverse, inclusive, and authentic workplace.
We could list as bullet points.
Now Pay: we already have salary range.
Now Schedule: full-time, hybrid – 2 days in the office. Location: Yes Energy Core Offices (list locations). Reporting to: VP, Customer Experience.
We need to avoid duplication: we already listed salary range in Pay; we should not repeat in Benefits? Benefits includes "highly competitive salaries and real bonuses". That's okay but we might keep it as part of Benefits description. However we should avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that sentence about salaries and bonuses in Benefits as well. But we already have Pay section with salary range. It's okay to have both; they are not duplicate exactly; Pay gives range, Benefits mentions competitive salaries and bonuses. We'll keep both.
Now we need to ensure we don't include boilerplate like EEO, legal, etc. We removed those.
Now output only HTML fragment.
Let's craft.
We'll need to escape any special characters? Not needed.
We'll produce:
About the role
The Senior Customer Support and Market Data Specialist plays a critical, front-line role in ensuring that Yes Energy lives up to our brand promises: we promise prompt, friendly, and smart customer support and are committed to collaborative partnerships with our customers. The position serves as the most technically focused member of the Customer Support Team, answering customer questions related to technical support and application usage. More than any other member of the Customer Support Team, the Senior Support and Market Data Specialist needs to understand how our products work “under the hood” to facilitate efficient troubleshooting and communication of issues and enhancement requests. This position also plays a vital role in maintaining customer relationships, ensuring customer satisfaction, and helping customers optimize application usage. This role ensures interactions are properly documented and communicated to stakeholders within Yes Energy.
Responsibilities
- Serve as a key member of Yes Energy’s Customer Support Team - providing exceptional customer service, answering questions, troubleshooting issues and providing technical support to internal and external customers.
- Assist with onboarding new support personnel through shadowing to help them develop product and technical knowledge.
- Lead and facilitate troubleshooting calls with customers.
- Help customers understand optimal workflows to meet their needs.
- Serve as a subject matter expert for products within the assigned product lines.
- Build skills working with Yes Energy software, including our API and SQL data products.
- Serve as a subject matter expert on the team within assigned product line and able to provide training and coaching for newer team members when asked.
- Work directly with users to understand and resolve their application-related issues.
- Manage, track, and resolve support inquiries and issues via a Client Relationship Management (CRM) system per service level agreements.
- Clearly and thoroughly documents customer issues for development staff.
- Coordinate with the technical writer to create and maintain internal knowledge base documentation for the broader support team and facilitate knowledge sharing between internal subject matter experts and Tier 1 support staff.
- Create, update, and close Client Relationship Management (CRM) inquiries/cases and other problem resolution tickets within designated timeframes.
- Work closely with the Yes Energy Customer Success team to communicate trends, customer risks, and opportunities.
- Facilitate communication amongst the broader support team for known issues and new products and features.
Requirements
- Minimum of 3 years experience in technical customer support, helpdesk, and technical sales roles.
- Comfortable communicating solutions to customers across various communication
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real specific content. Prefer few substantive sections over many thin ones. We need to parse the job posting. Key sections: - Position Summary (could be "About the role"): description of role. - Position Details: Salary range, location, full-time, hybrid, reporting to. - Primary Responsibilities: list of duties. - Minimum Qualifications: list. - Preferred Qualifications: list. - Overview: About Yes Energy (company description) maybe not needed? Could be "About the company" but not required; we can include if substantive. - Culture: description. - Compensation And Benefits: description. We need to decide which sections to include. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: Position Summary (maybe also overview of company? but we can keep role summary). - Responsibilities: Primary Responsibilities list. - Requirements: Minimum Qualifications (maybe also Preferred Qualifications? Could be Qualifications section includes both minimum and preferred? But we have separate Qualifications and Skills headings. Could treat Qualifications as minimum qualifications, Skills as preferred qualifications (skills). Or we could combine. - Benefits: Compensation And Benefits description. - Pay: Salary range from Position Details. - Schedule: Location, full-time, hybrid, reporting to maybe? Actually schedule could be hybrid - 2 days in office, full-time. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid. Schedule: we have full-time, hybrid - 2 days in office. That's specific. Benefits: we have description of benefits package. Requirements: Minimum Qualifications list. Skills: Preferred Qualifications list (skills like SQL, Python, etc.) We also have About the role: Position Summary. We also might include About the company? Not required but could be under About the role? Probably not needed. We must remove boilerplate: EEO, legal, etc. Also remove "At Yes Energy, we value connecting directly with candidates..." etc. Also remove "Overview ABOUT YES ENERGY" etc? That's company overview; could be considered substantive but maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." Could include a short paragraph about company under About the role? But we already have role summary. Might be okay to include a brief "About Yes Energy" as part of About the role? However the instruction says use headings for sections like About the role, Responsibilities, etc. So we should stick to those. Thus output:
About the role
... position summary ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
Salary range: $60,000 - $90,000 plus bonus
Schedule
Full-time, hybrid – 2 days in the office
Benefits
- Medical insurance
- 401(k) Plan with matching
- Flexible vacation
- Flexible work schedules
- Professional development funding (formal and informal)
About the role
The Senior Customer Support and Market Data Specialist plays a critical, front-line role in ensuring that Yes Energy lives up to our brand promises: we promise prompt, friendly, and smart customer support and are committed to collaborative partnerships with our customers. The position serves as the most technically focused member of the Customer Support Team, answering customer questions related to technical support and application usage. More than any other member of the Customer Support Team, the Senior Support and Market Data Specialist needs to understand how our products work “under the hood” to facilitate efficient troubleshooting and communication of issues and enhancement requests. This position also plays a vital role in maintaining customer relationships, ensuring customer satisfaction, and helping customers optimize application usage. This role ensures interactions are properly documented and communicated to stakeholders within Yes Energy.
Responsibilities
- Serve as a key member of Yes Energy’s Customer Support Team - providing exceptional customer service, answering questions, troubleshooting issues and providing technical support to internal and external customers.
- Assist with onboarding new support personnel through shadowing to help them develop product and technical knowledge.
- Lead and facilitate troubleshooting calls with customers.
- Help customers understand optimal workflows to meet their needs.
- Serve as a subject matter expert for products within the assigned product lines.
- Build skills working with Yes Energy software, including our API and SQL data products.
- Serve as a subject matter expert on the team within assigned product line and able to provide training and coaching for newer team members when asked.
- Work directly with users to understand and resolve their application-related issues.
- Manage, track, and resolve support inquiries and issues via a Client Relationship Management (CRM) system per service level agreements.
- Clearly and thoroughly documents customer issues for development staff.
- Coordinate with the technical writer to create and maintain internal knowledge base documentation for the broader support team and facilitate knowledge sharing between internal subject matter experts and Tier 1 support staff.
- Create, update, and close Client Relationship Management (CRM) inquiries/cases and other problem resolution tickets within designated timeframes.
- Work closely with the Yes Energy Customer Success team to communicate trends, customer risks, and opportunities.
- Facilitate communication amongst the broader support team for known issues and new products and features.
Requirements
- Minimum of 3 years experience in technical customer support, helpdesk, and technical sales roles.
- Comfortable communicating solutions to customers across various communication