Senior Software Engineer - Full Stack Java/React
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content from posting.
First, identify sections:
- Overview: description of company, role context. Could be "About the role" maybe. The overview includes description of Enterprise Mobility, IT team, hybrid work, benefits mention. We can put that under "About the role". Should include details: company description, team, hybrid work schedule, benefits mention (market-competitive pay, healthcare, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential). Also mention eligibility for hybrid schedule, location (Lakeside and/or Clayton Corporate HQ campus in St. Louis, Missouri). Also mention hiring process details? Those are boilerplate maybe but they are part of overview? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The hiring process details (identity verification, video interviews, etc.) might be considered application instructions? Probably we should drop them as they are part of hiring process. The overview also mentions "We are committed to a fair and transparent hiring process..." That's boilerplate; we should remove. Also "Candidates should expect identity verification..." etc. Remove.
Thus About the role: include company description, role context, hybrid work, benefits (market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential). Also mention location: Lakeside and/or Clayton Corporate HQ campus in St. Louis, Missouri.
Now Responsibilities: The posting has a big block under "Responsibilities". We need to extract that content. It includes description of ARMS department, role responsibilities. We'll put that under Responsibilities
with - items for each duty? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we need to decide if responsibilities are a list or prose. The responsibilities block is paragraph-like but contains multiple sentences. Could be turned into list items for each duty. Better to split into bullet points. Let's parse responsibilities:
Paragraph: "The ARMS (Automated Rental Management System) Department is responsible for managing the core B2B platform that automates communication, vehicle authorizations, and billing between Enterprise Mobility and its insurance, collision repair, and dealership partners. In addition to supporting these critical external integrations, the department builds, maintains, and modernizes the underlying platform to ensure reliable, scalable rental workflows and seamless partner connectivity through APIs and a modernized user interface. This team focuses on operational support, continuous improvement, and product optimization within ARMS, directly impacting system stability and user experience across the business. The role will support production operations, partner integrations, and modernization initiatives, including API enhancements, UI improvements, and ongoing defect resolution and performance optimization. The team works closely with rental operations, product and engineering teams, and external partners to ensure efficient, accurate transactions and continuous delivery of business value."
Then: "As an Engineer 2 in the Automated Rental Management System (ARMS), you will be responsible for using your technical knowledge to solve business problems. We are looking for a talented individual who can serve as a subject matter expert in their focus area and represent their department on complex assignments. You will be responsible for evaluating technical elements of our product offerings through requirements gathering, testing, research, and investigation and make recommendations for improvements that result in increased quality. You will be required to evaluate customer needs to determine and provide high-quality solutions that align with customer expectations. In this role on the ARMS development team, you will be responsible for designing, modifying, and developing complex code independently, within various teams using applicable technologies. You will be responsible for mentoring, driving standards, ensuring code performance, contributing to code reviews, performing unit and integration testing, and analysis and review of software requirements. This position will partner with our Production Support team to troubleshoot and resolve application issues, our business partners to implement enhancements, and our Modernization teams to support API and new technologies. You should also have a strong team orientation and a sense of leadership and ownership. This role will require you to have strong knowledge of Java, which will enable you to research and fix issues. You will also be part of after-hours “On-Call Rotation” after getting up to speed."
We can turn each sentence into bullet.
Now Knowledge, Skills, And Abilities: list of bullet points. We'll put under
Skills
maybe. The heading "Skills" is allowed. The content includes bullet points: Must possess excellent analytical, problem-solving and decision-making skills; Must possess willingness and drive to learn; Must be able to work with minimal supervision; Strong teamwork abilities in a collaborative environment; Strong verbal and written communication skills; Experience with agile development methodologies and tools such as Scrum or Kanban; Experience with source control management (Bitbucket/GIT); Experience with end-to-end testing using playwright or similar tools; Experience in the full software development lifecycle using tools such as Spring Tool Suite (STS) and/or IntelliJ IDEA or any other IDE (VS Code) for application development, debugging, and performance tuning.
We'll output as - each.
Qualifications: The posting has "Qualifications Required:" and then list. Also "Preferred" bullet list. We need to decide whether to put under Requirements or Qualifications. The allowed headings include Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We already used Skills for KSAs. We could put required qualifications under "Requirements" and preferred under "Qualifications". Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have required qualifications and preferred qualifications. Could make two sections: Requirements (required) and Qualifications (preferred). That seems appropriate.
Thus:
Requirements
with - for each required bullet.
Required bullets:
- Must be presently authorized to work in the U.S. without a requirement for work authorization sponsorship by our company for this position now or in the future
- Must reside in St. Louis, Missouri, or immediate surrounding area
- 3+ years of software development experience using Java, Spring Framework, Spring Boot, and Spring WebFlux to build reactive, event-driven microservices leveraging Project Reactor (Mono/Flux) and non-blocking APIs.
- 2+ years experience in front-end frameworks including TypeScript, React(Hooks, Context API, Redux), component-driven architecture and styling technologies including SASS, LESS, and SCSS.
- 2+ years of experience creating and implementing SQL
- Strong knowledge of SOA (Service-Oriented Architecture), RESTful API design, and API consumption within React applications.
- Experience in Struts, Angular, and Postman preferred. (This is actually under Preferred? Wait it's in Required block? The text: "Experience in Struts, Angular, and Postman preferred." It appears under Required? Actually after "Strong knowledge of SOA..." then "Experience in Struts, Angular, and Postman preferred." That seems like a preferred item but placed in Required block. We'll treat as required? It says preferred, but it's in the Required block. Safer to treat as required? But we have a separate Preferred section later. We'll move this to Preferred.
- Experience building, deploying, and supporting Spring Boot microservices on AWS
- Must be committed to incorporating security into all decisions and daily job responsibilities
Now Preferred bullets:
- Bachelor's degree in Computer Science, Computer Information Systems, Management Information Systems, or related field
- Experience with Cloud technologies (AWS)
- Experience with frameworks such as Hibernate and Struts
- Experience with WebLogic
- Experience with Jenkins or other continuous integration tools
- Experience with Putty
- Experience with Splunk
- Experience with Artifactory
- Experience with JIRA, Confluence, and/or similar tool
- Experience with Cloud technologies (Azure, Terraform)
- Experience with Postman/SOAP UI
- Experience with Dynatrace
Also note "Experience with Cloud technologies (AWS)" appears twice? Actually appears in Required (Experience building, deploying, and supporting Spring Boot microservices on AWS) and Preferred (Experience with Cloud technologies (AWS)). We'll keep both.
Now Benefits: The overview mentions benefits: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential. Also hybrid work schedule eligibility. So we can put Benefits section with those items.
Pay: The posting mentions "market-competitive pay" but not specific numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "market-competitive pay" which is a statement about pay, albeit vague. Is that enough? The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "market-competitive pay" is not a specific number but it's a statement. Is that considered filler? It's vague but it's a statement about pay. The instruction says avoid filler like "commensurate with experience". "market-competitive pay" is similar vague. Might be considered filler. Safer to not create Pay section unless there is explicit number or range. Since they didn't give numbers, we should omit Pay section.
Schedule: The posting mentions hybrid work schedule, ability to work from home, also need to be in person as needed at Lakeside and/or Clayton Corporate HQ campus locations. That's schedule info. So we can create Schedule section with that detail.
Benefits: we have benefits list.
Now we need to ensure we don't duplicate content. Overview already mentioned hybrid schedule and benefits; we might move those details to Benefits and Schedule sections, and keep About the role focusing on company description and role context.
Let's craft About the role: description of Enterprise Mobility, its brands, fleet size, revenue, locations, IT team role, hybrid work eligibility, location (Lakeside/Clayton). Not include benefits/hybrid schedule details (move to Benefits/Schedule). Also mention that we offer excellent package etc? That's benefits. So we keep About the role focusing on company description and team.
Now Benefits: list: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential.
Schedule: hybrid work schedule, ability to work from home, required in-person as needed at Lakeside and/or Clayton Corporate HQ campus locations in St. Louis, Missouri.
Now we need to ensure we don't include boilerplate like EEO etc. Already removed.
Now produce HTML fragment:
About the role
Enterprise Mobility is a leading provider of mobility solutions, owning and operating the Enterprise Rent-A-Car, National Car Rental and Alamo Rent A Car brands through its integrated global network of independent regional subsidiaries. Enterprise Mobility and its affiliates offer extensive car rental, carsharing, truck rental, fleet management, retail car sales, as well as travel management and other transportation services, to make travel easier and more convenient for customers. Privately held by the Taylor family of St. Louis, Enterprise Mobility together with its affiliate Enterprise Fleet Management manages a diverse fleet of 2.4 million vehicles and accounted for nearly $39 billion in revenue through a network of more than 9,500 fully-staffed neighborhood and airport rental locations in more than 90 countries and territories. At the center of it all, our dedicated IT teams innovate, design and develop the technology that is redefining how customers rent, buy and share vehicles from our family of brands. Here, you will be part of a diverse and talented team that creates and delivers powerful technology
- for any list of duties/requirements/benefits, and
for prose. So we need to decide if responsibilities are a list or prose. The responsibilities block is paragraph-like but contains multiple sentences. Could be turned into list items for each duty. Better to split into bullet points. Let's parse responsibilities: Paragraph: "The ARMS (Automated Rental Management System) Department is responsible for managing the core B2B platform that automates communication, vehicle authorizations, and billing between Enterprise Mobility and its insurance, collision repair, and dealership partners. In addition to supporting these critical external integrations, the department builds, maintains, and modernizes the underlying platform to ensure reliable, scalable rental workflows and seamless partner connectivity through APIs and a modernized user interface. This team focuses on operational support, continuous improvement, and product optimization within ARMS, directly impacting system stability and user experience across the business. The role will support production operations, partner integrations, and modernization initiatives, including API enhancements, UI improvements, and ongoing defect resolution and performance optimization. The team works closely with rental operations, product and engineering teams, and external partners to ensure efficient, accurate transactions and continuous delivery of business value." Then: "As an Engineer 2 in the Automated Rental Management System (ARMS), you will be responsible for using your technical knowledge to solve business problems. We are looking for a talented individual who can serve as a subject matter expert in their focus area and represent their department on complex assignments. You will be responsible for evaluating technical elements of our product offerings through requirements gathering, testing, research, and investigation and make recommendations for improvements that result in increased quality. You will be required to evaluate customer needs to determine and provide high-quality solutions that align with customer expectations. In this role on the ARMS development team, you will be responsible for designing, modifying, and developing complex code independently, within various teams using applicable technologies. You will be responsible for mentoring, driving standards, ensuring code performance, contributing to code reviews, performing unit and integration testing, and analysis and review of software requirements. This position will partner with our Production Support team to troubleshoot and resolve application issues, our business partners to implement enhancements, and our Modernization teams to support API and new technologies. You should also have a strong team orientation and a sense of leadership and ownership. This role will require you to have strong knowledge of Java, which will enable you to research and fix issues. You will also be part of after-hours “On-Call Rotation” after getting up to speed." We can turn each sentence into bullet. Now Knowledge, Skills, And Abilities: list of bullet points. We'll put under
Skills
maybe. The heading "Skills" is allowed. The content includes bullet points: Must possess excellent analytical, problem-solving and decision-making skills; Must possess willingness and drive to learn; Must be able to work with minimal supervision; Strong teamwork abilities in a collaborative environment; Strong verbal and written communication skills; Experience with agile development methodologies and tools such as Scrum or Kanban; Experience with source control management (Bitbucket/GIT); Experience with end-to-end testing using playwright or similar tools; Experience in the full software development lifecycle using tools such as Spring Tool Suite (STS) and/or IntelliJ IDEA or any other IDE (VS Code) for application development, debugging, and performance tuning. We'll output as- each.
Qualifications: The posting has "Qualifications Required:" and then list. Also "Preferred" bullet list. We need to decide whether to put under Requirements or Qualifications. The allowed headings include Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We already used Skills for KSAs. We could put required qualifications under "Requirements" and preferred under "Qualifications". Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have required qualifications and preferred qualifications. Could make two sections: Requirements (required) and Qualifications (preferred). That seems appropriate.
Thus:
Requirements
with- for each required bullet.
Required bullets:
- Must be presently authorized to work in the U.S. without a requirement for work authorization sponsorship by our company for this position now or in the future
- Must reside in St. Louis, Missouri, or immediate surrounding area
- 3+ years of software development experience using Java, Spring Framework, Spring Boot, and Spring WebFlux to build reactive, event-driven microservices leveraging Project Reactor (Mono/Flux) and non-blocking APIs.
- 2+ years experience in front-end frameworks including TypeScript, React(Hooks, Context API, Redux), component-driven architecture and styling technologies including SASS, LESS, and SCSS.
- 2+ years of experience creating and implementing SQL
- Strong knowledge of SOA (Service-Oriented Architecture), RESTful API design, and API consumption within React applications.
- Experience in Struts, Angular, and Postman preferred. (This is actually under Preferred? Wait it's in Required block? The text: "Experience in Struts, Angular, and Postman preferred." It appears under Required? Actually after "Strong knowledge of SOA..." then "Experience in Struts, Angular, and Postman preferred." That seems like a preferred item but placed in Required block. We'll treat as required? It says preferred, but it's in the Required block. Safer to treat as required? But we have a separate Preferred section later. We'll move this to Preferred.
- Experience building, deploying, and supporting Spring Boot microservices on AWS
- Must be committed to incorporating security into all decisions and daily job responsibilities
Now Preferred bullets:
- Bachelor's degree in Computer Science, Computer Information Systems, Management Information Systems, or related field
- Experience with Cloud technologies (AWS)
- Experience with frameworks such as Hibernate and Struts
- Experience with WebLogic
- Experience with Jenkins or other continuous integration tools
- Experience with Putty
- Experience with Splunk
- Experience with Artifactory
- Experience with JIRA, Confluence, and/or similar tool
- Experience with Cloud technologies (Azure, Terraform)
- Experience with Postman/SOAP UI
- Experience with Dynatrace
Also note "Experience with Cloud technologies (AWS)" appears twice? Actually appears in Required (Experience building, deploying, and supporting Spring Boot microservices on AWS) and Preferred (Experience with Cloud technologies (AWS)). We'll keep both.
Now Benefits: The overview mentions benefits: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential. Also hybrid work schedule eligibility. So we can put Benefits section with those items.
Pay: The posting mentions "market-competitive pay" but not specific numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "market-competitive pay" which is a statement about pay, albeit vague. Is that enough? The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "market-competitive pay" is not a specific number but it's a statement. Is that considered filler? It's vague but it's a statement about pay. The instruction says avoid filler like "commensurate with experience". "market-competitive pay" is similar vague. Might be considered filler. Safer to not create Pay section unless there is explicit number or range. Since they didn't give numbers, we should omit Pay section.
Schedule: The posting mentions hybrid work schedule, ability to work from home, also need to be in person as needed at Lakeside and/or Clayton Corporate HQ campus locations. That's schedule info. So we can create Schedule section with that detail.
Benefits: we have benefits list.
Now we need to ensure we don't duplicate content. Overview already mentioned hybrid schedule and benefits; we might move those details to Benefits and Schedule sections, and keep About the role focusing on company description and role context.
Let's craft About the role: description of Enterprise Mobility, its brands, fleet size, revenue, locations, IT team role, hybrid work eligibility, location (Lakeside/Clayton). Not include benefits/hybrid schedule details (move to Benefits/Schedule). Also mention that we offer excellent package etc? That's benefits. So we keep About the role focusing on company description and team.
Now Benefits: list: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential.
Schedule: hybrid work schedule, ability to work from home, required in-person as needed at Lakeside and/or Clayton Corporate HQ campus locations in St. Louis, Missouri.
Now we need to ensure we don't include boilerplate like EEO etc. Already removed.
Now produce HTML fragment:
About the role
Enterprise Mobility is a leading provider of mobility solutions, owning and operating the Enterprise Rent-A-Car, National Car Rental and Alamo Rent A Car brands through its integrated global network of independent regional subsidiaries. Enterprise Mobility and its affiliates offer extensive car rental, carsharing, truck rental, fleet management, retail car sales, as well as travel management and other transportation services, to make travel easier and more convenient for customers. Privately held by the Taylor family of St. Louis, Enterprise Mobility together with its affiliate Enterprise Fleet Management manages a diverse fleet of 2.4 million vehicles and accounted for nearly $39 billion in revenue through a network of more than 9,500 fully-staffed neighborhood and airport rental locations in more than 90 countries and territories. At the center of it all, our dedicated IT teams innovate, design and develop the technology that is redefining how customers rent, buy and share vehicles from our family of brands. Here, you will be part of a diverse and talented team that creates and delivers powerful technology
- for each required bullet.
Required bullets:
- Must be presently authorized to work in the U.S. without a requirement for work authorization sponsorship by our company for this position now or in the future
- Must reside in St. Louis, Missouri, or immediate surrounding area
- 3+ years of software development experience using Java, Spring Framework, Spring Boot, and Spring WebFlux to build reactive, event-driven microservices leveraging Project Reactor (Mono/Flux) and non-blocking APIs.
- 2+ years experience in front-end frameworks including TypeScript, React(Hooks, Context API, Redux), component-driven architecture and styling technologies including SASS, LESS, and SCSS.
- 2+ years of experience creating and implementing SQL
- Strong knowledge of SOA (Service-Oriented Architecture), RESTful API design, and API consumption within React applications.
- Experience in Struts, Angular, and Postman preferred. (This is actually under Preferred? Wait it's in Required block? The text: "Experience in Struts, Angular, and Postman preferred." It appears under Required? Actually after "Strong knowledge of SOA..." then "Experience in Struts, Angular, and Postman preferred." That seems like a preferred item but placed in Required block. We'll treat as required? It says preferred, but it's in the Required block. Safer to treat as required? But we have a separate Preferred section later. We'll move this to Preferred.
- Experience building, deploying, and supporting Spring Boot microservices on AWS
- Must be committed to incorporating security into all decisions and daily job responsibilities
Now Preferred bullets:
- Bachelor's degree in Computer Science, Computer Information Systems, Management Information Systems, or related field
- Experience with Cloud technologies (AWS)
- Experience with frameworks such as Hibernate and Struts
- Experience with WebLogic
- Experience with Jenkins or other continuous integration tools
- Experience with Putty
- Experience with Splunk
- Experience with Artifactory
- Experience with JIRA, Confluence, and/or similar tool
- Experience with Cloud technologies (Azure, Terraform)
- Experience with Postman/SOAP UI
- Experience with Dynatrace
Also note "Experience with Cloud technologies (AWS)" appears twice? Actually appears in Required (Experience building, deploying, and supporting Spring Boot microservices on AWS) and Preferred (Experience with Cloud technologies (AWS)). We'll keep both.
Now Benefits: The overview mentions benefits: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential. Also hybrid work schedule eligibility. So we can put Benefits section with those items.
Pay: The posting mentions "market-competitive pay" but not specific numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "market-competitive pay" which is a statement about pay, albeit vague. Is that enough? The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "market-competitive pay" is not a specific number but it's a statement. Is that considered filler? It's vague but it's a statement about pay. The instruction says avoid filler like "commensurate with experience". "market-competitive pay" is similar vague. Might be considered filler. Safer to not create Pay section unless there is explicit number or range. Since they didn't give numbers, we should omit Pay section.
Schedule: The posting mentions hybrid work schedule, ability to work from home, also need to be in person as needed at Lakeside and/or Clayton Corporate HQ campus locations. That's schedule info. So we can create Schedule section with that detail.
Benefits: we have benefits list.
Now we need to ensure we don't duplicate content. Overview already mentioned hybrid schedule and benefits; we might move those details to Benefits and Schedule sections, and keep About the role focusing on company description and role context.
Let's craft About the role: description of Enterprise Mobility, its brands, fleet size, revenue, locations, IT team role, hybrid work eligibility, location (Lakeside/Clayton). Not include benefits/hybrid schedule details (move to Benefits/Schedule). Also mention that we offer excellent package etc? That's benefits. So we keep About the role focusing on company description and team.
Now Benefits: list: market-competitive pay, comprehensive healthcare packages, 401k matching & profit sharing, schedule flexibility, work from home opportunities, paid time off, organizational growth potential.
Schedule: hybrid work schedule, ability to work from home, required in-person as needed at Lakeside and/or Clayton Corporate HQ campus locations in St. Louis, Missouri.
Now we need to ensure we don't include boilerplate like EEO etc. Already removed.
Now produce HTML fragment:
- each.
Qualifications: The posting has "Qualifications Required:" and then list. Also "Preferred" bullet list. We need to decide whether to put under Requirements or Qualifications. The allowed headings include Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We already used Skills for KSAs. We could put required qualifications under "Requirements" and preferred under "Qualifications". Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have required qualifications and preferred qualifications. Could make two sections: Requirements (required) and Qualifications (preferred). That seems appropriate.
Thus: