Full Stack Software Engineer

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse. The posting includes: - Intro paragraph: "In a world of possibilities..." etc. That's about the company, maybe "About the role"? Actually "About the role" could be the description of role. The job description: "Parsons is looking for an amazingly talented Full Stack Software Engineer...". That's about the role. We'll put that in a

under

About the role

. - Responsibilities: The "What You'll Be Doing" bullet list. That's responsibilities. Use

• . - Required Skills: "What Required Skills You'll Bring" list. That's requirements/qualifications. Could be "Requirements" or "Qualifications". We'll decide: Use

  Requirements

  for required skills. Also maybe "Qualifications" for desired? But we have both required and desired. Could combine? The instruction: prefer few substantive sections over many thin ones. We could have one "Requirements" covering required and desired? But we need to preserve all info. Could have "Required Skills" and "Desired Skills" as sub-sections? But headings limited to given list: we can use Skills heading for both? Actually we have Skills as a possible heading. Could put all skills under

  Skills

  with sub-lists for required and desired. That might be okay. - Security Clearance Requirement: That's a requirement; could be part of Requirements. - Salary Range: That's Pay. So we need Pay section with salary range. - Benefits: The paragraph about benefits: medical, dental, vision, paid time off, 401(k), life insurance, flexible work schedules, holidays. That's Benefits. - Schedule: Not mentioned explicitly; maybe flexible work schedules mentioned under benefits. No explicit schedule. So we should not create Schedule section unless posting actually states them. It mentions flexible work schedules as benefit, not schedule. So we skip Schedule. - About the role: we have intro. - Responsibilities: we have. - Requirements/Qualifications: we have required skills, desired skills, security clearance, maybe education. - Skills: we could combine required and desired under Skills. But we need to avoid duplication. Let's structure:

  About the role

  Intro paragraph (the first paragraph up to "Imagine Next!"? Actually the intro includes motivational text. We'll include that as about the role.) Then maybe a second paragraph: "Parsons is looking for an amazingly talented Full Stack Software Engineer to join our team! In this role you will get to Develop and enhance complex software systems that directly support critical customer missions. We are building a pipeline of passionate engineers interested in a variety of impactful projects—if you thrive in dynamic environments and want to make a difference, we want to hear from you!" That's also about role. We'll combine. Then

  Responsibilities

  with ul list of the bullet points from "What You'll Be Doing". Need to preserve each line exactly. Then

  Skills

  with maybe two sub-lists: Required Skills and Desired Skills. But we cannot add extra headings not in list? We could use inside

  or just separate

  with headings? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings like

  but says use

  for section headings (list). It might be okay to use

  only for those sections; we could still use

  with bold text for Required vs Desired. Safer: we can have two

  each preceded by a

  Required Skills:

  etc. That's fine. Then

  Benefits

  with ul list of benefits. Then

  Pay

  with p containing salary range. We should not include Requirements/Qualifications separate if we put skills under Skills. But we have also education (Bachelors degree) and experience (12+ years) and security clearance. Those are not skills per se but qualifications. Could put them under Skills as well? Might be odd. Better to have a

  Requirements

  for required skills, education, experience, clearance. And

  Skills

  for desired skills? But we have both required and desired skills. Could split: Requirements = required skills + education + experience + clearance. Skills = desired skills. That seems reasonable. Thus sections: - About the role - Responsibilities - Requirements - Skills (desired) - Benefits - Pay Check if any other: maybe Qualifications not needed. Now ensure we don't include boilerplate: remove EEO, fraud warning, etc. Also remove "Imagine Next!"? That's part of intro; we can keep. Now craft HTML. We need to preserve all substantive information: ensure we don't lose any bullet. Let's extract bullet points. Responsibilities list from "What You'll Be Doing": - Design, develop, and enhance complex, full-stack software systems based on documented requirements. - Architect and implement scalable, maintainable front-end solutions using modern frameworks (React, Angular, Vue, etc.). - Translate UX/UI designs and prototypes into functional, responsive, and accessible interfaces. - Contribute to backend development using technologies such as Java Spring, Node.js, Python, or Django. - Participate in the full software development lifecycle: requirements analysis, design, development, testing, deployment, and maintenance. - Apply modern engineering practices including version control (Git), code reviews, automated testing, and CI/CD pipelines. - Debug and troubleshoot UI and full-stack issues, performing root-cause analysis and driving fixes. - Continuously improve user experience and system performance by identifying enhancements and optimizations. - Collaborate closely with product owners, designers, and other engineers to refine requirements and deliver incremental value. Make sure each is a
  • . Required Skills list from "What Required Skills You'll Bring": - 12+ years of software engineering experience - Bachelors degree in Computer Science or related discipline - Proficiency with front-end JavaScript frameworks (e.g., Angular, React, or Vue) - Experience with back-end technologies (e.g., Java Spring, Node.js, Python, Django) - Strong understanding of software development methodologies (Agile/Scrum, DevOps, etc.) - Familiarity with version control systems (Git) and CI/CD pipelines - Excellent problem-solving, communication, and collaboration skills Also Security Clearance Requirement: "An active Top Secret SCI w/Polygraph security clearance is required for this position." This is a requirement. We'll include that as a
  • under Requirements. Desired Skills list from "What Desired Skills You'll Bring": - Experience with databases and SQL (MongoDB, MySQL, Oracle) - Experience with containerization technologies (Docker, Kubernetes) - AWS or other cloud platform experience - Experience with UI libraries, reusable components, and state management - Familiarity with Linux/Ubuntu environments - Experience with messaging systems (JMS, Kafka) - Knowledge of accessibility standards and best practices - Experience with Spring Boot, Spring MVC, Spring Data, Spring Security - Familiarity with build tools (Maven, Gradle) and DevOps practices (GitLab CI/CD) Now Benefits: "medical, dental, vision, paid time off, 401(k), life insurance, flexible work schedules, and holidays". We'll make each as li. Pay: "Salary Range: $125,100.00 - $225,200.00". We'll put in p. Now About the role: combine the intro paragraphs. Intro: "In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible." Then second: "Parsons is looking for an amazingly talented Full Stack Software Engineer to join our team! In this role you will get to Develop and enhance complex software systems that directly support critical customer missions. We are building a pipeline of passionate engineers interested in a variety of impactful projects—if you thrive in dynamic environments and want to make a difference, we want to hear from you!" We'll combine into one or two p tags. Use

    for prose. Now ensure we don't include any boilerplate like "Parsons is an equal opportunity employer..." etc. Remove. Now output HTML fragment. Let's craft:

    About the role

    In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible.

    Parsons is looking for an amazingly talented Full Stack Software Engineer to join our team! In this role you will get to Develop and enhance complex software systems that directly support critical customer missions. We are building a pipeline of passionate engineers interested in a variety of impactful projects—if you thrive in dynamic environments and want to make a difference, we want to hear from you!

    Responsibilities

    • Design, develop, and enhance complex, full-stack software systems based on documented requirements.
    • Architect and implement scalable, maintainable front-end solutions using modern frameworks (React, Angular, Vue, etc.).
    • Translate UX/UI designs and prototypes into functional, responsive, and accessible interfaces.
    • Contribute to backend development using technologies such as Java Spring, Node.js, Python, or Django.
    • Participate in the full software development lifecycle: requirements analysis, design, development, testing, deployment, and maintenance.
    • Apply modern engineering practices including version control (Git), code reviews, automated testing, and CI/CD pipelines.
    • Debug and troubleshoot UI and full-stack issues, performing root-cause analysis and driving fixes.
    • Continuously improve user experience and system performance by identifying enhancements and optimizations.
    • Collaborate closely with product owners, designers, and other engineers to refine requirements and deliver incremental value.

    Requirements

    • 12+ years of software engineering experience
    • Bachelors degree in Computer Science or related discipline
    • Proficiency with front-end JavaScript frameworks (e.g., Angular, React, or Vue)
    • Experience with back-end technologies (e.g., Java Spring, Node.js, Python, Django)
    • Strong understanding of software development methodologies (Agile/Scrum, DevOps, etc.)
    • Familiarity with version control systems (Git) and CI/CD pipelines
    • Excellent problem-solving, communication, and collaboration skills
    • An active Top Secret SCI w/Polygraph security clearance is required for this position.

    Skills

    • Experience with databases and SQL (MongoDB, MySQL, Oracle)
    • Experience with containerization technologies (Docker, Kubernetes)
    • AWS or other cloud platform experience
    • Experience with UI libraries, reusable components, and state management
    • Familiarity with Linux/Ubuntu environments
    • Experience with messaging