Sr. Technical Support Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate.
We need to parse the posting.
First paragraph: Rockwell Automation is a global technology leader... This is about the company, maybe "About the role"? Actually "About the role" would be a summary of the position. The posting includes "Position Summary:" after that. So we can put that under "About the role". The Position Summary: Rockwell Automation is building machine vision... etc. That's substantive.
Then "Your Responsibilities" list bullet points. Use - .
Then "The Essentials - You Will Have" includes: Bachelor's Degree or Equivalent Years of Relevant Work Experience; Legal authorization to work in the US is required; We will not sponsor individuals for employment visas... That's requirements/qualifications. Could be under "Requirements" or "Qualifications". The posting also has "The Preferred - You Might Also Have" list. That's preferred qualifications. Could be under "Qualifications" or "Skills". We need to decide.
We have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include only those with real content.
We have Responsibilities: yes.
We have Requirements: The Essentials list includes Bachelor's Degree or Equivalent Years of Relevant Work Experience; Legal authorization to work in the US is required; No sponsorship. That's requirements.
We have Qualifications: The Preferred list includes many items: 2 years experience, Bachelor's degree in Engineering, CS, etc. That's qualifications.
We have Skills: maybe we can extract specific skills from preferred list: Linux command line, industrial networking, EtherNet/IP, OPC UA, PLCs, machine vision systems, cameras, optics troubleshooting, building knowledge bases, etc. Could be under Skills.
We have Benefits: The posting lists "What We Offer": Health Insurance including Medical, Dental and Vision; 401k; Paid Time off; Parental and Caregiver Leave; Flexible Work Schedule; link to benefits. That's benefits.
We have Pay: "For this role, the Base Salary Compensation is 92,000.00 -138,000.00 USD Annual with an annual target bonus of 5% of base salary." That's pay.
We have Schedule: "This role will have a remote schedule" and also "Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life." So schedule info: remote schedule, flexible work schedule.
We also have "Position Summary" which we can put under About the role.
We need to avoid repeating job title as heading. Not include Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original sentences.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, accommodation contact, etc. Remove those.
Also remove "At Rockwell Automation we are dedicated to building a diverse, inclusive and authentic workplace..." that's EEO boilerplate. Remove.
Also remove "This position is part of a job family. Experience will be the determining factor for position level and compensation" maybe that's not boilerplate but it's about compensation; we already have pay section. Might keep? It's somewhat generic but still substantive? It says experience determines level and compensation. Could be considered part of Pay? Might keep as part of Pay? But we already have pay details. Might be considered redundant. Safer to keep? The instruction: remove duplicated lines. Not sure. I'd keep it as part of Pay? But it's not duplicated. It's about compensation determination. Could be included in Pay section as a note. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we can incorporate that into Pay section.
Also "To learn more about our benefits package, please visit at www.raquickfind.com." That's part of Benefits.
Also "Our benefits for the US can be found here." That's also benefits.
We need to not include application instructions like "please contact our services team" etc. That's accommodation request; that's EEO/accommodation boilerplate; remove.
Now structure:
About the role
Position Summary: Rockwell Automation is building machine vision and visual inspection into the Automation Control Software portfolio, alongside Studio 5000 Logix Designer and FactoryTalk Optix. You will own front-line technical support for it - the first response when a customer's inspection station stops passing parts, and the path from that call to a resolved defect. You will also own the support function itself: the portal, the ticket taxonomy, the escalation path into engineering, and the knowledge base that keeps the same question from being answered twice. You will work in an organization that applies agents to its own operating loop - triage, log analysis, summarization, and knowledge retrieval through MCP-connected systems - using GitHub Copilot Enterprise and Claude. You will help build that loop for support specifically, and measure whether it actually cut time to resolution. This role will have a remote schedule and will report to the Manager, Customer Support Engineering.
That's the position summary plus remote schedule line.
But we also have schedule section separate. Might duplicate remote schedule. Better to keep remote schedule in Schedule section. However the summary includes that line; we could keep it there but then schedule section would be redundant. The instruction: do not repeat content? Not explicitly, but we should preserve all substantive information; duplication may be okay but better to avoid duplication. We could keep remote schedule in Schedule section and not repeat in About the role. But the summary includes that line; we could remove it from summary to avoid duplication. However we must preserve all substantive information; removing that line would lose info about remote schedule. But we will have it in Schedule section, so it's preserved elsewhere. So we can omit from About the role.
Thus About the role paragraph: Position Summary: Rockwell Automation is building machine vision... (without the remote schedule line). Let's copy the summary up to "measure whether it actually cut time to resolution." Then stop before "This role will have a remote schedule..."
Now Responsibilities: list bullet points.
We need to capture each bullet:
- Own front-line and second-line technical support for inspection deployments, from intake through resolution.
- Diagnose issues across application, model behavior, edge device, network, and controller integration.
- Own and improve the support portal, ticket taxonomy, SLAs, and the escalation path into engineering.
- Build and maintain the knowledge base and troubleshooting documentation used by customers and the field.
- Turn recurring support patterns into product requirements, diagnostics, and test coverage.
- Apply agents to triage, log analysis, and knowledge retrieval, and measure the effect on time to resolution.
Make - each.
Now Requirements (Essentials): list:
- Bachelor's Degree or Equivalent Years of Relevant Work Experience
- Legal authorization to work in the US is required.
- We will not sponsor individuals for employment visas, now or in the future, for this job opening.
Make list.
Now Qualifications (Preferred): list:
- Typically requires a minimum of 2 years of related experience in a technical support or field engineering environment.
- Bachelor's degree in Engineering, Computer Science, or a related technical discipline.
- Experience providing technical support for a software or hardware-software product
- Experience diagnosing issues that span software, network, and physical hardware
- Experience owning a support function - portal, ticketing system, SLAs, and escalation process.
- Comfort on a Linux command line for log collection and diagnostics.
- Familiarity with industrial networking and controllers - EtherNet/IP, OPC UA, PLCs.
- Experience with machine vision systems, cameras, or optics troubleshooting.
- Experience building knowledge bases or self-service documentation that measurably deflects tickets.
Make list.
Now Skills: maybe we can extract specific skills from the preferred list that are skill-like: Linux command line, industrial networking, EtherNet/IP, OPC UA, PLCs, machine vision systems, cameras, optics troubleshooting, building knowledge bases, self-service documentation. Could also include: troubleshooting across application, model behavior, edge device, network, controller integration (but that's more responsibility). Might be redundant. But we can create a Skills section with those items.
But we need to avoid thin sections. If we create Skills with many items, it's okay.
Alternatively we could merge Skills into Qualifications. But we have both sections available; we could decide to not create Skills if it's thin. However we have enough specific technical skills to make a substantive section.
Let's create Skills section with list:
- Linux command line for log collection and diagnostics
- Industrial networking and controllers (EtherNet/IP, OPC UA, PLCs)
- Machine vision systems, cameras, optics troubleshooting
- Building knowledge bases or self-service documentation that deflects tickets
We need to preserve all substantive information; we are not omitting any info, just rephrasing. That's okay.
Now Benefits: list:
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
- To learn more about our benefits package, please visit at www.raquickfind.com.
- Our benefits for the US can be found here.
We could combine the last two as links but keep as prose? They are sentences; we can put them in
or as list items. Since they are not exactly benefits but references, we could put them in a
after the list. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits list items are benefits; the links are not benefits per se but still part of benefits section. Could be
.
We'll do:
Benefits
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
To learn more about our benefits package, please visit at www.raquickfind.com. Our benefits for the US can be found here.
But we should not add maybe not needed; but it's okay to keep as plain text. The instruction didn't forbid anchors. But we can keep as plain text.
Now Pay: we have base salary range and target bonus.
We also have "Actual pay will be based on factors such as skills, knowledge, education, and experience." That's also pay info.
We also have "Experience will be the determining factor for position level and compensation" maybe include.
We'll create Pay section with list or prose.
We'll do:
Pay
Base Salary Compensation: $92,000.00 - $138,000.00 USD Annual
Annual target bonus: 5% of
for each section heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original sentences.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, accommodation contact, etc. Remove those.
Also remove "At Rockwell Automation we are dedicated to building a diverse, inclusive and authentic workplace..." that's EEO boilerplate. Remove.
Also remove "This position is part of a job family. Experience will be the determining factor for position level and compensation" maybe that's not boilerplate but it's about compensation; we already have pay section. Might keep? It's somewhat generic but still substantive? It says experience determines level and compensation. Could be considered part of Pay? Might keep as part of Pay? But we already have pay details. Might be considered redundant. Safer to keep? The instruction: remove duplicated lines. Not sure. I'd keep it as part of Pay? But it's not duplicated. It's about compensation determination. Could be included in Pay section as a note. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we can incorporate that into Pay section.
Also "To learn more about our benefits package, please visit at www.raquickfind.com." That's part of Benefits.
Also "Our benefits for the US can be found here." That's also benefits.
We need to not include application instructions like "please contact our services team" etc. That's accommodation request; that's EEO/accommodation boilerplate; remove.
Now structure:
About the role
Position Summary: Rockwell Automation is building machine vision and visual inspection into the Automation Control Software portfolio, alongside Studio 5000 Logix Designer and FactoryTalk Optix. You will own front-line technical support for it - the first response when a customer's inspection station stops passing parts, and the path from that call to a resolved defect. You will also own the support function itself: the portal, the ticket taxonomy, the escalation path into engineering, and the knowledge base that keeps the same question from being answered twice. You will work in an organization that applies agents to its own operating loop - triage, log analysis, summarization, and knowledge retrieval through MCP-connected systems - using GitHub Copilot Enterprise and Claude. You will help build that loop for support specifically, and measure whether it actually cut time to resolution. This role will have a remote schedule and will report to the Manager, Customer Support Engineering.
That's the position summary plus remote schedule line.
But we also have schedule section separate. Might duplicate remote schedule. Better to keep remote schedule in Schedule section. However the summary includes that line; we could keep it there but then schedule section would be redundant. The instruction: do not repeat content? Not explicitly, but we should preserve all substantive information; duplication may be okay but better to avoid duplication. We could keep remote schedule in Schedule section and not repeat in About the role. But the summary includes that line; we could remove it from summary to avoid duplication. However we must preserve all substantive information; removing that line would lose info about remote schedule. But we will have it in Schedule section, so it's preserved elsewhere. So we can omit from About the role.
Thus About the role paragraph: Position Summary: Rockwell Automation is building machine vision... (without the remote schedule line). Let's copy the summary up to "measure whether it actually cut time to resolution." Then stop before "This role will have a remote schedule..."
Now Responsibilities: list bullet points.
We need to capture each bullet:
- Own front-line and second-line technical support for inspection deployments, from intake through resolution.
- Diagnose issues across application, model behavior, edge device, network, and controller integration.
- Own and improve the support portal, ticket taxonomy, SLAs, and the escalation path into engineering.
- Build and maintain the knowledge base and troubleshooting documentation used by customers and the field.
- Turn recurring support patterns into product requirements, diagnostics, and test coverage.
- Apply agents to triage, log analysis, and knowledge retrieval, and measure the effect on time to resolution.
Make - each.
Now Requirements (Essentials): list:
- Bachelor's Degree or Equivalent Years of Relevant Work Experience
- Legal authorization to work in the US is required.
- We will not sponsor individuals for employment visas, now or in the future, for this job opening.
Make list.
Now Qualifications (Preferred): list:
- Typically requires a minimum of 2 years of related experience in a technical support or field engineering environment.
- Bachelor's degree in Engineering, Computer Science, or a related technical discipline.
- Experience providing technical support for a software or hardware-software product
- Experience diagnosing issues that span software, network, and physical hardware
- Experience owning a support function - portal, ticketing system, SLAs, and escalation process.
- Comfort on a Linux command line for log collection and diagnostics.
- Familiarity with industrial networking and controllers - EtherNet/IP, OPC UA, PLCs.
- Experience with machine vision systems, cameras, or optics troubleshooting.
- Experience building knowledge bases or self-service documentation that measurably deflects tickets.
Make list.
Now Skills: maybe we can extract specific skills from the preferred list that are skill-like: Linux command line, industrial networking, EtherNet/IP, OPC UA, PLCs, machine vision systems, cameras, optics troubleshooting, building knowledge bases, self-service documentation. Could also include: troubleshooting across application, model behavior, edge device, network, controller integration (but that's more responsibility). Might be redundant. But we can create a Skills section with those items.
But we need to avoid thin sections. If we create Skills with many items, it's okay.
Alternatively we could merge Skills into Qualifications. But we have both sections available; we could decide to not create Skills if it's thin. However we have enough specific technical skills to make a substantive section.
Let's create Skills section with list:
- Linux command line for log collection and diagnostics
- Industrial networking and controllers (EtherNet/IP, OPC UA, PLCs)
- Machine vision systems, cameras, optics troubleshooting
- Building knowledge bases or self-service documentation that deflects tickets
We need to preserve all substantive information; we are not omitting any info, just rephrasing. That's okay.
Now Benefits: list:
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
- To learn more about our benefits package, please visit at www.raquickfind.com.
- Our benefits for the US can be found here.
We could combine the last two as links but keep as prose? They are sentences; we can put them in
or as list items. Since they are not exactly benefits but references, we could put them in a
after the list. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits list items are benefits; the links are not benefits per se but still part of benefits section. Could be
.
We'll do:
Benefits
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
To learn more about our benefits package, please visit at www.raquickfind.com. Our benefits for the US can be found here.
But we should not add maybe not needed; but it's okay to keep as plain text. The instruction didn't forbid anchors. But we can keep as plain text.
Now Pay: we have base salary range and target bonus.
We also have "Actual pay will be based on factors such as skills, knowledge, education, and experience." That's also pay info.
We also have "Experience will be the determining factor for position level and compensation" maybe include.
We'll create Pay section with list or prose.
We'll do:
Pay
Base Salary Compensation: $92,000.00 - $138,000.00 USD Annual
Annual target bonus: 5% of
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original sentences. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, accommodation contact, etc. Remove those. Also remove "At Rockwell Automation we are dedicated to building a diverse, inclusive and authentic workplace..." that's EEO boilerplate. Remove. Also remove "This position is part of a job family. Experience will be the determining factor for position level and compensation" maybe that's not boilerplate but it's about compensation; we already have pay section. Might keep? It's somewhat generic but still substantive? It says experience determines level and compensation. Could be considered part of Pay? Might keep as part of Pay? But we already have pay details. Might be considered redundant. Safer to keep? The instruction: remove duplicated lines. Not sure. I'd keep it as part of Pay? But it's not duplicated. It's about compensation determination. Could be included in Pay section as a note. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we can incorporate that into Pay section. Also "To learn more about our benefits package, please visit at www.raquickfind.com." That's part of Benefits. Also "Our benefits for the US can be found here." That's also benefits. We need to not include application instructions like "please contact our services team" etc. That's accommodation request; that's EEO/accommodation boilerplate; remove. Now structure:
About the role
Position Summary: Rockwell Automation is building machine vision and visual inspection into the Automation Control Software portfolio, alongside Studio 5000 Logix Designer and FactoryTalk Optix. You will own front-line technical support for it - the first response when a customer's inspection station stops passing parts, and the path from that call to a resolved defect. You will also own the support function itself: the portal, the ticket taxonomy, the escalation path into engineering, and the knowledge base that keeps the same question from being answered twice. You will work in an organization that applies agents to its own operating loop - triage, log analysis, summarization, and knowledge retrieval through MCP-connected systems - using GitHub Copilot Enterprise and Claude. You will help build that loop for support specifically, and measure whether it actually cut time to resolution. This role will have a remote schedule and will report to the Manager, Customer Support Engineering.
That's the position summary plus remote schedule line. But we also have schedule section separate. Might duplicate remote schedule. Better to keep remote schedule in Schedule section. However the summary includes that line; we could keep it there but then schedule section would be redundant. The instruction: do not repeat content? Not explicitly, but we should preserve all substantive information; duplication may be okay but better to avoid duplication. We could keep remote schedule in Schedule section and not repeat in About the role. But the summary includes that line; we could remove it from summary to avoid duplication. However we must preserve all substantive information; removing that line would lose info about remote schedule. But we will have it in Schedule section, so it's preserved elsewhere. So we can omit from About the role. Thus About the role paragraph: Position Summary: Rockwell Automation is building machine vision... (without the remote schedule line). Let's copy the summary up to "measure whether it actually cut time to resolution." Then stop before "This role will have a remote schedule..." Now Responsibilities: list bullet points. We need to capture each bullet: - Own front-line and second-line technical support for inspection deployments, from intake through resolution. - Diagnose issues across application, model behavior, edge device, network, and controller integration. - Own and improve the support portal, ticket taxonomy, SLAs, and the escalation path into engineering. - Build and maintain the knowledge base and troubleshooting documentation used by customers and the field. - Turn recurring support patterns into product requirements, diagnostics, and test coverage. - Apply agents to triage, log analysis, and knowledge retrieval, and measure the effect on time to resolution. Make- each.
Now Requirements (Essentials): list:
- Bachelor's Degree or Equivalent Years of Relevant Work Experience
- Legal authorization to work in the US is required.
- We will not sponsor individuals for employment visas, now or in the future, for this job opening.
Make list.
Now Qualifications (Preferred): list:
- Typically requires a minimum of 2 years of related experience in a technical support or field engineering environment.
- Bachelor's degree in Engineering, Computer Science, or a related technical discipline.
- Experience providing technical support for a software or hardware-software product
- Experience diagnosing issues that span software, network, and physical hardware
- Experience owning a support function - portal, ticketing system, SLAs, and escalation process.
- Comfort on a Linux command line for log collection and diagnostics.
- Familiarity with industrial networking and controllers - EtherNet/IP, OPC UA, PLCs.
- Experience with machine vision systems, cameras, or optics troubleshooting.
- Experience building knowledge bases or self-service documentation that measurably deflects tickets.
Make list.
Now Skills: maybe we can extract specific skills from the preferred list that are skill-like: Linux command line, industrial networking, EtherNet/IP, OPC UA, PLCs, machine vision systems, cameras, optics troubleshooting, building knowledge bases, self-service documentation. Could also include: troubleshooting across application, model behavior, edge device, network, controller integration (but that's more responsibility). Might be redundant. But we can create a Skills section with those items.
But we need to avoid thin sections. If we create Skills with many items, it's okay.
Alternatively we could merge Skills into Qualifications. But we have both sections available; we could decide to not create Skills if it's thin. However we have enough specific technical skills to make a substantive section.
Let's create Skills section with list:
- Linux command line for log collection and diagnostics
- Industrial networking and controllers (EtherNet/IP, OPC UA, PLCs)
- Machine vision systems, cameras, optics troubleshooting
- Building knowledge bases or self-service documentation that deflects tickets
We need to preserve all substantive information; we are not omitting any info, just rephrasing. That's okay.
Now Benefits: list:
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
- To learn more about our benefits package, please visit at www.raquickfind.com.
- Our benefits for the US can be found here.
We could combine the last two as links but keep as prose? They are sentences; we can put them in
or as list items. Since they are not exactly benefits but references, we could put them in a
after the list. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits list items are benefits; the links are not benefits per se but still part of benefits section. Could be
. We'll do:
Benefits
- Health Insurance including Medical, Dental and Vision
- 401k
- Paid Time off
- Parental and Caregiver Leave
- Flexible Work Schedule where you will work with your manager to enjoy a work schedule that can be flexible with your personal life.
To learn more about our benefits package, please visit at www.raquickfind.com. Our benefits for the US can be found here.
But we should not add maybe not needed; but it's okay to keep as plain text. The instruction didn't forbid anchors. But we can keep as plain text. Now Pay: we have base salary range and target bonus. We also have "Actual pay will be based on factors such as skills, knowledge, education, and experience." That's also pay info. We also have "Experience will be the determining factor for position level and compensation" maybe include. We'll create Pay section with list or prose. We'll do:Pay
Base Salary Compensation: $92,000.00 - $138,000.00 USD Annual
Annual target bonus: 5% of
- for any list of duties/requirements/benefits, and