Forward Deployed Engineer

We need to output HTML fragment with sections: About the role (but the page already shows job title, we should not repeat job title as heading). The posting includes "About Forterra" (company description) and "About The Role". We should not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About Forterra (company overview) – could be "About the role"? Actually "About Forterra" is company description, not role. Could be "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (maybe summarizing role description). The posting includes "About The Role" heading with description. So we can put that under

About the role

with paragraphs. Then we have "What You'll Do" which is responsibilities. So we can have

Responsibilities

with

• items. Then we have "Qualifications" section with bullet list of qualifications (some are paragraphs). Also there is "Preferred Qualifications". Could combine under Requirements or Qualifications. We'll have

  Qualifications

  with
  • for required qualifications, maybe separate required vs preferred? But we can list all. We have "US Salary Range $120,000—$150,000" – that's Pay. So we need a Pay section with that info. Also there is a Benefits section with details. So we need Benefits heading. Schedule? Not mentioned. Travel up to 75% is mentioned under Qualifications? Actually under "Travel And Field Operations" – that's about travel expectations, could be Schedule? But schedule not given. We could omit Schedule if no specific schedule. We should not include sections with placeholder text. So we will include About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statements, clearance eligibility line? That might be considered boilerplate? It's about clearance eligibility – maybe keep? It's substantive? It's a requirement maybe. But it's about clearance eligibility; could be considered part of Qualifications? It says "CLEARANCE ELIGIBILITY - This position may require eligibility to obtain and maintain a U.S. security clearance." That's substantive. We should keep it, maybe under Qualifications. Also we need to remove duplicated lines, like the benefits paragraph that repeats salary range statement. We'll keep only unique. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Forterra paragraph: "At Forterra, we are unleashing autonomy at scale to transform the battlefield. Our mission is to build the foundational platforms that enable an intelligent ecosystem to coordinate, adapt, and execute with speed and precision even in the uncertainty and disruption of modern conflict. In an era marked by rapid technological change and evolving threats, we design for flexibility, survivability, and operational dominance. Forterra delivers weapons, sensors, and battlefield effects through integrated autonomous networks reaching operational areas faster, safer, and without placing human lives at risk. Our systems operate with distributed control, dynamic routing, and real-time responsiveness, enabling sustained advantage across complex mission environments." About The Role: "The Field Service Engineer plays a critical role in delivering advanced technical support across hardware and software systems to ensure customer success, system reliability, and operational excellence. Reporting to the Director of Customer Success, this role focuses on hands-on field support to diagnose, troubleshoot, and resolve complex system issues. The Field Service Engineer is responsible for maintaining system uptime, supporting deployments, and serving as a technical expert for customers, with a strong focus on root cause analysis, system integration, and continuous improvement. This role will support extended deployments in operational field environments, including possible active combat zones." What You'll Do: list bullet points. We need to convert each bullet into
  • . The bullet points are: - Customer Product Support: Monitor customer system performance and proactively identify issues across hardware and software components. Provide on-site and remote support to diagnose and resolve complex system issues, minimizing downtime. Serve as a primary technical escalation point for customers, particularly for software, and networking-related issues. - Technical Expertise And Troubleshooting: Diagnose and resolve issues across systems, networking infrastructure, and software. Perform log analysis, system health checks, and root cause investigations for recurring or critical failures. Support system installations, upgrades, patches, and configuration changes in field environments. Troubleshoot connectivity issues (e.g., IP networking, routing, firewalls, VPNs) and system integrations. - Software & Systems Support: Work with engineering teams to debug and resolve software defects encountered in the field. Assist in deploying and validating software updates, ensuring system stability post-deployment. Support command-line operations, scripting, and system configuration within Linux environments. - Documentation And Communication: Maintain detailed records of service activities, including issue diagnostics, resolution processes, asset usage, and customer interactions. Generate comprehensive Field Reports and Work Orders to provide actionable feedback to quality and engineering teams. Communicate service bulletins, informational notices, and product updates effectively to internal and external stakeholders, ensuring clear understanding and implementation. - Customer Relationship Management: Build strong customer relationships by acting as a trusted technical advisor. Provide guidance on best practices for system operation, maintenance, and performance optimization. Proactively identify opportunities to improve customer experience and system reliability. - Travel And Field Operations: Regularly travel to various customer sites to deliver essential on-site support, ensuring responsiveness and timely issue resolution. Extended deployments in operational field environments, including possible active combat zones Ensure readiness and compliance with all safety standards during travel and field service operations. Note there is a slight formatting issue: "Extended deployments in operational field environments, including possible active combat zones Ensure readiness..." Should be two sentences. We'll keep as is. Qualifications: list: - 5 or more years of relevant experience - B.S. in computer science, engineering, robotics, or related field - Proficiency in Linux systems (command line, system logs, basic administration) - Solid understanding of networking fundamentals (TCP/IP, DNS, routing, firewalls, VPNs) - Strong software troubleshooting skills, including log analysis and debugging - Experience diagnosing complex systems involving both hardware and software components - Ability to communicate technical concepts clearly to diverse audiences - Strong documentation and organizational skills - Ability to work independently in dynamic, customer-facing environments - Experience in integrating software on hardware products - Strong programming skills in languages such as C++ or Python - Solid core software engineering skills: software design, unit testing, debugging - Strong understanding of algorithms, data structures, and software design principles - Experience working in teams and a willingness to proactively solve problems - Ability to travel up to 75%, including internationally Preferred Qualifications: - Familiarity with autonomous systems, robotics, or distributed systems. - Experience working closely with engineering teams to resolve field issues. - Experience in software development for robotics and autonomous systems - Experience with state machines, motion, path planning, and/or perception pipelines - Knowledge of navigation, localization, and/or mapping algorithms - Familiarity with real-time operating systems and embedded programming Clearance eligibility: "CLEARANCE ELIGIBILITY - This position may require eligibility to obtain and maintain a U.S. security clearance." Benefits: The benefits paragraph includes many details. We need to preserve all substantive information. The benefits section includes: - The salary range for this role is an estimate and is based on a wide variety of compensation factors. The salary offered to candidates will vary based on a variety of factors including (but not limited to) relevant work experience, education, specialized training, critical expertise, training, and more. (This is more about salary, but we have Pay section.) - Equity in Forterra is included in most of our full-time, high-demand roles and is therefore considered part of Forterra’s overall compensation package. - In addition to base salary and equity, Forterra offers competitive benefits for full-time employees including: - Premium Healthcare Benefits: Three plan options, including an HSA-eligible plan, with Forterra covering 80% of the plan premium for you and your dependents. - Basic Life/AD&D, short and long-term disability insurance plans 100% covered by Forterra, plus the option to purchase additional life insurance for you and your dependents. - Extremely generous company holiday calendar including a winter break in December. - Competitive paid time off (PTO) offering 20 days accrued per year. - A minimum of 7 weeks fully paid parental leave for birth/adoption. - A $9k annual tuition reimbursement or professional development stipend. - Fully stocked beverage refrigerators with all the Celsius your little heart desires. - 401(k) retirement savings plan, including traditional, Roth 401(k), and after-tax deferral with company match up to 4%. - Your recruiter will be able to share more information about our salary and benefits offering during the hiring process. We should keep all that. Pay: US Salary Range $120,000—$150,000. We should not include the sentence about salary range being an estimate etc. That's more generic; but it's substantive? It's about salary determination. Could be included in Pay section as a note. But the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The sentence "The salary range for this role is an estimate and is based on a wide variety of compensation factors..." is not filler; it's explanatory. Could be included. However we already have Pay section with the range. We could add a paragraph after the range explaining that it's an estimate etc. That's fine. We need to avoid duplication: The benefits paragraph also repeats "The salary range for this role is an estimate..." which we already might include in Pay. We'll include it only once under Pay. Now we need to output HTML. Structure:

    About the role

    ... (About Forterra + About The Role?) Actually About the role should include role description. The About Forterra is company overview; maybe we could put that under About the role? But the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid including company description under About the role. Could combine both. But we might want a separate section for About Forterra? Not in list. Probably we should put company overview under About the role as well, or we could omit it? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but we should follow that pattern. The posting has "About Forterra" and "About The Role". We could treat "About the role" as the role description, and maybe we could include a brief company overview in a paragraph before that heading? But we cannot add extra headings not in list? It didn't forbid other headings, but to be safe we can include company overview as a paragraph under About the role heading (mix). Or we could create a heading "About Forterra" but that's not in the examples; but maybe allowed. However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The e.g. suggests those are examples, not