Field Engineering Specialist - Queens, NY
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", etc. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Intro about Roche culture: "At Roche you can show up as yourself..." etc. That's about company culture, maybe "About the role"? Actually "About the role" could be description of role. But we have "The Opportunity:" and bullet list of duties. Also "This is a field-based role - the territory serves NYC, Long Island and Northern NJ. (Must Reside in Brooklyn/Queens area)". Travel: 50% travel, includes onboarding/training at Indianapolis.
- "Who You Are:" lists qualifications: high school diploma + 2 years technical school or equivalent military training or equivalent work experience; 5 years progressive experience repairing or servicing mechanical/system hardware and software, or networking/wireless networking OR a Bachelor’s degree in Biomedical Engineering, Mechanical Engineering, Electrical Engineering, Chemistry or related field plus 1-2 years progressive experience repairing or servicing complex mechanical/system hardware and software, or networking/wireless networking; Successfully training or certification as defined by RD Services Leadership and policy; Ability to travel, including some overnight travel, is required.
- "Preferred Qualifications:" 8+ years progressive experience or a Bachelor's degree in a relevant field plus 4+ years progressive experience are required; Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry; The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential.
- "Relocation benefits are not available for this job posting."
- Pay: "The expected salary range for this position based on the primary location of New York is $74,600.00- 138,600.00USD . Actual pay will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by law. A discretionary annual bonus may be available based on individual and Company performance."
- Benefits: "This position also qualifies for the benefits detailed at the link provided below." Then later "Benefits" heading appears but no details given besides link. The posting includes a "Benefits" heading but no actual benefit list. According to rule: do NOT create Benefits section unless posting actually states them. It says "qualifies for the benefits detailed at the link provided below." That's not specific benefit details; it's a reference. Should we include Benefits? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states that benefits exist but not details. Might be considered stating them? It says "qualifies for the benefits detailed at the link provided below." That's a statement that benefits exist, but not listing them. The instruction: "Prefer a few substantive sections over many thin ones." Likely we should not include Benefits because no concrete benefits listed. However we could include a short
saying "Qualifies for Roche benefits (see link)". But that might be considered filler? The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." The benefit info is substantive: that they qualify for benefits detailed at link. So we could include a Benefits section with a
stating that. But we must not invent details. So we can include a short paragraph.
- Schedule: Not explicitly stated besides travel 50% and some overnight travel. No schedule like full-time, part-time, shift. So we should not create Schedule section.
- Pay: we have salary range and bonus. So we can include Pay section.
- About the role: we have introductory paragraphs about Roche culture and mission, plus "The Opportunity:" bullet list. Could be considered About the role. We'll include About the role with prose summarizing Roche culture and mission? But we must not repeat job title as heading. The "About the role" could contain description of role and company. We'll include prose from the first paragraphs and the "Opportunity:" bullet list as
.
- Responsibilities: Could be same as duties? The bullet list under "The Opportunity:" are duties. Could be placed under Responsibilities. But we already used bullet list under About the role? We need to decide sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role and Responsibilities into one section? But headings are predefined; we must use those headings only if we have content. We could have About the role (company overview) and Responsibilities (duties). Or we could have About the role (including duties) and skip Responsibilities. But we need to avoid thin sections. Let's think: The posting includes a clear "The Opportunity:" bullet list of duties. That's substantive. So we can make a Responsibilities section with that list. Then About the role could contain the company culture/mission intro. That's also substantive. So we will have both.
- Requirements: The "Who You Are:" section includes mandatory qualifications. That's Requirements.
- Qualifications: Could be Preferred Qualifications? Actually we have "Who You Are:" (minimum qualifications) and "Preferred Qualifications:" (preferred). So we can put Requirements for mandatory, Qualifications for preferred? Or we could treat Requirements as mandatory, Qualifications as preferred. The headings list includes both Requirements and Qualifications. We'll assign accordingly.
- Skills: Could be derived from preferred qualifications like advanced knowledge of electronics, etc. Could be a Skills section. But we might avoid thin sections. However we have specific skill statements: "Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry; The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential." That's skills. Could be a Skills section.
- Benefits: we have statement about qualifies for benefits detailed at link. We'll include Benefits section with a .
- Pay: we have salary range and bonus.
- Schedule: not present, omit.
Now we need to ensure we don't include boilerplate like EEO, equal opportunity, accommodation, etc. Remove those lines.
Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting includes "Roche is an equal opportunity employer..." etc. Remove.
Also remove "Relocation benefits are not available for this job posting." That's substantive? It's a detail about relocation benefits not available. Could be included in Benefits? But it's a negative. Might be worth including in Benefits section as a note. However we already have Benefits section about qualifies for benefits; we could add that relocation benefits are not available. That's substantive. Let's include.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... company culture/mission ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
... (including relocation benefits not available)
Pay
... salary range and bonus ...
We must ensure we don't include filler like "commensurate with experience". Not present.
Now extract precise text.
About the role: The first paragraph: "At Roche you can show up as yourself, embraced for the unique qualities you bring. Our culture encourages personal expression, open dialogue, and genuine connections, where you are valued, accepted and respected for who you are, allowing you to thrive both personally and professionally. This is how we aim to prevent, stop and cure diseases and ensure everyone has access to healthcare today and for generations to come. Join Roche, where every voice matters."
Then second paragraph: "A healthier future. It’s what drives us to innovate. To continuously advance science and ensure everyone has access to the healthcare they need today and for generations to come. Creating a world where we all have more time with the people we love. That’s what makes us Roche."
Third paragraph: "Roche Support Network offers an exciting opportunity for individuals who are passionate about problem solving. As a research-focused healthcare company, Roche is dedicated to discovering, developing, and providing innovative diagnostics and therapeutic products. With a commitment to employee development and a work environment that values respect and empowerment, Roche offers exciting career prospects for those seeking to make a significant impact on patient care."
We could combine these into About the role prose. Might be a bit long but okay.
Responsibilities: The bullet list under "The Opportunity:":
- showcase your expertise in technical repair for Roche assigned product lines
- offer valuable service to laboratory customers in your assigned territory
- provide routine technical support, on-site service and repair of Roche products
- serve as a customer contact for technical and service-related issues and perform preventative maintenance
- diagnose and resolve mechanical, hardware, software, and system failures
- document all activities, contribute to quality improvement, and focus on maximizing customer satisfaction
Also note: "This is a field-based role - the territory serves NYC, Long Island and Northern NJ. (Must Reside in Brooklyn/Queens area)" and "Travel: This position requires 50% travel based on customer needs and demands, and includes comprehensive onboarding and training at our corporate headquarters in Indianapolis, IN." These could be part of Responsibilities or maybe separate. But they are details about role. Could be included in Responsibilities as list items. We'll add them as list items.
Requirements: "Who You Are:" bullet points:
- High school diploma and 2 years of technical school or equivalent military training or equivalent work experience
- 5 years of progressive experience repairing or servicing mechanical/system hardware and software, or networking/wireless networking OR a Bachelor’s degree in Biomedical Engineering, Mechanical Engineering, Electrical Engineering, Chemistry or related field plus 1-2 years of progressive experience repairing or servicing complex mechanical/system hardware and software, or networking/wireless networking
- Successfully training or certification as defined by RD Services Leadership and policy
- Ability to travel, including some overnight travel, is required
We need to keep the OR logic. We'll keep as is.
Qualifications (Preferred): "Preferred Qualifications:" bullet points:
- 8+ years of progressive experience or a Bachelor's degree in a relevant field plus 4+ years of progressive experience are required
- Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry
- The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential
Skills: Could be derived from preferred qualifications: advanced knowledge etc. But we already have those as qualifications. Might be redundant. Perhaps we should not have Skills separate; we could put those under Qualifications. But we have both headings; we need to avoid thin sections. If we put advanced knowledge etc under Qualifications, then Skills may be thin. Better to combine: maybe we treat Qualifications as mandatory? Actually we already have Requirements for mandatory. Qualifications could be preferred. Skills could be something else like "technical repair, customer service, documentation". But we already have those in responsibilities. To avoid thin sections, we could omit Skills section and instead include skill statements within Qualifications or Responsibilities. However the instruction says to use headings only when posting has real, specific content for it. If we don't have distinct skill content beyond what's already captured, we could
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", etc. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro about Roche culture: "At Roche you can show up as yourself..." etc. That's about company culture, maybe "About the role"? Actually "About the role" could be description of role. But we have "The Opportunity:" and bullet list of duties. Also "This is a field-based role - the territory serves NYC, Long Island and Northern NJ. (Must Reside in Brooklyn/Queens area)". Travel: 50% travel, includes onboarding/training at Indianapolis. - "Who You Are:" lists qualifications: high school diploma + 2 years technical school or equivalent military training or equivalent work experience; 5 years progressive experience repairing or servicing mechanical/system hardware and software, or networking/wireless networking OR a Bachelor’s degree in Biomedical Engineering, Mechanical Engineering, Electrical Engineering, Chemistry or related field plus 1-2 years progressive experience repairing or servicing complex mechanical/system hardware and software, or networking/wireless networking; Successfully training or certification as defined by RD Services Leadership and policy; Ability to travel, including some overnight travel, is required. - "Preferred Qualifications:" 8+ years progressive experience or a Bachelor's degree in a relevant field plus 4+ years progressive experience are required; Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry; The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential. - "Relocation benefits are not available for this job posting." - Pay: "The expected salary range for this position based on the primary location of New York is $74,600.00- 138,600.00USD . Actual pay will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by law. A discretionary annual bonus may be available based on individual and Company performance." - Benefits: "This position also qualifies for the benefits detailed at the link provided below." Then later "Benefits" heading appears but no details given besides link. The posting includes a "Benefits" heading but no actual benefit list. According to rule: do NOT create Benefits section unless posting actually states them. It says "qualifies for the benefits detailed at the link provided below." That's not specific benefit details; it's a reference. Should we include Benefits? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states that benefits exist but not details. Might be considered stating them? It says "qualifies for the benefits detailed at the link provided below." That's a statement that benefits exist, but not listing them. The instruction: "Prefer a few substantive sections over many thin ones." Likely we should not include Benefits because no concrete benefits listed. However we could include a short
saying "Qualifies for Roche benefits (see link)". But that might be considered filler? The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." The benefit info is substantive: that they qualify for benefits detailed at link. So we could include a Benefits section with a
stating that. But we must not invent details. So we can include a short paragraph. - Schedule: Not explicitly stated besides travel 50% and some overnight travel. No schedule like full-time, part-time, shift. So we should not create Schedule section. - Pay: we have salary range and bonus. So we can include Pay section. - About the role: we have introductory paragraphs about Roche culture and mission, plus "The Opportunity:" bullet list. Could be considered About the role. We'll include About the role with prose summarizing Roche culture and mission? But we must not repeat job title as heading. The "About the role" could contain description of role and company. We'll include prose from the first paragraphs and the "Opportunity:" bullet list as
- .
- Responsibilities: Could be same as duties? The bullet list under "The Opportunity:" are duties. Could be placed under Responsibilities. But we already used bullet list under About the role? We need to decide sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role and Responsibilities into one section? But headings are predefined; we must use those headings only if we have content. We could have About the role (company overview) and Responsibilities (duties). Or we could have About the role (including duties) and skip Responsibilities. But we need to avoid thin sections. Let's think: The posting includes a clear "The Opportunity:" bullet list of duties. That's substantive. So we can make a Responsibilities section with that list. Then About the role could contain the company culture/mission intro. That's also substantive. So we will have both.
- Requirements: The "Who You Are:" section includes mandatory qualifications. That's Requirements.
- Qualifications: Could be Preferred Qualifications? Actually we have "Who You Are:" (minimum qualifications) and "Preferred Qualifications:" (preferred). So we can put Requirements for mandatory, Qualifications for preferred? Or we could treat Requirements as mandatory, Qualifications as preferred. The headings list includes both Requirements and Qualifications. We'll assign accordingly.
- Skills: Could be derived from preferred qualifications like advanced knowledge of electronics, etc. Could be a Skills section. But we might avoid thin sections. However we have specific skill statements: "Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry; The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential." That's skills. Could be a Skills section.
- Benefits: we have statement about qualifies for benefits detailed at link. We'll include Benefits section with a
- ... ...
- ... ...
- ... ...
- ... ...
. - Pay: we have salary range and bonus. - Schedule: not present, omit. Now we need to ensure we don't include boilerplate like EEO, equal opportunity, accommodation, etc. Remove those lines. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting includes "Roche is an equal opportunity employer..." etc. Remove. Also remove "Relocation benefits are not available for this job posting." That's substantive? It's a detail about relocation benefits not available. Could be included in Benefits? But it's a negative. Might be worth including in Benefits section as a note. However we already have Benefits section about qualifies for benefits; we could add that relocation benefits are not available. That's substantive. Let's include. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
... company culture/mission ...
Responsibilities
Requirements
Qualifications
Skills
Benefits
... (including relocation benefits not available)
Pay
... salary range and bonus ...
We must ensure we don't include filler like "commensurate with experience". Not present. Now extract precise text. About the role: The first paragraph: "At Roche you can show up as yourself, embraced for the unique qualities you bring. Our culture encourages personal expression, open dialogue, and genuine connections, where you are valued, accepted and respected for who you are, allowing you to thrive both personally and professionally. This is how we aim to prevent, stop and cure diseases and ensure everyone has access to healthcare today and for generations to come. Join Roche, where every voice matters." Then second paragraph: "A healthier future. It’s what drives us to innovate. To continuously advance science and ensure everyone has access to the healthcare they need today and for generations to come. Creating a world where we all have more time with the people we love. That’s what makes us Roche." Third paragraph: "Roche Support Network offers an exciting opportunity for individuals who are passionate about problem solving. As a research-focused healthcare company, Roche is dedicated to discovering, developing, and providing innovative diagnostics and therapeutic products. With a commitment to employee development and a work environment that values respect and empowerment, Roche offers exciting career prospects for those seeking to make a significant impact on patient care." We could combine these into About the role prose. Might be a bit long but okay. Responsibilities: The bullet list under "The Opportunity:": - showcase your expertise in technical repair for Roche assigned product lines - offer valuable service to laboratory customers in your assigned territory - provide routine technical support, on-site service and repair of Roche products - serve as a customer contact for technical and service-related issues and perform preventative maintenance - diagnose and resolve mechanical, hardware, software, and system failures - document all activities, contribute to quality improvement, and focus on maximizing customer satisfaction Also note: "This is a field-based role - the territory serves NYC, Long Island and Northern NJ. (Must Reside in Brooklyn/Queens area)" and "Travel: This position requires 50% travel based on customer needs and demands, and includes comprehensive onboarding and training at our corporate headquarters in Indianapolis, IN." These could be part of Responsibilities or maybe separate. But they are details about role. Could be included in Responsibilities as list items. We'll add them as list items. Requirements: "Who You Are:" bullet points: - High school diploma and 2 years of technical school or equivalent military training or equivalent work experience - 5 years of progressive experience repairing or servicing mechanical/system hardware and software, or networking/wireless networking OR a Bachelor’s degree in Biomedical Engineering, Mechanical Engineering, Electrical Engineering, Chemistry or related field plus 1-2 years of progressive experience repairing or servicing complex mechanical/system hardware and software, or networking/wireless networking - Successfully training or certification as defined by RD Services Leadership and policy - Ability to travel, including some overnight travel, is required We need to keep the OR logic. We'll keep as is. Qualifications (Preferred): "Preferred Qualifications:" bullet points: - 8+ years of progressive experience or a Bachelor's degree in a relevant field plus 4+ years of progressive experience are required - Advanced knowledge of electronics, electro-mechanical systems, information technology, and basic chemistry - The ability to serve as an internal technical resource, provide support after hours and on weekends/holidays, and maintain strong customer relationships is essential Skills: Could be derived from preferred qualifications: advanced knowledge etc. But we already have those as qualifications. Might be redundant. Perhaps we should not have Skills separate; we could put those under Qualifications. But we have both headings; we need to avoid thin sections. If we put advanced knowledge etc under Qualifications, then Skills may be thin. Better to combine: maybe we treat Qualifications as mandatory? Actually we already have Requirements for mandatory. Qualifications could be preferred. Skills could be something else like "technical repair, customer service, documentation". But we already have those in responsibilities. To avoid thin sections, we could omit Skills section and instead include skill statements within Qualifications or Responsibilities. However the instruction says to use headings only when posting has real, specific content for it. If we don't have distinct skill content beyond what's already captured, we could