Senior Software Engineer

We need to output HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about JBT Marel purpose, values. That's about the company, maybe "About the role"? Actually "About the role" could be overview of role. But we have "Overview As our Sr. Software Engineer you will join..." That's role overview. Could be placed under "About the role" or "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Benefits: listed. - Overview: description of role responsibilities. - Qualifications: bullet list. - Desired Skills: bullet list. - Pay: salary range. - Schedule: hybrid schedule mentioned: "working on-site under a hybrid schedule at the Redmond, WA location." Also occasional travel. - Responsibilities: could be the list of tasks under "On a Given Day, You May ..." That's responsibilities. - Requirements: maybe the qualifications (degree, experience). Could be separate. We need to avoid filler headings like Pay if not specific; but we have salary range, so include Pay. Schedule: we have hybrid schedule, occasional travel. So include Schedule. Benefits: we have list. We must not include headings with placeholder like "commensurate with experience". Not present. We must not include duplicated lines. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove the diversity statement, EEO, etc. Also remove "Commitment to Diversity", "Equal Opportunity Employment", "Use of Technology in Our Hiring Process". Also remove "Work Environment And Physical Demands" maybe? That's not boilerplate but could be considered generic; but it's substantive? It's about office setting. Might be considered boilerplate but it's not EEO. However it's generic; but we could keep if it's substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The work environment paragraph is not exactly boilerplate but could be considered generic; but it's not duplicated. Might keep? However we have no heading for Work Environment; we could incorporate into Schedule or maybe not needed. Since we only output sections we have headings for, we could omit that paragraph. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details from the work environment? It's not under any heading we output; if we omit it, we lose info. But we could incorporate it into Schedule or maybe a separate section like "Work Environment". However the instruction only lists allowed headings; we could add other headings? It says "use

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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map all content into those sections. Work environment could go under Schedule? Not really. Could go under About the role? Maybe we can include a brief sentence about work environment in About the role or Responsibilities. But we must preserve all substantive information; we can embed it in a paragraph under About the role. Thus we need to craft sections: - About the role: include company purpose/intro? Actually "About the role" maybe includes overview of role and company context. We'll put the introductory paragraph about JBT Marel purpose and values, plus the overview paragraph. - Responsibilities: list of tasks from "On a Given Day, You May ..." as

• . - Requirements: maybe the qualifications bullet list (Bachelor’s/Master’s, 5+ years experience, etc.) Could be separate from Qualifications? Actually we have Qualifications and Desired Skills. The instruction includes Qualifications and Skills as separate headings. So we can put the "Qualifications" bullet list under Requirements? Or under Qualifications? The heading list includes Qualifications and Skills. So we should have a Qualifications section for the bullet list under "Qualifications". And a Skills section for "Desired Skills". Requirements could be maybe the experience and degree? But we already have Qualifications. Hmm. We have both "Qualifications" and "Desired Skills". The instruction includes Qualifications and Skills. So we can map: - Qualifications: the bullet list under "Qualifications" (degree, experience, etc.) - Skills: the bullet list under "Desired Skills". What about Requirements? Could be maybe the "Experience 5+ years..." but that's already in Qualifications. Could combine Requirements with Qualifications? But we need to decide. The instruction says include a section ONLY when the posting has real, specific content for it. So we need to see if there is distinct content for Requirements separate from Qualifications. The posting has a section titled "Qualifications" and then "Desired Skills". There's no separate "Requirements". So we should not create a Requirements heading because there is no specific content labeled as Requirements. However we could treat the Qualifications as Requirements. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It expects possibly Requirements and Qualifications both. But we must not create a heading with filler. If we don't have distinct Requirements content, we should omit Requirements heading. However we might still need to convey the qualification details; we can put them under Qualifications. That's fine. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Check each for content: - About the role: company purpose/intro + overview paragraph. - Responsibilities: list of tasks. - Qualifications: bullet list under "Qualifications". - Skills: bullet list under "Desired Skills". - Benefits: list. - Pay: salary range. - Schedule: hybrid schedule, occasional travel. Now we need to format. We must not include markdown code fences. Just raw HTML. We need to ensure we use

  for each heading. Then content:

  for prose,

  • for lists. We must preserve all substantive information. Let's extract exact text. Company purpose/intro: "At JBT Marel, what we do matters; we recognize that the contributions of our employees drive the success of our business. Our purpose is to transform the future of food, guiding our vision to be the global leader in food and beverage technology by harnessing the full power of JBT Marel to partner with our customers and pioneer sustainable innovation. Our values show who we are at our best. As we Create with Collaboration, Serve with Integrity, Grow with Excellence, and Advance with Innovation." We can keep that as a paragraph. Overview paragraph: "Overview As our Sr. Software Engineer you will join a focused engineering team developing software that drives robotic waterjet cutting systems for the food processing industry. Our applications combine real-time control, computer vision, and data-driven technologies to deliver precise, reliable solutions to customers worldwide. You will work directly with senior technical leadership to build a deep understanding of existing systems, architecture, and customer-driven applications. Through hands-on project work, you will develop toward long-term technical ownership and continuity. You will be part of the JBT Marel Poultry division, working on-site under a hybrid schedule at the Redmond, WA location." Note: The hybrid schedule mention appears here; but we will also have Schedule section. Might duplicate. We could keep overview without schedule mention, but we need to preserve all info. We could keep overview as is, and Schedule section will mention hybrid schedule and occasional travel. That's okay; some duplication but we must preserve all info, not remove duplication unless it's duplicated lines. The instruction says remove duplicated lines. This is not a duplicated line exactly; it's same info appears in two places. Might be considered duplicated content. Safer to avoid duplication: we could remove the hybrid schedule mention from overview and keep it in Schedule. But then we lose that detail from overview? However overview still contains other details. The hybrid schedule is a substantive detail; we need to preserve it somewhere. If we put it only in Schedule, it's preserved. So we can edit overview to exclude that sentence. But we must not invent or summarize away detail; we can just omit that sentence from overview and place it in Schedule. That's not removing detail, just relocating. That's acceptable. Thus overview paragraph without the hybrid schedule sentence. Let's craft overview: "As our Sr. Software Engineer you will join a focused engineering team developing software that drives robotic waterjet cutting systems for the food processing industry. Our applications combine real-time control, computer vision, and data-driven technologies to deliver precise, reliable solutions to customers worldwide. You will work directly with senior technical leadership to build a deep understanding of existing systems, architecture, and customer-driven applications. Through hands-on project work, you will develop toward long-term technical ownership and continuity. You will be part of the JBT Marel Poultry division." Now Responsibilities list: extract each bullet from "On a Given Day, You May ..." list. List items: - Develop and maintain C/C++ applications supporting machine control and customer-facing functionality - Translate field needs, service reports, and requirements into prioritized development tasks and working solutions - Collaborate with applications, sales, and engineering teams to refine and deliver solutions - Develop, test, and validate prototype applications for customer evaluations and pre-sales efforts - Evolve validated prototypes into production-ready applications - Debug and troubleshoot software across development, lab, and production environments - Work within existing complex codebases while making targeted improvements - Manage work using Jira and coordinate across distributed teams - Work directly with senior engineers to understand system architecture and design intent - Operate independently while aligning with team and business priorities - Balance development timelines with customer and sales needs - Occasional travel to customer sites or internal facilities Note: occasional travel also appears in Schedule; we may keep it only in Schedule to avoid duplication. But it's also a responsibility. Could keep in both? Might be considered duplicated. Better to keep it only in Schedule, as it's about schedule/travel. However the responsibility list includes it as a task. If we remove it from responsibilities, we lose that detail as a responsibility. But we can keep it in responsibilities and also mention in Schedule? That would be duplication. The instruction says remove duplicated lines. So we should avoid duplicate exact lines. The line "Occasional travel to customer sites or internal facilities" appears in responsibilities list. If we also mention travel in Schedule, that's duplication of meaning but not exact line. Might still be considered duplicate? Safer to keep it only in responsibilities and not repeat in Schedule; but Schedule should still convey hybrid schedule and occasional travel. We could mention occasional travel in Schedule as well but rephrase to avoid exact duplicate. Eg "Hybrid schedule with occasional travel to customer sites or internal facilities." That's not identical line. So we can keep responsibilities list as given, and Schedule section can mention hybrid schedule and occasional travel (rephrased). That's okay. Now Qualifications bullet list: - Bachelor’s or Master’s degree in Computer Science, Engineering, or related field preferred - Strong foundation in C/C++ programming - Strong problem-solving skills and self-motivation - Experience 5+ years of relevant experience preferred (flexible for the right candidate) - Experience contributing to real-time software or engineering projects - Familiarity with version control and issue tracking systems (GitHub, Jira, or similar) - Experience learning from or working alongside experienced engineers is a plus Note: The last bullet is "Experience learning from or working alongside experienced engineers is a plus". Keep. Now Skills bullet