Infrastructure Automation Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Position Type: Contract - Duration: 12+ Months - Location: Chandler, AZ - Required Qualifications: Experience of software development in building enterprise-level software Using Python AND Expertise in Ansible - Participate in agile software development processes and contribute to project planning and estimation. Familiarity with project management tool such as JIRA. - Work with development team to integrate automation solution into a workflow. - Understand of software development life cycle and participate in SDLC process and contribute to the design, development, and testing phases. - Unit testing and system integration testing. - Experience with CI/CD tool (Jenkins), Deployment scripting. - Hands-on experience with Git and version control practices. - Qualified candidates should APPLY NOW for immediate consideration! This position is only open to applicants who can be engaged on a W-2 basis. - Please hit APPLY to provide the required information, and we will be back in touch as soon as possible. - We are currently interviewing to fill this and other similar positions. If this role is not a fit for you, we do offer a referral bonus program for referrals that we successfully place with our clients, subject to program guidelines. ASK ME HOW. - Thank you! - Aquib Khan (+1) 208-620-3124 Aquib.Khan@innovasolutions.com - PAY RANGE AND BENEFITS: - Pay Range*: $65/hr to $70/hr - *Pay range offered to a successful candidate will be based on several factors, including the candidate's education, work experience, work location, specific job duties, certifications, etc. - Benefits: Innova Solutions offers benefits( based on eligibility) that include the following: Medical & pharmacy coverage, Dental/vision insurance, 401(k), Health saving account (HSA) and Flexible spending account (FSA), Life Insurance, Pet Insurance, Short term and Long term Disability, Accident & Critical illness coverage, Pre-paid legal & ID theft protection, Sick time, and other types of paid leaves (as required by law), Employee Assistance Program (EAP). - ABOUT INNOVA SOLUTIONS: ... (company description) - Recent Recognitions: ... (list) - Website: https://www.innovasolutions.com/ - Innova Solutions offers a referral bonus for qualified Ambassadors who refer eligible referrals. Submit referrals at https://innovasolutions.workllama.com/atsuser/anonreferafriend and earn $250-$1,000 per referral. - Innova Solutions is an Equal Opportunity Employer ... (EEO boilerplate) - The company will consider for employment qualified applicants with arrest and conviction records ... (Fair Chance) - By applying for this job, you agree to receive calls, AI-generated calls, text messages, or emails ... (privacy/TCPA) We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove: - "Qualified candidates should APPLY NOW for immediate consideration! This position is only open to applicants who can be engaged on a W-2 basis." - "Please hit APPLY to provide the required information, and we will be back in touch as soon as possible." - "We are currently interviewing to fill this and other similar positions. If this role is not a fit for you, we do offer a referral bonus program for referrals that we successfully place with our clients, subject to program guidelines. ASK ME HOW." - "Thank you!" - Contact info (Aquib Khan phone email) maybe considered metadata; we can fold minor metadata into a short
or drop it. Probably drop contact info. - "PAY RANGE AND BENEFITS:" heading not needed as we will have separate Pay and Benefits sections. - The pay range details: we need Pay section if posting actually states them. Yes, they have Pay Range: $65/hr to $70/hr. Also note about factors. That's substantive. So include Pay section. - Benefits: they list benefits. So include Benefits section. - About Innova Solutions: that's company description, not about the role. Should we include? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave examples but we can include other headings? Probably only those headings. The "About Innova Solutions" is not one of the listed headings; we could treat as "About the role"? No, that's about the role, not company. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we shouldn't invent other headings. So we should not include a section for About Innova Solutions. However we need to preserve ALL substantive information; but we can incorporate company description maybe into a
without a heading? The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose." It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings but they gave examples. Safer to stick to those headings only. So we can omit company description entirely? But that would lose substantive information. However maybe company description is considered boilerplate? It's not exactly boilerplate but it's about the company. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep it. But we need to put it somewhere. Could we put it under a heading like "About the role"? That's not accurate. Could we put it under a generic
without heading? 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 suggests using those for sections. It might be okay to have a heading like "About Innova Solutions" but not in the list. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. Safer to follow exactly: only those headings. Then where to put company description? Could be omitted? But that would lose info. Maybe we can treat company description as part of "About the role"? Not really. Could we incorporate it into a
under "About the role"? The role description is about the job, not company. But we could still put company info there as extra prose. Might be acceptable.
Better: We'll create sections: About the role (maybe a brief description of the role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present, so omit.
We need to extract responsibilities: list of duties.
From posting:
- Participate in agile software development processes and contribute to project planning and estimation. Familiarity with project management tool such as JIRA.
- Work with development team to integrate automation solution into a workflow.
- Understand of software development life cycle and participate in SDLC process and contribute to the design, development, and testing phases.
- Unit testing and system integration testing.
- Experience with CI/CD tool (Jenkins), Deployment scripting.
- Hands-on experience with Git and version control practices.
These are responsibilities/duties.
Requirements: "Experience of software development in building enterprise-level software Using Python AND Expertise in Ansible"
Also maybe "Participate in agile software development processes..." is more responsibility.
Qualifications: maybe same as requirements? The posting has "Required Qualifications" then the bullet about Python and Ansible. Then later "Qualified candidates should APPLY NOW..." etc. So we can treat that as Qualifications.
Skills: maybe list of specific skills: Python, Ansible, JIRA, SDLC, Jenkins, Git, CI/CD, Deployment scripting.
We can separate.
Benefits: list as given.
Pay: $65/hr to $70/hr.
Now we need to strip boilerplate: remove application instructions, referral program, EEO, Fair Chance, privacy/TCPA, contact info, website, etc.
Also remove "About Innova Solutions" and "Recent Recognitions" maybe considered boilerplate? It's substantive about company but not required headings. Might be considered extra but we could keep as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could include a heading "About the company" but not in list. Might be considered inventing a heading. Better to omit? But we need to preserve ALL substantive information. If we omit company description, we lose info. However maybe the company description is considered boilerplate? It's not standard legal boilerplate; it's marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove company description. So we should keep it.
Thus we need a way to include it without violating heading rule. Perhaps we can put it under a heading "About the role" but that is inaccurate. Could we use a generic heading like "About Innova Solutions"? 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 an exhaustive list. So we can use other headings as long as they are . So we can use About Innova Solutions
. That seems okay.
Thus we will include sections: About the role (maybe a brief summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, About Innova Solutions (or Company Overview). But we need to avoid thin sections. The About Innova Solutions section has substantive content (company description, recognitions, website, referral bonus). That's substantive.
We also need to avoid duplicating lines.
Let's extract company description:
"Founded in 1998 and headquartered in Atlanta, Georgia, Innova Solutions employs approximately 50,000 professionals worldwide and reports an annual revenue approaching $3 Billion. Through our global delivery centers across North America, Asia, and Europe, we deliver strategic technology and business transformation solutions to our clients, enabling them to operate as leaders within their fields.
Recent Recognitions:
- Named One of America’s Best Employers for New Grads by Forbes (2024)
- Named One of the Best Companies to Work for by U.S. News & World Report (Private Companies List, 2024-2025)
- One of the Largest IT Staffing Firms in the US – Ranked #3 by Staffing Industry Analysts (SIA, 2024)
- One of the Largest Staffing Firms in the US – Ranked #13 by Staffing Industry Analysts (SIA, 2024; includes Innova Solutions, Volt, & HireGenics)
- Named One of the Top Ten Private Companies in Atlanta by the Atlanta Business Chronicle (2023)
- One of the Largest Certified Minority Business Enterprises (MBEs
for prose." It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings but they gave examples. Safer to stick to those headings only. So we can omit company description entirely? But that would lose substantive information. However maybe company description is considered boilerplate? It's not exactly boilerplate but it's about the company. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep it. But we need to put it somewhere. Could we put it under a heading like "About the role"? That's not accurate. Could we put it under a generic
without heading? 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 suggests using those for sections. It might be okay to have a heading like "About Innova Solutions" but not in the list. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. Safer to follow exactly: only those headings. Then where to put company description? Could be omitted? But that would lose info. Maybe we can treat company description as part of "About the role"? Not really. Could we incorporate it into a
under "About the role"? The role description is about the job, not company. But we could still put company info there as extra prose. Might be acceptable. Better: We'll create sections: About the role (maybe a brief description of the role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present, so omit. We need to extract responsibilities: list of duties. From posting: - Participate in agile software development processes and contribute to project planning and estimation. Familiarity with project management tool such as JIRA. - Work with development team to integrate automation solution into a workflow. - Understand of software development life cycle and participate in SDLC process and contribute to the design, development, and testing phases. - Unit testing and system integration testing. - Experience with CI/CD tool (Jenkins), Deployment scripting. - Hands-on experience with Git and version control practices. These are responsibilities/duties. Requirements: "Experience of software development in building enterprise-level software Using Python AND Expertise in Ansible" Also maybe "Participate in agile software development processes..." is more responsibility. Qualifications: maybe same as requirements? The posting has "Required Qualifications" then the bullet about Python and Ansible. Then later "Qualified candidates should APPLY NOW..." etc. So we can treat that as Qualifications. Skills: maybe list of specific skills: Python, Ansible, JIRA, SDLC, Jenkins, Git, CI/CD, Deployment scripting. We can separate. Benefits: list as given. Pay: $65/hr to $70/hr. Now we need to strip boilerplate: remove application instructions, referral program, EEO, Fair Chance, privacy/TCPA, contact info, website, etc. Also remove "About Innova Solutions" and "Recent Recognitions" maybe considered boilerplate? It's substantive about company but not required headings. Might be considered extra but we could keep as a
without heading? The instruction says use