Automation Control Specialist with Rockwell Automation Experience
aeSolutions · Greenville, SC · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "To Learn More About The Company And Apply, Visit" etc. Also remove "Equal Opportunity Employer / Drug Free Work Zone" etc.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph after title: "Are you an experienced controls professional who enjoys solving complex automation challenges, supporting industrial clients, and seeing projects through from design to startup? aeSolutions is seeking an Automation & Controls Specialist II with strong experience in Rockwell Automation platforms to join our team. In this role, you will develop and configure control system solutions for industrial facilities across a variety of industries, including chemical manufacturing, energy, food and beverage, life sciences, and other process industries. This position is ideal for someone who has moved beyond entry-level controls work and is ready to take ownership of project deliverables, mentor junior team members, and serve as a trusted technical resource for clients."
That's about the role.
- Responsibilities: The "What You'll Do As an Automation Controls Specialist II, you will:" then bullet list items.
List items:
- Design and configure industrial control systems and associated hardware
- Develop PLC and HMI software applications for client projects
- Create and execute verification and test plans
- Support equipment installation, startup, commissioning, and troubleshooting activities
- Participate in factory acceptance testing (FAT) and site acceptance testing (SAT)
- Perform technical quality reviews of control system deliverables
- Interface directly with clients on technical matters
- Lead automation activities on assigned projects
- Provide technical guidance and mentorship to junior engineers and specialists
- Support a strong culture of safety, quality, and continuous improvement
- Qualifications: There's a "Qualifications Required" section with bullet list (though not bullet but lines). Items:
- Bachelor's degree in Electrical Engineering, Computer Engineering, Chemical Engineering, or a related technical discipline
- 3+ years of industrial automation and control systems experience
- Demonstrated experience developing PLC and HMI applications
- Strong troubleshooting and commissioning experience in operating industrial facilities
- Ability to work independently while collaborating effectively with multidisciplinary teams
- Excellent written and verbal communication skills
- Willingness to travel up to approximately 35%
- Preferred: "Preferred Experience with Rockwell Automation platforms, including:" then list:
- Experience with industrial networking and communications protocols
- Experience supporting batch or continuous process facilities
- Exposure to safety instrumented systems (SIS)
- Previous client-facing consulting experience
- Ability to lead technical teams and coordinate automation project execution
- Travel & Working Conditions: "Travel & Working Conditions" paragraph: Up to 35% travel (valid driver’s license required)Occasional work in manufacturing, industrial, and construction environmentsSite visits may involve exposure to varying environmental conditionsMost client travel is concentrated within the Southeastern United States, with occasional travel outside the region
- Benefits: "Why Join aeSolutions?" then bullet list of benefits: Actually there is a paragraph about working alongside industry experts etc. Then "This full-time position includes competitive compensation and benefits, including:" then list:
- Medical, Prescription Drug, Dental, & Vision insurance
- HSA, FSA, and Dependent Care FSA options
- Mental health & counseling benefits through our confidential Employee Assistance Program (EAP) for employees and their family members
- Company-provided Employee Life and Disability Coverage with buy-up options
- 401(k) retirement plan with Roth or Traditional options and company contribution
- 1-on-1 retirement planning and financial advice for all stages of life
- Flexible paid time off accrual program
- Flex-time schedules, Half-Day Fridays, & Office, Hybrid, and Remote work options
- Incentive bonus programs, including for performance, professional development, employee referrals, repeat business, and more
- Resources and support for career and skills development, including a Learning Management System with access to thousands of high-quality learning courses, and a peer-to-peer Coaching Program
- About AeSolutions: paragraph describing company.
- Pay: Not explicitly mentioned. There's no salary figure. So we should NOT create Pay section.
- Schedule: Not explicitly mentioned besides travel and flexible schedules etc. There's mention of "Flex-time schedules, Half-Day Fridays, & Office, Hybrid, and Remote work options" which is schedule-related but it's under benefits. Could we create a Schedule section? The rule: only create Schedule section if posting actually states them. It does mention flexible schedules etc. That's schedule info. However it's also under benefits. Might be okay to include Schedule section with that info. But we need to avoid duplication. The rule: Prefer a few substantive sections over many thin ones. Could combine schedule info into Benefits or maybe a separate Schedule section if we think it's substantive. The posting includes "Flex-time schedules, Half-Day Fridays, & Office, Hybrid, and Remote work options". That's schedule. Could create Schedule section with that bullet. But also there is travel % etc. Travel is not schedule but working conditions. Could be under Schedule? Probably better to keep Travel & Working Conditions as its own section? The allowed headings list does not include Travel & Working Conditions. So we need to fold that into appropriate existing headings: maybe under Responsibilities? No. Could be under Qualifications? Not really. Could be under Benefits? Travel is not a benefit. Could be under "About the role"? Not ideal. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. We must map content to those headings. If content doesn't fit, we may need to omit or incorporate into nearest. Travel & Working Conditions could go under Schedule? Schedule is about work schedule, not travel. But maybe we can treat travel as part of Schedule? Not ideal but maybe acceptable. However we could also omit travel details if they are not covered by allowed headings. But we must preserve ALL substantive information. So we need to include travel info somewhere. The allowed headings do not have Travel, but we could put it under Schedule (maybe as "Travel & Schedule") but heading must be exactly one of the allowed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. We must map content to those headings. If content doesn't fit, we may need to omit or incorporate into nearest. Travel & Working Conditions could go under Schedule? Schedule is about work schedule, not travel. But maybe we can treat travel as part of Schedule? Not ideal but maybe acceptable. However we could also omit travel details if they are not covered by allowed headings. But we must preserve ALL substantive information. So we need to include travel info somewhere. The allowed headings do not have Travel, but we could put it under Schedule (maybe as "Travel & Schedule") but heading must be exactly one of the allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive? 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 must fit content into those.
We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Qualifications (maybe split into Requirements and Qualifications?), Skills, Benefits, Schedule (flex-time etc). We also have Preferred experience which could be Skills. Requirements could be the required qualifications (Bachelor's degree, 3+ years, etc). Qualifications could be the preferred? Or we could treat Requirements as required, Qualifications as preferred. Skills could be specific technical skills (Rockwell, PLC/HMI, networking, SIS, etc). Let's map:
- About the role: as above.
- Responsibilities: bullet list.
- Requirements: required qualifications (Bachelor's degree, 3+ years experience, demonstrated PLC/HMI, troubleshooting/commissioning, ability to work independently, excellent communication, willingness to travel up to 35%). Travel could be included here.
- Qualifications: preferred experience (Rockwell platforms, industrial networking, batch/continuous, SIS, client-facing consulting, lead technical teams). Could also include "Ability to lead technical teams and coordinate automation project execution". That's a skill.
- Skills: maybe we could list specific technical skills: Rockwell Automation platforms, PLC/HMI development, industrial networking, safety instrumented systems, etc. But we already have Qualifications for preferred. Could combine.
But we need to avoid thin sections. Perhaps we can have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. That's six sections. Skills maybe not needed if we incorporate into Qualifications.
Let's see if we have enough content for Skills: The posting mentions "Strong experience in Rockwell Automation platforms", "Experience with industrial networking and communications protocols", "Experience supporting batch or continuous process facilities", "Exposure to safety instrumented systems (SIS)". Those could be skills. We could make a Skills section with those bullet points.
But we also have "Ability to work independently while collaborating effectively with multidisciplinary teams", "Excellent written and verbal communication skills", "Willingness to travel". Those are more like requirements.
Thus we could have:
- About the role
- Responsibilities
- Requirements (required qualifications)
- Qualifications (preferred experience)
- Skills (technical skills: Rockwell, PLC/HMI, networking, SIS, etc)
- Benefits
- Schedule (flex-time, half-day Fridays, remote/hybrid/office, travel? maybe travel included in Requirements)
But we must not create Pay section.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no markdown.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must fit content into those.
We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Qualifications (maybe split into Requirements and Qualifications?), Skills, Benefits, Schedule (flex-time etc). We also have Preferred experience which could be Skills. Requirements could be the required qualifications (Bachelor's degree, 3+ years, etc). Qualifications could be the preferred? Or we could treat Requirements as required, Qualifications as preferred. Skills could be specific technical skills (Rockwell, PLC/HMI, networking, SIS, etc). Let's map:
- About the role: as above.
- Responsibilities: bullet list.
- Requirements: required qualifications (Bachelor's degree, 3+ years experience, demonstrated PLC/HMI, troubleshooting/commissioning, ability to work independently, excellent communication, willingness to travel up to 35%). Travel could be included here.
- Qualifications: preferred experience (Rockwell platforms, industrial networking, batch/continuous, SIS, client-facing consulting, lead technical teams). Could also include "Ability to lead technical teams and coordinate automation project execution". That's a skill.
- Skills: maybe we could list specific technical skills: Rockwell Automation platforms, PLC/HMI development, industrial networking, safety instrumented systems, etc. But we already have Qualifications for preferred. Could combine.
But we need to avoid thin sections. Perhaps we can have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. That's six sections. Skills maybe not needed if we incorporate into Qualifications.
Let's see if we have enough content for Skills: The posting mentions "Strong experience in Rockwell Automation platforms", "Experience with industrial networking and communications protocols", "Experience supporting batch or continuous process facilities", "Exposure to safety instrumented systems (SIS)". Those could be skills. We could make a Skills section with those bullet points.
But we also have "Ability to work independently while collaborating effectively with multidisciplinary teams", "Excellent written and verbal communication skills", "Willingness to travel". Those are more like requirements.
Thus we could have:
- About the role
- Responsibilities
- Requirements (required qualifications)
- Qualifications (preferred experience)
- Skills (technical skills: Rockwell, PLC/HMI, networking, SIS, etc)
- Benefits
- Schedule (flex-time, half-day Fridays, remote/hybrid/office, travel? maybe travel included in Requirements)
But we must not create Pay section.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no markdown.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
- ... ...
. Responsibilities list: as above. Requirements list: required qualifications: - Bachelor's degree in Electrical Engineering, Computer Engineering, Chemical Engineering, or a related technical discipline - 3+ years of industrial automation and control systems experience - Demonstrated experience developing PLC and HMI applications - Strong troubleshooting and commissioning experience in operating industrial facilities - Ability to work independently while collaborating effectively with multidisciplinary teams - Excellent written and verbal communication skills - Willingness to travel up to approximately 35% (valid driver’s license required) (maybe include driver's license) We could also include "valid driver’s license required" as part of travel. Qualifications list: preferred experience: - Experience with Rockwell Automation platforms - Experience with industrial networking and communications protocols - Experience supporting batch or continuous process facilities - Exposure to safety instrumented systems (SIS) - Previous client-facing consulting experience - Ability to lead technical teams and coordinate automation project execution Skills list: maybe we can list specific technical skills: Rockwell Automation platforms, PLC/HMI software development, industrial networking, safety instrumented