Jobs · OTHR · Texas

Software Engineer - IV

VARITE INC · Dallas, TX · 3 wk ago
HybridOTHR$61.57/hrFull-time
We need to output HTML fragment with sections for headings where content exists. The posting is messy: It starts with VARITE looking for a qualified Software Engineer - IV then description of client (central banking system) etc. Then "Job Title: Software Engineer - IV Location: Dallas, TX 75201 Duration: 18 months Mode: Hybrid/ Remote is also acceptable Pay Range: $61.57/hr. - $70.80/hr. on W2". Then "Here’s What You’ll Do Qualifications: *** Job Title: Senior Automation Engineer - Ansible *** This position can be hybrid, remote or onsite. Only US citizens Ansible skillset required". Then responsibilities list etc. Then qualifications list. Then benefits list. Then application instructions etc which we need to remove. We need to preserve all substantive info, but remove boilerplate, duplicated lines, application instructions, EEO etc. Also we must not repeat job title as heading (the page already shows it). So we should not include a heading for "Software Engineer - IV". Instead we can include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. We need to decide what sections to include based on content. We have: - About the role / What does the client do? and What do we do? Could be "About the role" or "About the company". Probably "About the role" includes description of client and VARITE. - Responsibilities: list of duties (the bullet points after "What Will Be Expected of You"). - Qualifications: list of qualifications (the bullet points after "Qualifications"). - Skills: maybe combine with qualifications? But we can have separate Skills if distinct. The qualifications list includes many skill items; we could treat that as Qualifications. Could also have Skills section for technical skills like Ansible, Python, Bash, PowerShell, RESTful APIs, IaC, CI/CD, etc. But to avoid thin sections, we can combine into Qualifications. - Benefits: list of benefits (Health Insurance, Retirement Plans, Legal Service Plans). - Pay: Pay Range given. - Schedule: Duration and Mode? Could be Schedule section: Duration 18 months, Mode Hybrid/Remote. We must not create sections with filler like "commensurate with experience". We have actual pay range, so Pay section is valid. Schedule: we have Duration: 18 months, Mode: Hybrid/ Remote is also acceptable. That's substantive. We need to avoid repeating job title as heading. So we will not have a heading for Software Engineer - IV. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading, then content: either

for prose or

  • for lists. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we should cut out the lines about EasyApply, referral fee, EEO statement, etc. Also need to remove duplicated lines like "Job Title: Senior Automation Engineer - Ansible" appears earlier? Actually there is a weird mix: The posting seems to have two job titles: Software Engineer - IV and Senior Automation Engineer - Ansible. The content after "Here’s What You’ll Do Qualifications: *** Job Title: Senior Automation Engineer - Ansible ***" seems to be the actual job description for Senior Automation Engineer - Ansible. The earlier part about Software Engineer - IV may be a mistake. We need to preserve all substantive information; but we need to decide which is the actual job. The posting seems to be a mix; maybe the correct job is Senior Automation Engineer - Ansible, with details about responsibilities, qualifications, benefits, pay, schedule. The earlier part about Software Engineer - IV includes location, duration, pay range, but that may be for a different job. However we must preserve all substantive information; we cannot discard info that is part of the posting. But we need to avoid duplication and contradictory info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include both sets? But they conflict: different job titles, responsibilities, etc. However the later section includes responsibilities and qualifications that match the Senior Automation Engineer - Ansible. The earlier part includes location, duration, pay range, but not responsibilities. The later part also includes benefits. The pay range is given earlier: $61.57/hr - $70.80/hr on W2. That likely applies to the Senior Automation Engineer role. So we can combine: The job is Senior Automation Engineer - Ansible, location Dallas, TX 75201, duration 18 months, mode hybrid/remote, pay range as given. The earlier "Software Engineer - IV" may be a mistake; but we should not invent or summarize away detail; we could include that as a note? But that would be inaccurate. The instruction says do not invent or summarize away detail. If we discard the "Software Engineer - IV" line, we are removing substantive information (the job title). But maybe that line is boilerplate? It's not clearly boilerplate; it's a job title. However the later section clearly defines the role as Senior Automation Engineer - Ansible. The earlier "Software Engineer - IV" could be a mislabel. We need to decide which to keep. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep both? But that would be contradictory and confusing. However we could treat the earlier "Software Engineer - IV" as a heading that we must not repeat as heading (the page already shows it). But we are not supposed to repeat the job title as a heading. The page already shows it (maybe the actual title shown elsewhere). So we could omit repeating it as a heading, but we could still include the info in a paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include the job title in a paragraph if we want, but not as heading. However the later section also has a job title line "Job Title: Senior Automation Engineer - Ansible". That is also a job title; we should not repeat it as heading either. So we could treat that as a paragraph or maybe we just not include any job title heading, but we can include the job title in a paragraph under About the role? The instruction says we should not repeat the job title as a heading; it's okay to include it elsewhere. Thus we could create an "About the role" paragraph that includes the job title and location etc. Then responsibilities, qualifications, benefits, pay, schedule. We need to avoid duplication: The earlier part also had "What does the client do?" and "What do we do?" which is about the client and VARITE. That is substantive about the role/company. We'll include that in About the role. Now we need to extract responsibilities list: The bullet points after "What Will Be Expected of You". Let's list them: - Work in multiple service automation engagements to automate the high priority tasks, services and end to end workflows across Infrastructure, Platforms & Operations - Design, develop, and maintain end-to-end automation solutions using Ansible (playbooks, roles, modules, and workflows) for complex, secure enterprise environments - Execute the full software development lifecycle for automation projects, from requirements gathering through deployment, maintenance, support and hand-over - Create advanced automation scripts using Python, Bash, and/or PowerShell to address complex business requirements and develop custom tools that enhance operational efficiency - Develop and maintain RESTful APIs using modern frameworks (FastAPI, Flask) to orchestrate automation workflows and implement integration patterns that connect diverse enterprise systems - Build and optimize Infrastructure as Code (IaC) solutions with CI/CD pipelines, version control best practices, and automated testing frameworks to ensure code quality and reliability - Collaborate within Agile and Scaled Agile frameworks with cross-functional teams including infrastructure, security, and service teams to deliver integrated solutions - Implement secure coding practices and ensure all automation solutions comply with enterprise security policies and banking regulations where applicable - Document solutions, create runbooks, and maintain knowledge base articles - Provide technical support for automations, troubleshoot production issues, and participate in on-call rotation as needed - Stay current with emerging automation technologies and contribute to automation standards, best practices, and governance frameworks - Other duties assigned as necessary We need to keep all. Qualifications list after "Qualifications": - 7+ years of extensive experience in end-to-end enterprise software development life cycle experience, automation including maintenance and support - Advanced Ansible Expertise: Proven experience developing playbooks, roles, modules and workflows for complex and secure enterprise environments - Scripting Proficiency: Advanced skills in Python, Bash, or PowerShell for custom automation solutions - API Development and Integration: Expertise in building RESTful APIs using modern frameworks (FastAPI, Flask) and implementing diverse integration patterns to trigger and orchestrate automation workflows - Infrastructure as Code (IaC): Proficiency in version control, CI/CD pipelines, and automated testing frameworks - Multi-Platform Knowledge: Strong understanding of Linux/Unix systems, Windows, and cloud platforms (AWS/Azure) - Bachelor’s degree in computer science, Information Systems, or equivalent background or equivalent experience. - Experience with automation orchestration platforms (e.g., ServiceNow, ARIA ) is a plus - Working experience in Agile and Scaled Agile environments - Knowledge of secure coding standards and banking environment is a plus We need to keep all. Benefits list: - Health Insurance: Medical, dental, and vision coverage - Retirement Plans: Participation in a company-sponsored retirement savings plan - Legal Service Plans - Offering access to attorneys for legal advice and representation We need to keep all. Pay: "$61.57/hr. - $70.80/hr. on W2" Schedule: Duration: 18 months, Mode: Hybrid/ Remote is also acceptable. Location: Dallas, TX 75201 (from earlier). We could include location in About the role or Schedule? Probably About the role. Now we need to remove boilerplate: lines like "Here’s What You’ll Do Qualifications: *** Job Title: Senior Automation Engineer - Ansible *** This position can be hybrid, remote or onsite. Only US citizens Ansible skillset required" - we need to parse that. Actually that line seems to be a mix: "Here’s What You’ll Do Qualifications: *** Job Title: Senior Automation Engineer - Ansible *** This position can be hybrid, remote or onsite. Only US citizens Ansible skillset required". We should extract the useful parts: "This position can be hybrid, remote or onsite." (mode), "Only US citizens" (maybe a requirement), "Ansible skillset required" (skill). The "Only US citizens" is a requirement; we could include that in Qualifications or Requirements. But we already have qualifications list; we could add a bullet: "Must be a US citizen". However the instruction says preserve all substantive information; we should not discard "Only US citizens". So we need to include that as a qualification. Also "Ansible skillset required" is already covered. We also need to remove duplicated lines: The phrase "Here’s What You’ll Do Qualifications:" seems like a heading but we will not use it as heading; we will treat the content. We also need to remove application instructions: "If this opportunity interests you, please respond by clicking on EasyApply. In case you are not currently available or interested in pursuing this opportunity, please forward this email among your circle who might be suitable and interested in any of our open requirements. VARITE has a robust Candidate Referral Fee plan where you will receive a one-time referral fee if the referred candidate successfully works with VARITE on an assignment for at least 1 month or 160 Hours." Also EEO statement at end. Remove those. Also remove lines like "VARITE is committed to creating a diverse environment and is proud to be an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender

Similar jobs

Software Engineer - IV

Primary Talent PartnersAtlanta, GA· 2 mo ago
Engineering$54–$64/hrapply on www1.jobdiva.com

Software Engineer IV

SpectrumGreenwood Village, CO· 2 mo ago
Engineering$88k–$157k/yrapply on jobs.spectrum.com

Software Engineer IV

Murphy USAEl Dorado, AR· 3 mo ago
Information Technologyapply on sjobs.brassring.com

Software Engineer IV

BlueScope North AmericaKansas City, MO· 2 mo ago
Engineeringapply on bluescopenac.wd5.myworkdayjobs.com

Software Engineer IV

BlueScope Buildings North America, Inc.Kansas City, MO· 2 mo ago
Engineeringapply on bluescopenac.wd5.myworkdayjobs.com