FS Java Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. We need to parse the job description. Key parts: Job#: 3052501 (metadata, drop) Job Description: Full Stack Developer – Recall Suite Applications (title, not needed as heading) Location: Hybrid (4 days onsite) 3 Month Contract Position Overview: paragraph about FCSD. Key Responsibilities: list bullet points. Required Qualifications: includes Education, Experience, etc. Technical Skills: many subpoints. Professional Competencies: list. Required Skills: list. Preferred Skills: list. Additional Information: Hybrid work schedule required. 4 days onsite per week. Everforth Apex description, benefits overview, etc. We need to extract substantive content for sections. We need to decide which sections to include: About the role (position overview), Responsibilities (Key Responsibilities), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Education?), Skills (Technical Skills + Required Skills + Preferred Skills?), Benefits (Everforth Apex Benefits Overview), Pay (not mentioned), Schedule (Hybrid work schedule required. 4 days onsite per week). No explicit pay. We must not create sections with placeholder like "not specified". So omit Pay if not present. We need to include Schedule section because we have specific schedule: Hybrid work schedule required. 4 days onsite per week. Also mention 3 Month Contract? That's contract length; maybe include in About the role? Could be part of schedule? Probably schedule section includes hybrid and onsite days. Contract length maybe part of About the role. We need to preserve all substantive info; not invent or summarize away detail. So we must keep details like "3 Month Contract". Where to put? Could be in About the role paragraph. We need to avoid duplication. We need to format using

for section headings,

• for lists,

  for prose. We must not repeat job title as heading. We must not put Job ID as heading. We must drop cookie/navigation/legal/EEO etc. So remove all equal opportunity statements, privacy policy, etc. We need to keep benefits overview: medical, dental, vision, life, disability, other insurance, ESPP, 401K, HSA, SupportLinc EAP, corporate discount savings program, on-demand training, certification prep, library, certification discounts, perks to associations (CompTIA, IIBA), dedicated customer service team, certified Career Coach, Welcome Packet. We need to keep schedule: Hybrid work schedule required. 4 days onsite per week. We need to keep contract length: 3 Month Contract. We need to keep location: Hybrid (4 days onsite). Already schedule. We need to keep position overview paragraph. We need to keep responsibilities list. We need to keep required qualifications: Education, Experience (5+ years progressive experience, etc), plus subpoints. We need to keep technical skills list. We need to keep professional competencies. We need to keep required skills (maybe duplicate of required qualifications? but we keep as Skills section maybe). We need to keep preferred skills. We need to avoid duplication: maybe combine Required Qualifications and Required Skills into Requirements and Skills sections. Let's design sections: - About the role: includes Position Overview, contract length, location? Could mention Hybrid (4 days onsite) 3 Month Contract. - Responsibilities: Key Responsibilities list. - Requirements: Education + Experience (maybe combine Required Qualifications). Could also include Required Skills? But we have Skills section separate. - Qualifications: maybe Education only? But we could skip Qualifications if we put education in Requirements. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We can decide to include Requirements (education+experience), Qualifications (maybe certifications? none), Skills (technical + required + preferred), Benefits, Schedule. We need to avoid thin sections. So maybe combine Education and Experience into Requirements, and put Technical Skills etc into Skills. Qualifications maybe not needed if no specific qualifications beyond education/experience. Could omit. Let's see if there are any specific qualifications like certifications? Not mentioned. So we can omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Now we need to extract content. About the role: Should include position overview paragraph plus contract length and location. Position Overview paragraph: "Ford Customer Service Division (FCSD) is committed to providing customers with an "Always On" experience. Our mission is to get customers back on the road in the shortest possible time. FCSD Tech delivers world-class software that: Dealers use to diagnose, repair, and service vehicles.Customers use for a seamless service experience.Ford enterprise teams use to operate a highly profitable, critical, and complex Parts & Service business. FCSD is a true one-stop shop, offering comprehensive diagnostics, repair, and service capabilities for a full portfolio of electrified, hybrid, and internal combustion vehicles globally. We are seeking a Full Stack Developer to join the Recall Suite Applications team and contribute to the design, development, testing, and deployment of scalable, cloud-native solutions." We also have location: Hybrid (4 days onsite) 3 Month Contract. Could embed as sentence: "This is a hybrid position requiring 4 days onsite per week, with a 3‑month contract." We'll keep that. Responsibilities: list bullet points from Key Responsibilities. Let's extract each bullet: - Serve as a core member of an engineering team designing and developing web services, web applications, APIs, and microservices. - Collaborate with product teams on integrations, testing, and deployments. - Translate business requirements into detailed technical specifications. - Ensure software engineering excellence through the adoption of best practices and quality standards. - Partner with other product teams to: - Reduce complexity across products and product lines. - Enhance interoperability between services. - Drive key architecture and design decisions across the portfolio. - Innovate and operate with an iterative, agile, and user-centric mindset. - Communicate effectively with team members and internal/external stakeholders. - Demonstrate engineering excellence through: - Active coding and development. - Pair programming and mob programming. - Code reviews and architecture reviews. - Work effectively with technical specialists, Product Managers, UX/UI Designers, and business partners. - Utilize Agile methodologies and tools, including JIRA, backlogs, iterations, and user stories. Note there is some nesting; we can flatten or keep subbullets? The instruction: use

  • for any list of duties/requirements/benefits. Could nest but simpler to keep flat list items; we can include subpoints as separate
  • items. We'll produce a flat list. Requirements: Education and Experience. Education: "Bachelor's Degree in Computer Science, Engineering, or a related field, or equivalent work experience." Experience: "5+ years of progressive experience in Software Engineering, Architecture, and Agile frameworks. 5+ years of experience with: Core Java Spring Boot React.js and/or Angular 3+ years of experience with modern databases, including: Relational databases Non-relational (NoSQL) databases 2+ years of experience developing and deploying applications to cloud platforms such as: Google Cloud Platform (GCP) Amazon Web Services (AWS) Microsoft Azure Experience with API design, development, and implementation. Experience collaborating with engineers, designers, and product owners. Experience working with diverse and global teams." We can break into list items. Skills: Technical Skills + Required Skills + Preferred Skills. Technical Skills list includes many items under categories: Software Development, Cloud & DevOps, Testing & Code Quality, Professional Competencies (but we already have separate). We'll combine. Let's extract Technical Skills bullet points: Software Development: - Deep understanding of Object-Oriented Design (OOD) principles. - Demonstrated experience developing API-based solutions. - Familiarity with eXtreme Programming (XP) practices, including: - Pair Programming - Mob Programming - Test-First Development - Test-Driven Development (TDD) Cloud & DevOps: - Experience with Continuous Integration/Continuous Delivery (CI/CD) tools and pipelines, including: Tekton, Jenkins, Terraform, SonarQube, Maven, Gradle, GitHub Actions, Apigee X - Strong understanding of cloud services and platform technologies. Testing & Code Quality: - Test-Driven Development Proven experience using Test-Driven Development (TDD) methodologies. - Front-End Testing Frameworks Experience with: Jest, React Testing Library, Cypress, Playwright - Back-End Testing Frameworks Experience with: JUnit 5, Mockito, TestContainers, Spring Boot Test - Code Quality & Best Practices Strong understanding of Clean Code principles. - Experience with software design patterns, including: SOLID Principles, Domain-Driven Design (DDD) - Proficiency with code quality and static analysis tools, including: SonarQube, ESLint, Prettier, Checkstyle - Understanding of refactoring techniques and legacy code modernization. Professional Competencies (maybe part of Skills): - Proven ability to work effectively within diverse, global teams. - Strong personal presence and ability to resolve complex technical concerns. - Excellent communication skills with the ability to adapt messaging to different audiences. - Ability to collaborate effectively and navigate complex decision-making in a rapidly changing environment. Required Skills list: - 5+ years of experience with Core Java, Spring Boot, and React.js/Angular. - 3+ years of experience with modern relational and non-relational databases. - 2+ years of cloud development and deployment experience using GCP, AWS, or Azure. - Experience with CI/CD tools and pipelines including Tekton, Jenkins, Terraform, SonarQube, Maven, Gradle, GitHub Actions, and Apigee X. - Experience collaborating with engineers, designers, and product owners. - Strong communication and interpersonal skills. Preferred Skills list: - Experience designing and developing web services, web applications, APIs, and microservices. - Experience collaborating across product teams on integrations, testing, and deployments. - Strong ability to convert business requirements into technical solutions. - Proven track record of driving software engineering best practices and quality initiatives. - Experience making architecture and design decisions across product portfolios. - Agile, iterative, and user-centered development mindset. - Experience with JIRA, backlogs, iterations, and user stories. - Strong collaboration skills with Product Managers, UX/UI Designers, technical specialists, and business stakeholders. - Deep understanding of Object-Oriented Design principles. - Familiarity with XP methodologies including Pair Programming, Mob Programming, and TDD. We need to avoid duplication; but we can keep all as they are substantive. Some overlap but okay. We'll output Skills section with a combined list (maybe categorize but not required). We'll just list all unique items; but to preserve all substantive information, we should not omit any. Duplication is okay but we could keep as is. Better to keep as separate subsections? But we only have Skills heading; we can include multiple
    maybe? The instruction: use
    • for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. We could have separate
      for Technical Skills, Required Skills, Preferred Skills. That preserves all. We'll do that. Benefits: Everforth Apex Benefits Overview paragraph. Extract: "Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance