Intermediate Software Engineer
for each section heading. Use - for lists. Use
for prose.
We need to preserve all substantive info, remove boilerplate: "This job description is not a contract..." etc. Also remove "Apply" at end. Also remove "Applicants must be authorized..." etc? That's substantive? It's about work authorization, maybe keep? It's not boilerplate? It's a requirement. Might keep under Qualifications? Could be separate? Probably keep as part of Qualifications or a note. But we can include as a paragraph under Qualifications.
We must not invent sections. Only include sections with real content.
Let's extract:
About the role: first sentence(s) maybe: "The Intermediate Software Engineer utilizes web and cloud technologies, APIs, and third party software development frameworks to build and support basic application solutions."
Responsibilities: list items after "Responsibilities". The text after "Responsibilities" is a run-on sentence with multiple responsibilities separated by periods. We need to split into list items.
Responsibilities text:
"Work collaboratively with other development staff, including contract and offshore Software Engineers, and business product owners in an agile environment.
Perform design and analysis for deliverables.
Support analysis and general architectural design across platforms toward the development of end-to-end solutions.
Utilize third-party software development frameworks, open-source libraries, and APIs to rapidly develop basic application solutions.
Learn and keep pace with the latest advances in the field and rapidly grasp new technologies to support the environment and contribute to project deliverables.
Code, test, identify, implement, and document solutions to business challenges utilizing Python, .NET, web, cloud, and data integration technologies.
Develop, maintain, troubleshoot, and enhance Python-based applications, automation solutions, APIs, ETL processes, and operational support tools.
Support production operations by performing root cause analysis, defect remediation, data validation, automation, and continuous improvement initiatives."
We'll make each as
- .
Qualifications: list after "Qualifications". The text includes many items separated by periods. We'll split.
Qualifications text:
"Bachelor’s degree in computer science, information systems, math, engineering, or other technical field, or equivalent education/experience.
Atleast One year of professional software development experience using Python, .NET/C#, or comparable object-oriented programming languages.
Knowledge of software development languages and frameworks (e.g. Python, .NET/C#, Java, OOD, OOP).
One year of experience and proficiency in database design techniques and philosophies (e.g. RDBMS, Document, Star Schema, Kimball Model).
Understanding of NoSQL database technologies (e.g. MS Cosmos DB, Apache Cassandra, Amazon DynamoDB).
Understanding of cloud services (AWS) utilizing various supporting tools (e.g. EC2, ECS, S3, Kinesis, VMs, Blob, Cosmos, Data Factory, SQL Datawarehouse, ARM Templates, Event Hubs).
Experience with build and deployment tools (e.g. Visual Studio, Git/Bitbucket, Maven, Jenkins, Nexus, SQL Management Studio, Nunit, Ajax).
Knowledge of developing distributed computing (e.g. MS HPC, Sagemaker, Spark).
One year of experience with integration and service frameworks (e.g. API Gateways, Swagger API, Zookeeper, Kafka, messaging tools, microservices).
Experience with continuous integration/development tools (e.g. Jenkins, Docker, Containers, OpenShift, Kubernetes, and container automation) in a Ci/CD pipeline).
Understanding of software development and research tools.
Attention to detail and results oriented, with a strong customer focus.
Ability to work as part of a team and independently.
Analytical and problem-solving skills.
Technical communication skills.
Problem-solving and technical communication skills.
Ability to prioritize workload to meet tight deadlines.
Experience with scripting, automation, and operational support using Python, PowerShell, Bash, or similar technologies."
Note duplicate "Problem-solving and technical communication skills." appears twice; we can keep once? But we must preserve all substantive info; duplicate is still substantive but we could keep both? Might be okay to keep both but could be redundant. We'll keep as separate items? Might be weird. We'll keep as is but maybe combine? Safer to keep both as separate list items.
Preferred Qualifications: list after "Preferred Qualifications". Text:
"Experience developing data processing, automation, integration, or ETL solutions using Python libraries and frameworks.
Experience with AWS services such as Lambda, Glue, S3, IAM, CloudWatch, or serverless application development.
Experience supporting production systems, troubleshooting data issues, and performing root cause analysis in enterprise environments.
Understanding of real time data processing.
Understanding of data mappings and ETL.
Knowledge of the financial services industry."
Working Conditions: after "Working Conditions". Text:
"Hybrid Office Environment (Tuesdays, Wednesdays, Thursdays)
Work outside of normal business hours may be required
Occasional Travel"
Compensation: after "Compensation". Text:
"The Salary for this position generally ranges between $82,000 - $92,000 annually.
Please note that the salary range is a good faith estimate for this position and actual starting pay is determined by several factors including qualifications, experience, geography, work location designation (in-office, hybrid, remote) and operational needs.
Salary may vary above and below the stated amounts, as permitted by applicable law.
Additionally, this position is typically eligible for an Annual Bonus based on the Company Bonus Plan/Individual Performance and is at the Company’s discretion."
Also there is "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is a requirement; could be placed under Qualifications or a separate section like "Eligibility". Since we don't have a specific heading for that, we could add a paragraph under Qualifications or a separate section "Eligibility". But instruction: include a section ONLY when posting has real, specific content for it. It does have content about work authorization. Could make a section "Eligibility" but not in the list of allowed headings? The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Eligibility. So we should fold into Qualifications or maybe Skills. Probably Qualifications.
Also "Relocation assistance will not be provided for this position." That's a condition; could be under Working Conditions or Benefits? Not benefits. Could be under Working Conditions.
Also "Enterprise Technology is a global Aegon/Transamerica organization..." that's boilerplate about company; remove.
Also "We offer a wide range of career opportunities..." remove.
Also "Curiosity is the quality we value most..." remove.
Also "Apply" remove.
Thus final HTML: sections: About the role (p), Responsibilities (ul), Qualifications (ul), Preferred Qualifications (ul), Working Conditions (ul or p?), Schedule? Actually Working Conditions includes hybrid schedule and travel; we could treat as Schedule section. But we already have Working Conditions content; we could make a Schedule section for hybrid days and travel. However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use Schedule for hybrid days/travel. Working Conditions maybe not needed; we can put hybrid schedule under Schedule. The "Work outside of normal business hours may be required" and "Occasional Travel" also schedule-related. So we can make Schedule section with those items.
Thus we will have sections: About the role, Responsibilities, Qualifications, Preferred Qualifications, Schedule, Pay.
We need to include Pay section with salary range and bonus info.
We must not include Benefits (none). No Requirements separate; we have Qualifications.
We must not repeat job title.
Now craft HTML.
We'll wrap each section in appropriate tags.
Example:
About the role
The Intermediate Software Engineer utilizes web and cloud technologies, APIs, and third party software development frameworks to build and support basic application solutions.
Responsibilities
- Work collaboratively with other development staff, including contract and offshore Software Engineers, and business product owners in an agile environment.
- Perform design and analysis for deliverables.
- Support analysis and general architectural design across platforms toward the development of end-to-end solutions.
- Utilize third-party software development frameworks, open-source libraries, and APIs to rapidly develop basic application solutions.
- Learn and keep pace with the latest advances in the field and rapidly grasp new technologies to support the environment and contribute to project deliverables.
- Code, test, identify, implement, and document solutions to business challenges utilizing Python, .NET, web, cloud, and data integration technologies.
- Develop, maintain, troubleshoot, and enhance Python-based applications, automation solutions, APIs, ETL processes, and operational support tools.
- Support production operations by performing root cause analysis, defect remediation, data validation, automation, and continuous improvement initiatives.
Qualifications
- Bachelor’s degree in computer science, information systems, math, engineering, or other technical field, or equivalent education/experience.
- At least One year of professional software development experience using Python, .NET/C#, or comparable object-oriented programming languages.
- Knowledge of software development languages and frameworks (e.g. Python, .NET/C#, Java, OOD, OOP).
- One year of experience and proficiency in database design techniques and philosophies (e.g. RDBMS, Document, Star Schema, Kimball Model).
- Understanding of NoSQL database technologies (e.g. MS Cosmos DB, Apache Cassandra, Amazon DynamoDB).
- Understanding of cloud services (AWS) utilizing various supporting tools (e.g. EC2, ECS, S3, Kinesis, VMs, Blob, Cosmos, Data Factory, SQL Datawarehouse, ARM Templates, Event Hubs).
- Experience with build and deployment tools (e.g. Visual Studio, Git/Bitbucket, Maven, Jenkins, Nexus, SQL Management Studio, Nunit, Ajax).
- Knowledge of developing distributed computing (e.g. MS HPC, Sagemaker, Spark).
- One year of experience with integration and service frameworks (e.g. API Gateways, Swagger API, Zookeeper, Kafka, messaging tools, microservices).
- Experience with continuous integration/development tools (e.g. Jenkins, Docker, Containers, OpenShift, Kubernetes, and container automation) in a Ci/CD pipeline.
- Understanding of software development and research tools.
- Attention to detail and results oriented, with a strong customer focus.
- Ability to work as part of a team and independently.
- Analytical and problem-solving skills.
- Technical communication skills.
- Problem-solving and technical communication skills.
- Ability to prioritize workload to meet tight deadlines.
- Experience with scripting, automation, and operational support using Python, PowerShell, Bash, or similar technologies.
- Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time.
- Relocation assistance will not be provided for this position.
Preferred Qualifications
for prose. We need to preserve all substantive info, remove boilerplate: "This job description is not a contract..." etc. Also remove "Apply" at end. Also remove "Applicants must be authorized..." etc? That's substantive? It's about work authorization, maybe keep? It's not boilerplate? It's a requirement. Might keep under Qualifications? Could be separate? Probably keep as part of Qualifications or a note. But we can include as a paragraph under Qualifications. We must not invent sections. Only include sections with real content. Let's extract: About the role: first sentence(s) maybe: "The Intermediate Software Engineer utilizes web and cloud technologies, APIs, and third party software development frameworks to build and support basic application solutions." Responsibilities: list items after "Responsibilities". The text after "Responsibilities" is a run-on sentence with multiple responsibilities separated by periods. We need to split into list items. Responsibilities text: "Work collaboratively with other development staff, including contract and offshore Software Engineers, and business product owners in an agile environment. Perform design and analysis for deliverables. Support analysis and general architectural design across platforms toward the development of end-to-end solutions. Utilize third-party software development frameworks, open-source libraries, and APIs to rapidly develop basic application solutions. Learn and keep pace with the latest advances in the field and rapidly grasp new technologies to support the environment and contribute to project deliverables. Code, test, identify, implement, and document solutions to business challenges utilizing Python, .NET, web, cloud, and data integration technologies. Develop, maintain, troubleshoot, and enhance Python-based applications, automation solutions, APIs, ETL processes, and operational support tools. Support production operations by performing root cause analysis, defect remediation, data validation, automation, and continuous improvement initiatives." We'll make each as
About the role
The Intermediate Software Engineer utilizes web and cloud technologies, APIs, and third party software development frameworks to build and support basic application solutions.
Responsibilities
- Work collaboratively with other development staff, including contract and offshore Software Engineers, and business product owners in an agile environment.
- Perform design and analysis for deliverables.
- Support analysis and general architectural design across platforms toward the development of end-to-end solutions.
- Utilize third-party software development frameworks, open-source libraries, and APIs to rapidly develop basic application solutions.
- Learn and keep pace with the latest advances in the field and rapidly grasp new technologies to support the environment and contribute to project deliverables.
- Code, test, identify, implement, and document solutions to business challenges utilizing Python, .NET, web, cloud, and data integration technologies.
- Develop, maintain, troubleshoot, and enhance Python-based applications, automation solutions, APIs, ETL processes, and operational support tools.
- Support production operations by performing root cause analysis, defect remediation, data validation, automation, and continuous improvement initiatives.
Qualifications
- Bachelor’s degree in computer science, information systems, math, engineering, or other technical field, or equivalent education/experience.
- At least One year of professional software development experience using Python, .NET/C#, or comparable object-oriented programming languages.
- Knowledge of software development languages and frameworks (e.g. Python, .NET/C#, Java, OOD, OOP).
- One year of experience and proficiency in database design techniques and philosophies (e.g. RDBMS, Document, Star Schema, Kimball Model).
- Understanding of NoSQL database technologies (e.g. MS Cosmos DB, Apache Cassandra, Amazon DynamoDB).
- Understanding of cloud services (AWS) utilizing various supporting tools (e.g. EC2, ECS, S3, Kinesis, VMs, Blob, Cosmos, Data Factory, SQL Datawarehouse, ARM Templates, Event Hubs).
- Experience with build and deployment tools (e.g. Visual Studio, Git/Bitbucket, Maven, Jenkins, Nexus, SQL Management Studio, Nunit, Ajax).
- Knowledge of developing distributed computing (e.g. MS HPC, Sagemaker, Spark).
- One year of experience with integration and service frameworks (e.g. API Gateways, Swagger API, Zookeeper, Kafka, messaging tools, microservices).
- Experience with continuous integration/development tools (e.g. Jenkins, Docker, Containers, OpenShift, Kubernetes, and container automation) in a Ci/CD pipeline.
- Understanding of software development and research tools.
- Attention to detail and results oriented, with a strong customer focus.
- Ability to work as part of a team and independently.
- Analytical and problem-solving skills.
- Technical communication skills.
- Problem-solving and technical communication skills.
- Ability to prioritize workload to meet tight deadlines.
- Experience with scripting, automation, and operational support using Python, PowerShell, Bash, or similar technologies.
- Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time.
- Relocation assistance will not be provided for this position.