Inside Sales
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Content:
Position Summary Inside Sales will develop and maintain relationships with potential and existing clients within the technical and manufacturing fields This position will receive inbound inquiries from potential or current customers or Outside Sales via phone and email. The successful candidate will be able to work with a sense of urgency, be customer focused and boost order profitability by upselling and recognizing opportunities to cross-sell.
Responsibilities: list of duties.
Then "Required Experience and Qualifications:" includes Associate’s degree etc.
Then "Who we are!" includes mission, vision, cultural competencies etc. This is more about company; maybe we can treat as About the role? Actually "About the role" could be the position summary. We'll put that under About the role
with paragraph.
Responsibilities: list.
Requirements/Qualifications: The posting has "Required Experience and Qualifications:" which includes degree, experience, etc. Also later "Who we are!" includes cultural competencies but that's more about company; maybe we can treat as "About the company" but not requested headings. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
- About the role: position summary paragraph.
- Responsibilities: list of duties (the bullet list after "Responsibilities").
- Requirements: maybe education/experience: Associate’s degree, 2 years related experience, experience in electrical industry and B2B sales desired.
- Qualifications: maybe skills: strong negotiation, verbal/written communication, computer/data entry, handle multiple projects, problem solve.
- Skills: maybe same as qualifications? Could combine but we need separate sections only if content.
- Benefits: posting includes "Benefits: Full benefits including medical, dental, vision, company-paid life insurance, matching 401k, paid time off, Paid Holidays (10 a year), and Milestone gifts."
- Pay: "Compensation: $30-$37/Hr."
- Schedule: maybe "Type: Full-time" and "Travel: up to 15%" and location etc. Schedule could be full-time; also maybe "Physical Demands: Occasionally lifting a maximum of 50lbs. Position sits completing computer and phone work." Not schedule. Travel is not schedule but could be considered schedule? Probably not. The instruction: include Schedule section only if posting actually states them. The posting does not explicitly state schedule like hours, shift, etc. It says Type: Full-time (that's employment type). Could treat as Schedule? Might be okay to include Schedule with full-time. But they said "Schedule" heading for schedule info. Since we have Type: Full-time, we could put that under Schedule. However they also have Location: Cerritos, CA. That's not schedule. Might be better to omit Schedule if no explicit schedule like "Monday-Friday, 8am-5pm". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Benefits and Pay. For Schedule, it does not explicitly state schedule; only Type: Full-time. Is that considered schedule? Might be ambiguous. Safer to omit Schedule section if not explicit. But we could include Schedule with "Full-time". I'd lean to include Schedule as it's a type of schedule. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Type: Full-time". That's a schedule type. So we can include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Now we need to extract content.
About the role: The position summary paragraph: "Inside Sales will develop and maintain relationships with potential and existing clients within the technical and manufacturing fields. This position will receive inbound inquiries from potential or current customers or Outside Sales via phone and email. The successful candidate will be able to work with a sense of urgency, be customer focused and boost order profitability by upselling and recognizing opportunities to cross-sell."
We need to preserve all substantive information; not invent.
Responsibilities: list after "Responsibilities". Let's extract bullet points:
- Cultivate and maintain customer relationships with electrical contractors, distributors, end users and utilities;
- Call on current, future, and past customers;
- Conduct customer visits in order to build/maintain strong customer relations as directed.
- Create and maintain positive relations with vendors, internal business unit leaders and strategic business relationships; utilize contacts to ensure our customers are getting the best value and support.
- Apply industry knowledge to offer technical / practical options to both internal and external customers; Provide consultation to customers regarding electrical solution needs.
- Boost order profitability by upselling and recognizing opportunities to cross-sell.
- Develop and win (job) opportunities.
- Develop and implement trade area sales strategy in conjunction with leadership and Outside Sales.
- Attend/support applicable customer events, trade shows.
- Work with internal departments to ensure customer transactions are processed accurately and efficiently.
- Successfully manage job function(s) by continuously demonstrating following:
- Prepare quotes and meet weekly/monthly quotation goal.
- Continuously follow up all quotes/projects daily, weekly, etc.
- Maintain and update company’s database by inputting quotes and orders in a timely and accurate way.
- Meet the monthly budget expectations/goals.
- Frequent communication with operations team.
- For specified location(s): schedule services with customers and field service team; Prepare all necessary work for field service team before services are performed; communicate service expectations and job details to field services team. Generate work orders for technicians.
- For specified location(s): Perform site visits and job walk throughs to create profitable quoting and present to the Client as directed.
- Accountable for maintaining status of projects and providing the Customers, Team and other team members with this information.
- Conduct client communication in a highly customer service-oriented manner and potentially expand the scope of project work as well as negotiate any extra charges associated with work performed.
- Other duties as assigned.
We need to format as - each item. For sub-items under "Successfully manage job function(s) by continuously demonstrating following:" we can treat as nested list? The instruction: Use
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can keep as top-level items; the sub-bullets could be separate
- as well. Simpler: treat each line as separate
- . Might lose hierarchy but okay.
We'll produce list items for each duty.
Now Requirements: "Associate’s degree in related field or experience equivalency and a minimum of 2 years related experience. Experience in the electrical industry and business to business sales experience desired."
We'll put as
- items.
Qualifications: maybe "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve."
We'll list.
Skills: Could be same as qualifications? Might duplicate. Perhaps we can treat Qualifications as education/experience, Skills as abilities. We'll split: Requirements = education/experience; Qualifications = maybe "Associate’s degree..."? Actually we already used that. Let's think: The posting has "Required Experience and Qualifications:" then bullet of education/experience and experience desired. Then after that: "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve." That seems like skills/competencies.
Thus we can map:
- Requirements: Associate’s degree in related field or experience equivalency and a minimum of 2 years related experience. Experience in the electrical industry and business to business sales experience desired.
- Qualifications: Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve.
- Skills: maybe we could leave empty or not include. But we need to decide if we include Skills section. The posting does not have a separate "Skills" heading; but we have content that could be considered skills. However we already used Qualifications for those. To avoid duplication, we could omit Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we can combine qualifications and skills into one section called Qualifications (or Requirements). But we already have Requirements for education/experience. We could have Requirements (education/experience) and Qualifications (skills). That seems reasonable. Then we don't need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We'll omit Skills.
Now Benefits: "Full benefits including medical, dental, vision, company-paid life insurance, matching 401k, paid time off, Paid Holidays (10 a year), and Milestone gifts."
Pay: "$30-$37/Hr."
Schedule: "Type: Full-time" maybe also "Travel: up to 15%" but travel is not schedule. We'll include Type: Full-time. Could also include location? Not schedule. We'll just put Full-time.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. We'll exclude the "Who we are!" mission/vision etc. Also exclude "Additional Information Travel: up to 15% Type: Full-time Location: Cerritos, CA Compensation: $30-$37/Hr. Relocation: Open Benefits: ..." We'll extract needed parts.
We need to ensure we preserve all substantive information: we have captured position summary, responsibilities, requirements, qualifications, benefits, pay, schedule (full-time). We omitted location, travel, relocation, physical demands, application details, EEO etc. That's okay per instruction to remove boilerplate/navigation/legal/EEO etc. However location might be considered substantive? Not listed as a heading we must include; but we could include location in About the role paragraph? Not required. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could fold into a short
under About the role or maybe drop. Safer to drop location as it's minor metadata. Similarly travel up to 15% maybe minor; we could drop. The instruction says fold minor metadata into a short
or drop it. So we could include a short
under About the role that includes location and travel? But we already have About the role paragraph; we could append location and travel as extra sentences. However that might be considered adding detail not originally in that paragraph but it's still present in posting. It's not boilerplate; it's location and travel. The instruction says we can fold minor metadata into a short
or drop it. So we could add a
after About the role: "Location: Cerritos, CA. Travel: up to 15%." That's fine.
Similarly Relocation: Open maybe minor; we could drop.
Physical demands maybe minor; we could drop.
Application details etc drop.
EEO drop.
Thus final HTML:
About the role
Inside Sales will develop and maintain relationships with potential and existing clients within the technical and manufacturing fields. This position will receive inbound inquiries from potential or current customers or Outside Sales via phone and email. The successful candidate will be able to work with a sense of urgency, be customer focused and boost order profitability by upselling and recognizing opportunities to cross-sell. Location: Cerritos, CA. Travel: up to 15%.
Responsibilities
- Cultivate and maintain customer relationships
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can keep as top-level items; the sub-bullets could be separate
- as well. Simpler: treat each line as separate
- . Might lose hierarchy but okay.
We'll produce list items for each duty.
Now Requirements: "Associate’s degree in related field or experience equivalency and a minimum of 2 years related experience. Experience in the electrical industry and business to business sales experience desired."
We'll put as
- items.
Qualifications: maybe "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve."
We'll list.
Skills: Could be same as qualifications? Might duplicate. Perhaps we can treat Qualifications as education/experience, Skills as abilities. We'll split: Requirements = education/experience; Qualifications = maybe "Associate’s degree..."? Actually we already used that. Let's think: The posting has "Required Experience and Qualifications:" then bullet of education/experience and experience desired. Then after that: "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve." That seems like skills/competencies.
Thus we can map:
- Requirements: Associate’s degree in related field or experience equivalency and a minimum of 2 years related experience. Experience in the electrical industry and business to business sales experience desired.
- Qualifications: Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve.
- Skills: maybe we could leave empty or not include. But we need to decide if we include Skills section. The posting does not have a separate "Skills" heading; but we have content that could be considered skills. However we already used Qualifications for those. To avoid duplication, we could omit Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we can combine qualifications and skills into one section called Qualifications (or Requirements). But we already have Requirements for education/experience. We could have Requirements (education/experience) and Qualifications (skills). That seems reasonable. Then we don't need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We'll omit Skills.
Now Benefits: "Full benefits including medical, dental, vision, company-paid life insurance, matching 401k, paid time off, Paid Holidays (10 a year), and Milestone gifts."
Pay: "$30-$37/Hr."
Schedule: "Type: Full-time" maybe also "Travel: up to 15%" but travel is not schedule. We'll include Type: Full-time. Could also include location? Not schedule. We'll just put Full-time.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. We'll exclude the "Who we are!" mission/vision etc. Also exclude "Additional Information Travel: up to 15% Type: Full-time Location: Cerritos, CA Compensation: $30-$37/Hr. Relocation: Open Benefits: ..." We'll extract needed parts.
We need to ensure we preserve all substantive information: we have captured position summary, responsibilities, requirements, qualifications, benefits, pay, schedule (full-time). We omitted location, travel, relocation, physical demands, application details, EEO etc. That's okay per instruction to remove boilerplate/navigation/legal/EEO etc. However location might be considered substantive? Not listed as a heading we must include; but we could include location in About the role paragraph? Not required. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could fold into a short
under About the role or maybe drop. Safer to drop location as it's minor metadata. Similarly travel up to 15% maybe minor; we could drop. The instruction says fold minor metadata into a short
or drop it. So we could include a short
under About the role that includes location and travel? But we already have About the role paragraph; we could append location and travel as extra sentences. However that might be considered adding detail not originally in that paragraph but it's still present in posting. It's not boilerplate; it's location and travel. The instruction says we can fold minor metadata into a short
or drop it. So we could add a
after About the role: "Location: Cerritos, CA. Travel: up to 15%." That's fine. Similarly Relocation: Open maybe minor; we could drop. Physical demands maybe minor; we could drop. Application details etc drop. EEO drop. Thus final HTML:
About the role
Inside Sales will develop and maintain relationships with potential and existing clients within the technical and manufacturing fields. This position will receive inbound inquiries from potential or current customers or Outside Sales via phone and email. The successful candidate will be able to work with a sense of urgency, be customer focused and boost order profitability by upselling and recognizing opportunities to cross-sell. Location: Cerritos, CA. Travel: up to 15%.
Responsibilities
- Cultivate and maintain customer relationships
- for lists.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. We'll exclude the "Who we are!" mission/vision etc. Also exclude "Additional Information Travel: up to 15% Type: Full-time Location: Cerritos, CA Compensation: $30-$37/Hr. Relocation: Open Benefits: ..." We'll extract needed parts.
We need to ensure we preserve all substantive information: we have captured position summary, responsibilities, requirements, qualifications, benefits, pay, schedule (full-time). We omitted location, travel, relocation, physical demands, application details, EEO etc. That's okay per instruction to remove boilerplate/navigation/legal/EEO etc. However location might be considered substantive? Not listed as a heading we must include; but we could include location in About the role paragraph? Not required. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- items.
Qualifications: maybe "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve."
We'll list.
Skills: Could be same as qualifications? Might duplicate. Perhaps we can treat Qualifications as education/experience, Skills as abilities. We'll split: Requirements = education/experience; Qualifications = maybe "Associate’s degree..."? Actually we already used that. Let's think: The posting has "Required Experience and Qualifications:" then bullet of education/experience and experience desired. Then after that: "Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve." That seems like skills/competencies.
Thus we can map:
- Requirements: Associate’s degree in related field or experience equivalency and a minimum of 2 years related experience. Experience in the electrical industry and business to business sales experience desired.
- Qualifications: Strong negotiation skills, strong verbal and written communication skills. Able to communicate with a variety of individuals. Strong computer and data entry skills. Able to handle multiple projects, able to problem solve.
- Skills: maybe we could leave empty or not include. But we need to decide if we include Skills section. The posting does not have a separate "Skills" heading; but we have content that could be considered skills. However we already used Qualifications for those. To avoid duplication, we could omit Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we can combine qualifications and skills into one section called Qualifications (or Requirements). But we already have Requirements for education/experience. We could have Requirements (education/experience) and Qualifications (skills). That seems reasonable. Then we don't need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We'll omit Skills.
Now Benefits: "Full benefits including medical, dental, vision, company-paid life insurance, matching 401k, paid time off, Paid Holidays (10 a year), and Milestone gifts."
Pay: "$30-$37/Hr."
Schedule: "Type: Full-time" maybe also "Travel: up to 15%" but travel is not schedule. We'll include Type: Full-time. Could also include location? Not schedule. We'll just put Full-time.
Now we need to output HTML fragment only, no /. Use