Lead Java Full Stack Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes: "Job Summary" (prose), "Required Qualifications", "Preferred Qualifications". Also includes Salary Range, Location, Position Type, Experience Required, Sponsorship. Those are metadata; we should fold minor metadata into a short

or drop it. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a paragraph with location, remote, salary range, etc. Also we need sections only when posting has real specific content. So we can have sections: About the role (maybe from Job Summary), Responsibilities (maybe from Job Summary? Actually responsibilities are described in Job Summary: architect, design, develop, maintain, end-to-end engineering lifecycle, etc. Could be a Responsibilities section). Requirements (Required Qualifications). Qualifications (maybe Preferred Qualifications). Benefits? Not given. Pay? Salary range given, so we can include Pay section. Schedule? Not given (full-time). Could include Schedule? The posting says Position Type: Full-time, Direct W2. That's schedule info. We could include Schedule section with "Full-time, Direct W2". But we need to avoid filler like "not specified". It's specified, so we can include. Benefits: not mentioned, so omit. Pay: include salary range. Also we need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from required qualifications, preferred qualifications, job summary, salary, location, sponsorship, etc. We can embed sponsorship info in a paragraph. We must remove boilerplate: EEO statement, application instructions (How to Apply), powered by JazzHR, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  Location: 100% Remote (U.S.) | Position Type: Full-time, Direct W2 | Salary Range: $80,000–$100,000 Annually | Experience Required: 6+ years | Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.

  Then sections:

  About the role

  We are seeking an accomplished Lead Java Full Stack Engineer to architect, design, develop, and maintain enterprise-grade web applications and distributed systems that operate at significant scale and across multiple business domains. In this role you will be responsible for the end-to-end engineering lifecycle, from translating business requirements into robust technical designs, to writing production-quality code, to deploying cloud-native services and supporting them through their full operational lifespan. You will work closely with product managers, architects, DevOps engineers, and fellow developers in an Agile environment to deliver high-quality, secure, and performant applications that directly support strategic business outcomes.

  Maybe we can split responsibilities into a list? The job summary includes responsibilities; we could make a Responsibilities section with
  • . But we need to decide: The instruction says use
    • for any list of duties/requirements/benefits. If we have a list, we should use that. The job summary is prose; we could keep as

      . Could also extract duties into list but that might be summarizing. Better to keep as prose. Then

      Responsibilities

      maybe not needed if we already covered in About the role. But we could separate: About the role (brief) and Responsibilities (list). However we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine About the role and Responsibilities into one section "About the role" with prose that includes responsibilities. That's fine. Then

      Requirements

      with
      • for each required qualification. Then

        Preferred Qualifications

        with
        • for each preferred. Then

          Pay

          with

          Salary Range: $80,000–$100,000 Annually

          (but we already included salary in metadata paragraph; we could still include Pay section but risk duplication. The instruction: "include a section ONLY when the posting has real, specific content for it". Salary is specific; we could include Pay section. But we already included salary in metadata paragraph; we could drop metadata paragraph and instead have separate sections for Location, Schedule, Pay, Sponsorship? However they said fold minor metadata into a short

          or drop it. So we could have a short paragraph with location, position type, sponsorship, and then separate Pay section. That seems okay. Let's craft:

          Location: 100% Remote (U.S.) | Position Type: Full-time, Direct W2 | Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.

          About the role

          We are seeking an accomplished Lead Java Full Stack Engineer to architect, design, develop, and maintain enterprise-grade web applications and distributed systems that operate at significant scale and across multiple business domains. In this role you will be responsible for the end-to-end engineering lifecycle, from translating business requirements into robust technical designs, to writing production-quality code, to deploying cloud-native services and supporting them through their full operational lifespan. You will work closely with product managers, architects, DevOps engineers, and fellow developers in an Agile environment to deliver high-quality, secure, and performant applications that directly support strategic business outcomes.

          Requirements

          • Bachelor’s degree in Computer Science, Engineering, or a closely related technical discipline
          • Five or more years of professional software development experience building production-grade enterprise applications
          • Strong, demonstrable understanding of data structures, algorithms, computational complexity, and end-to-end system design principles
          • Advanced working knowledge of Java (versions 11 and 17), the Spring Boot framework, and the design of clean, idiomatic RESTful APIs
          • Hands-on, production-level experience designing and operating microservices architectures, including service decomposition, inter-service communication, and observability patterns
          • Proven experience developing front-end applications using React, with working familiarity in Angular or Vue considered a strong plus
          • Strong SQL skills and meaningful experience working with relational databases such as PostgreSQL, MySQL, Oracle, or SQL Server, including query tuning and schema design
          • Solid experience with CI/CD tooling and Git-based version control workflows, including branching strategies, code review practices, and release management
          • Hands-on experience deploying applications to at least one major cloud platform (AWS, Azure, or GCP), including familiarity with managed services, networking, and identity primitives
          • Strong debugging, troubleshooting, and root-cause analysis skills, with the discipline to investigate problems methodically and document findings clearly

          Preferred Qualifications

          • Experience designing and operating event-driven architectures using Kafka, RabbitMQ, or equivalent streaming platforms
          • Familiarity with containerization and orchestration using Docker and Kubernetes in production environments
          • Exposure to distributed system design principles such as eventual consistency, CAP trade-offs, idempotency, and saga patterns
          • Experience writing automation tests using modern frameworks and contributing to test-driven and behavior-driven development practices

          Pay

          Salary Range: $80,000–$100,000 Annually

          We could also add Schedule section: but we already have position type in metadata paragraph. Could add Schedule section with "Full-time, Direct W2". But that would be thin. The instruction: prefer few substantive sections over many thin ones. So we keep schedule in metadata paragraph. We must not include any boilerplate like EEO, How to Apply, etc. Check that we preserved all substantive info: job summary, responsibilities, required qualifications, preferred qualifications, salary, location, position type, sponsorship, experience required (6+ years) - we included experience required? Actually we didn't explicitly mention "Experience Required: 6+ years". We have "Five or more years of professional software development experience building production-grade enterprise applications" which is similar but not exactly 6+ years. The posting says Experience Required: 6+ years. The required qualifications list includes "Five or more years of professional software development experience". That's slightly different. We should include the exact experience requirement as well. Could add a line in metadata paragraph: "Experience Required: 6+ years". Or we could adjust required qualifications to reflect 6+ years. But we must not invent or summarize away detail. The required qualifications says "Five or more years". The experience required says "6+ years". Both are present; we should include both. So we need to include "Experience Required: 6+ years" somewhere. We can add to metadata paragraph. Thus metadata paragraph: "Location: 100% Remote (U.S.) | Position Type: Full-time, Direct W2 | Experience Required: 6+ years | Salary Range: $80,000–$100,000 Annually | Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Now we have all. Check for any other substantive info: "Job Title: Lead Java Full Stack Engineer" - we are not to repeat as heading. Already not. "Job Summary" we used. "Required Qualifications" we used. "Preferred Qualifications" we used. "Sponsorship" we included. "Position Type" included. "Location" included. "Salary Range" included in Pay section and also metadata? We have salary in metadata paragraph and also Pay section. That's duplication. Better to not duplicate. We could drop salary from metadata paragraph and keep only in Pay section. But metadata paragraph is for minor metadata; salary is not minor, it's specific. So we should have Pay section and not repeat salary in metadata. So adjust metadata paragraph to exclude salary. Thus metadata paragraph: "Location: 100% Remote (U.S.) | Position Type: Full-time, Direct W2 | Experience Required: 6+ years | Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Pay section: salary range. Now check if we missed any other specifics: "Direct W2" included. Good. Check for any other specifics like "cloud, AI, data, and enterprise solutions" in company description. That's part of intro; we could include in About the role? The intro: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States." That's substantive. Should we preserve? Yes, we should preserve all substantive information. We could add a brief intro paragraph before About the role, maybe as part of About the role or a separate section "About the company". But we have no heading for company; we could incorporate into About the role paragraph. However the instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have an "About the company" section? Not listed but could be used if we want.