Application Engineer (Remote in Nashville)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the job description. Key sections: - Position: Application Engineer - Position Location: Remote in the Nashville, TN or Atlanta, GA area - On-Target Compensation: $85,000 - $130,000 (Compensation is an estimate and includes base salary plus incentives and depends on skills, knowledge, education, location, and experience) - Position Snapshot: description. - About you: description. - A Day In The Life: bullet points under subheadings: Solution Development & Engineering, Pre-Sales, Sales & Customer Engagement, Technical Support & Product Expertise, Training & Demonstrations, Travel. - Requirements: bullet list. - Perks Of Being Part Of Our Team: list of benefits. - About us: description. - Our culture: description. - EEO statement (should be removed as boilerplate). We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "About the role": could include Position Snapshot, About you, maybe A Day In The Life? Usually responsibilities separate. "Responsibilities": could be the A Day In The Life bullet points. "Requirements": the Requirements bullet list. "Qualifications": maybe education and experience? Could be part of Requirements but we can separate: Qualifications could be degree, etc. But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we might combine. "Skills": maybe technical skills list. "Benefits": the Perks list. "Pay": the compensation range. "Schedule": travel up to 25% maybe schedule? Also mention flexible schedules? There's "Many of our positions offer flexible schedules to meet your needs". Also "Sit/Stand desks for onsite office positions". Travel up to 25% could be schedule. We need to include sections only if posting has real specific content. So we need to check each. - About the role: we have Position Snapshot and About you. That's substantive. - Responsibilities: A Day In The Life bullet points (multiple). That's substantive. - Requirements: bullet list. Substantive. - Qualifications: maybe we could treat education and experience as qualifications; but we already have Requirements covering that. Could combine Requirements and Qualifications into one section? But we need to follow headings list; we can include Qualifications if we have content distinct from Requirements. Could we extract "Bachelor’s degree in electrical, Mechatronics, Robotics, or Mechanical Engineering or relevant experience" as qualification, and "Proficient in IEC 61131-3 programming languages..." as skills? Might be splitting. Better: Use Requirements for the bullet list (including education, experience, technical skills). Use Skills for maybe soft skills? But we have "You’re naturally analytical, detail-oriented, and love solving complex problems..." that's more about you (soft skills). Could go under About the role or Skills. But we need to avoid duplication. Let's think: The posting includes: - About you (soft skills, traits) - A Day In The Life (responsibilities) - Requirements (hard qualifications) - Perks (benefits) - Compensation (pay) - Travel (schedule) - Flexible schedules (schedule) - About us (company description) - maybe not needed for any section; could be omitted as boilerplate? It's substantive about company but not required sections. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep About us info somewhere. Where could it fit? Could be part of About the role? Or maybe we add a section "About the company"? Not in allowed headings. The allowed headings are limited to those eight. We must only use those headings. So we need to fit company description into one of those sections, maybe About the role? But About the role is about the role, not company. However we could include it under About the role as extra context? Might be okay but could be considered not strictly about role. However we must preserve all substantive info; we cannot drop it. So we need to include it somewhere. Perhaps we can add a paragraph under About the role that includes company overview. Or we could add a separate section "About us" but not allowed. So we must embed it within allowed headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. Likely we must only use those headings. So we need to map all content to those. Thus: - About the role: include Position Snapshot, About you, and maybe company overview (About us) and culture? Could be too much but okay. - Responsibilities: A Day In The Life bullet points. - Requirements: bullet list of hard qualifications. - Qualifications: maybe education and experience? But we already have that in Requirements. Could split: Requirements = technical skills, Qualifications = education/experience. But we have both in the bullet list; we could separate. - Skills: maybe soft skills from About you (analytical, detail-oriented, problem solver, communicator, reliable, customer-focused, collaborative). Could be placed there. - Benefits: Perks list. - Pay: compensation range. - Schedule: travel up to 25%, flexible schedules, maybe mention overnight travel. We must not include boilerplate like EEO, navigation, legal, duplicated lines, application instructions. Also remove "On-Target Compensation: $85,000 - $130,000 (Compensation is an estimate and includes base salary plus incentives and depends on skills, knowledge, education, location, and experience)" - we keep the range but maybe drop the parenthetical explanation? It's substantive? It says it's an estimate etc. Might be considered boilerplate? It's part of compensation description; we can keep the range and maybe note it's an estimate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the full sentence? It's not boilerplate; it's part of compensation. We'll keep it. Also remove duplicated lines: there may be duplicate "Job Description" at start; we ignore. Now craft HTML. We'll produce:

About the role

Position: Application Engineer. Position Location: Remote in the Nashville, TN or Atlanta, GA area. Position Snapshot: The Application Engineer provides technical expertise in motion control, drive systems, and industrial automation. This role supports customers with application development, drive and servo system selection, commissioning, troubleshooting, and machine performance optimization while partnering closely with Sales to develop differentiated motion solutions. About you: You’re naturally analytical, detail-oriented, and love solving complex problems, especially when it helps customers succeed. You bring a strong foundation in industrial automation and enjoy translating technical challenges into practical, value-driven solutions. You’re a strong communicator who partners seamlessly with sales team members to drive results, building trust quickly and becoming a go-to resource for both customers and internal teams. You are considered reliable, customer-focused, and collaborative, and you take pride in being the person others count on to get it right and keep things moving forward. About us: Lenze is a global manufacturer of electrical and mechanical drives, motion control and automation technology - offering products, drive solutions, complete automation systems, and engineering services and tools from one single source. Our products can be found in many industries, including automotive, packaging, material handling and logistics, robotics, and industrial equipment (pumps/fans). A global network of distributors and representatives makes Lenze Americas perfectly positioned to meet the motion control needs of customers worldwide. Lenze Americas, the American subsidiary of Lenze SE of Germany, is headquartered in Uxbridge, Massachusetts; corporate global headquarters are in Hamelin, Germany. Our culture: We’re powered by people. Our culture is built on collaboration, innovation, and respect—where every voice matters and every idea has the potential to shape the future. We believe in balance, supporting our team with the flexibility and resources they need to thrive both professionally and personally.

Then Responsibilities:

Responsibilities

• Solution Development & Engineering: Develop system and application solutions, including motion architecture, system topology, and software design; Create customer-specific application software and support full project lifecycle (prototype through commissioning); Configure and commission drives (VFDs, inverters, servo systems) and develop PLC/HMI programs; Support testing, start-up, and field validation of automation solutions; Capture and standardize application knowledge into reusable tools and best practices.
• Pre-Sales, Sales & Customer Engagement: Partner with Sales to develop solution concepts aligned to customer requirements; Provide technical support during pre-sales activities, including customer meetings, workshops, and presentations; Assist in preparing proposals and identifying upsell or cross-sell opportunities; Build strong customer relationships and support overall sales growth objectives.
• Technical Support & Product Expertise: Deliver advanced technical support to customers and internal teams (remote and onsite); Size and select appropriate products and solutions based on application needs; Support commissioning and troubleshooting during system start-up.
• Training & Demonstrations: Conduct product demonstrations and deliver technical training to customers and internal teams; Develop training materials, application documentation, and technical guides; Support ongoing technical development within the Sales organization.
• Travel: Travel up to 25% across the region for customer support, sales activities, and training.

But we also have Travel as schedule; maybe we keep travel under Responsibilities? Could also move to Schedule. However we have Travel bullet under A Day In The Life. We could keep it there. For Schedule section we can mention flexible schedules and overnight travel. But we need to avoid duplication. If we keep Travel under Responsibilities, we shouldn't also have Schedule section with travel. We could keep Schedule focusing on flexible schedules and overnight travel mention. Let's decide: Responsibilities includes the bullet points; we can include Travel as a bullet there. Then Schedule section can mention flexible schedules and overnight travel (maybe from Requirements: Ability to travel up to 25%, including overnight travel within the region). That's duplicate. Better to keep travel under Requirements? Actually travel is in Requirements bullet list: "Ability to travel up to 25%, including overnight travel within the region". So we could keep travel in Requirements and not duplicate in Responsibilities. But the A Day In The Life also had Travel bullet. We could omit that duplicate to avoid repetition. The instruction: remove duplicated lines. So we should remove duplicate travel line from Responsibilities. So we keep travel only in Requirements (or Schedule). Let's keep travel in Requirements (makes sense). Then Responsibilities will not have Travel bullet. Thus Responsibilities bullets: Solution Development & Engineering, Pre-Sales, Sales & Customer Engagement, Technical Support & Product Expertise, Training & Demonstrations. Now Requirements bullet list: include education, technical skills, mechatronics background, commissioning, wiring diagrams, VB, safety standards, project management, Windows OS, Microsoft tools, Ability to travel up to 25% including overnight travel. We need to keep all bullet points. Now Qualifications: maybe we can treat education and experience as qualifications; but we already have them in Requirements. To avoid thin sections, maybe we omit Qualifications section. But we need to include sections only when posting has real specific content. If we think Qualifications overlaps with Requirements, we could skip Qualifications. However the instruction list includes Qualifications as possible heading; we can omit if not needed. Let's omit Qualifications. Skills: we can extract soft skills from About you: analytical