Sales Engineer II

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Pavion: "Pavion Connects and Protects by providing innovative fire, security, and communication integration solutions to customers across the globe. We bring industry-leading expertise to clients in enterprise, healthcare, education, government, data center, and retail industries. Global Reach. Local Service. As a global leader, Pavion specializes in the design, installation, service, and maintenance of cutting-edge fire alarm systems, critical communications, video surveillance, access control, and advanced AV technologies. Our mission is to bring clarity and transformation to safety, security, and communication through integral technology and radical service. With a commitment to safety, reliability, and operational excellence, Pavion ensures scalable, future-ready solutions tailored to meet and exceed our clients’ needs. Learn more at www.pavion.com" That's about the company. Could be "About the role"? Actually "About the role" would be description of role. The intro is about company, not role. But we can treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading with description of role. The posting includes "Pavion and our family of companies are seeking a talented and motivated Sales Engineer II to join our security business unit." That's role intro. Then "Primary Responsibilities:" list. Thus "About the role" could contain the introductory sentence(s) about the role: "Pavion and our family of companies are seeking a talented and motivated Sales Engineer II to join our security business unit." Possibly also the company description? But better to keep role-specific. We need to preserve all substantive info. So we need to include responsibilities list, basic qualifications, preferred qualifications, salary range, benefits statement. We must not include boilerplate like EEO, disclaimer, accommodation note, etc. We must not include application instructions (like contact email). Must drop those. We must not repeat job title as heading. We must not include Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and benefits package. So we can include Pay and Benefits sections. No schedule info given, so omit Schedule. We need to decide sections: About the role, Responsibilities, Requirements (maybe Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not explicit), Benefits, Pay. We have Basic Qualifications: High School Diploma or GED, 5+ years of design sales engineering experience. Preferred Qualifications: Experience with Bluebeam and Autocad. Skills: Not explicitly listed, but responsibilities mention many skills: AutoCad/Bluebeam, proposal creation, drawing, account planning, project management, RFI/RFP, product expertise, conveying requirements, relationship building, gathering requirements, pre-sales technical assistance, after-sales support, cost analysis, marketing activities, technical presentations, Statements of Work, product design, industry strategy, training, competitive product knowledge, coordinating installation. We could put those under Skills as a list. But the instruction: Use

• for any list of duties/requirements/benefits. So we can put responsibilities as list, qualifications as list, skills as list. We must not invent or summarize away detail. So we need to preserve all substantive info from responsibilities list. The responsibilities list is a long paragraph with many items separated by commas and "and". We need to break into list items preserving each duty. Must not lose any. Let's extract responsibilities: "Actively participate in the business development process, assist Sales Team during customer calls, on site customer meetings, and all technical aspects of the customer cycle, discover customer business and technical objectives and develop requirements" "Work closely with the Sales Team in the creation of proposals that present compelling technical solutions that adjust to the customer’s needs and requirements" "Mark up and produce drawings for each site in AutoCad/Bluebeam per the playbook and direction from AM" "Assist Sales Team with overall account planning as it relates to technical aspects of hardware, software, and service opportunity development" "Assist Sales Team with Project Management for complex presales engagements" "Assisting with the development of functional and technical elements of RFI/RFP responses" "During all phases of the sales cycle, assisting sales efforts with particular sales prospects as subject matter expert on all aspects of Star’s products and services" "Convey customer requirements to Product Management teams" "Developing long-term relationships with clients, in collaboration with sales representatives" "Gathering, managing and interpreting sales prospect requirements. Providing pre-sales technical assistance and product education, and after-sales support services" "Analyzing costs" "Supporting marketing activities by attending trade shows, conferences and other marketing events" "Making technical presentations and demonstrating how a product meets client needs, including developing Statements of Work and technical proposals for presentation to customers, ensuring that proposals are technically sound" "Helping in product design and product-related industry strategy" "Providing training and producing support material for other members of the sales team" "Maintain high level of knowledge of competitive Product lines, especially as it relates to technical strengths and weaknesses of the competitor’s products and what strategy Star should develop to counter" "Ensure smooth customer implementations by coordinating installation and implementation with Account Management" We need to ensure we keep all. Now Basic Qualifications: "High School Diploma or GED", "5+ years of design sales engineering experience" Preferred Qualifications: "Experience with Bluebeam and Autocad" Salary: "The salary range for this position is $XX,XXX–$YY,YYY annually. The starting salary will be determined based on qualifications, experience, education, skills, certifications, and internal equity." Benefits: "We also offer a comprehensive benefits package." We must not include placeholder like "$XX,XXX–$YY,YYY" but it's actual content (though placeholder). It's still specific? It says salary range is $XX,XXX–$YY,YYY annually. That's not actual numbers but it's what's given. We must preserve ALL substantive information; we cannot invent or summarize away detail. So we must keep that exact string. We must not create Pay section if it's only placeholder? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit with placeholder. So we include. We must not include Schedule (none). Now we need to output HTML fragment only, no markdown. We'll structure:

  About the role

  Pavion and our family of companies are seeking a talented and motivated Sales Engineer II to join our security business unit.

  Maybe also include company description? Could be part of About the role? But the instruction says About the role heading for role description. The company description is not role but could be considered "About the role"? Might be okay to include as part of role description? But better to keep only role-specific. However we must preserve ALL substantive information; if we omit company description, we lose that info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the company description somewhere. Where to put? Could be under About the role as well, as it's about the company but still substantive. The heading list includes About the role as example, but we could also add a section like "About Pavion" but not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those types. It says "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role section. Thus About the role paragraph(s) will include both the company overview and the role seeking sentence. We'll put:

  About the role

  Pavion Connects and Protects by providing innovative fire, security, and communication integration solutions to customers across the globe. We bring industry-leading expertise to clients in enterprise, healthcare, education, government, data center, and retail industries. Global Reach. Local Service. As a global leader, Pavion specializes in the design, installation, service, and maintenance of cutting-edge fire alarm systems, critical communications, video surveillance, access control, and advanced AV technologies. Our mission is to bring clarity and transformation to safety, security, and communication through integral technology and radical service. With a commitment to safety, reliability, and operational excellence, Pavion ensures scalable, future-ready solutions tailored to meet and exceed our clients’ needs. Learn more at www.pavion.com Pavion and our family of companies are seeking a talented and motivated Sales Engineer II to join our security business unit.

  That preserves all. Now Responsibilities:

  Responsibilities

  • Actively participate in the business development process, assist Sales Team during customer calls, on site customer meetings, and all technical aspects of the customer cycle, discover customer business and technical objectives and develop requirements
  • Work closely with the Sales Team in the creation of proposals that present compelling technical solutions that adjust to the customer’s needs and requirements
  • Mark up and produce drawings for each site in AutoCad/Bluebeam per the playbook and direction from AM
  • Assist Sales Team with overall account planning as it relates to technical aspects of hardware, software, and service opportunity development
  • Assist Sales Team with Project Management for complex presales engagements
  • Assisting with the development of functional and technical elements of RFI/RFP responses
  • During all phases of the sales cycle, assisting sales efforts with particular sales prospects as subject matter expert on all aspects of Star’s products and services
  • Convey customer requirements to Product Management teams
  • Developing long-term relationships with clients, in collaboration with sales representatives
  • Gathering, managing and interpreting sales prospect requirements. Providing pre-sales technical assistance and product education, and after-sales support services
  • Analyzing costs
  • Supporting marketing activities by attending trade shows, conferences and other marketing events
  • Making technical presentations and demonstrating how a product meets client needs, including developing Statements of Work and technical proposals for presentation to customers, ensuring that proposals are technically sound
  • Helping in product design and product-related industry strategy
  • Providing training and producing support material for other members of the sales team
  • Maintain high level of knowledge of competitive Product lines, especially as it relates to technical strengths and weaknesses of the competitor’s products and what strategy Star should develop to counter
  • Ensure smooth customer implementations by coordinating installation and implementation with Account Management
  Now Requirements (Basic Qualifications):

  Requirements

  • High School Diploma or GED
  • 5+ years of design sales engineering experience
  Now Qualifications (Preferred Qualifications):

  Qualifications

  • Experience with Bluebeam and Autocad
  Now Skills: Could we create a Skills section from responsibilities? But we already have responsibilities list covering duties. The instruction says use
  • for any list of duties/requirements/benefits. So we could treat responsibilities as duties list. Skills could be separate but not required. Since we already have responsibilities, we might not need Skills. However we might want to include Skills for things like technical knowledge, presentation, etc. But to avoid thin sections, we can omit Skills if not explicitly listed. The posting does not have a separate "Skills" heading. So we should not create a Skills section unless there is real specific content for it. There is no