Senior React Developer 668

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title heading. Must not include Job ID etc. Must preserve all substantive info, not invent. Remove boilerplate like EEO, legal, application instructions, etc. We need to parse the posting. Key content: - Intro: "Join Our Mission-Focused Team — This Position Is Eligible for a $25,000 Welcome Bonus for Qualified Candidates! Join a team that powers the business enterprise behind the mission. Freedom supports the sustainment, modernization, and transformation of more than 100 enterprise business systems that enable tens of thousands of government personnel, industry partners, and prospective employees worldwide. These mission-enabling applications support workforce management, finance, acquisitions, security processing, training, recruitment, logistics, program management, executive decision-making, and other critical business functions across multiple secure environments. We are seeking a Senior React Developer to join one of our Prime Contracts supporting the Government's Corporate Management Services (CMS) organization. Telework up to one day a week! In this role, you will help design, modernize, secure, and sustain the enterprise applications and platforms that keep the organization operating every day. Working alongside experts in software engineering, cloud computing, DevSecOps, systems engineering, user experience, and enterprise platforms, you'll help modernize legacy systems, automate business processes, integrate commercial technologies, and deliver innovative solutions that improve efficiency, reduce costs, and enhance the user experience. If you're looking for an opportunity where your work has broad enterprise impact, you'll find it here. Our diverse and growing team offers the chance to solve complex technical challenges, collaborate with talented professionals, and directly contribute to the technology and services that enable the Government's mission around the world." Then: "We are seeking a Full Stack Software Engineer with strong experience in React and Java to support the development and delivery of a modernized application. This role will play a key part in building a new capability while supporting the migration of a legacy system to a hybrid architecture leveraging Camunda and Pega workflow platforms. The ideal candidate is a hands-on developer who thrives in a fast-paced environment, can quickly understand existing systems, and is comfortable contributing across the full stack to deliver high-quality, scalable solutions. Pega is a leading enterprise application platform used by major government agencies and Fortune 500 organizations to build workflow-driven applications, automate complex business processes, and modernize legacy systems. Developers on this team work with a combination of visual application design, software engineering principles, API integrations, cloud technologies, and enterprise architecture patterns to rapidly deliver mission-critical solutions. Contribute to the development of a full-stack application using React (frontend) and Java/Spring Boot (backend), with a primary focus on delivering high-quality, scalable functionality. Build modern, responsive user interfaces in React and integrate them with robust backend services and APIs developed in Java. Support the migration of a legacy application to a modern architecture, refactoring existing functionality into React and Java-based services. Integrate application components with Camunda workflow services and interface with Pega-based workflows to enable end-to-end business process orchestration. Develop and optimize data interactions with an Oracle database, ensuring performance, reliability, and data integrity. Collaborate with cross-functional teams to translate requirements into technical solutions and ensure alignment across development, integration, and migration efforts. Participate in code reviews, testing, and debugging to deliver secure, maintainable, and high-quality code. Support deployments, troubleshoot issues, and contribute to improving system performance and stability across environments." Then required: "Required: TS/SCI with Full Scope Polygraph A bachelor's degree in a technical discipline and twelve (12) years' experience as a developer in programs and contracts of similar scope, type, and complexity is required. Sixteen (16) years' development experience may be substituted for a bachelor's degree Strong proficiency in React and modern JavaScript frameworks Strong experience with Java and Spring Boot Experience developing and integrating RESTful APIs Familiarity with Oracle databases and SQL Experience working in fast-paced, agile development environments Must be able to work during core hours of Monday-Friday 10am-2pm. Exceptions will be considered on a case-by-case basis" Desired: "Desired: A strong willingness to learn about COTS products and integrations, particularly with PEGA services. Enthusiasm for tackling new challenges while working in a collaborative, fast-paced environment. Experience working in an Agile Development environment Willingness to get relevant PEGA certification" Salary: "The estimated salary range for this position is between $200,000-$275,000 (annualized USD). This range reflects the typical pay for the role and is one part of the company's comprehensive compensation package. Actual salaries are influenced by several factors, such as location, the individual's education, skills, experience, and competencies, as well as contract affordability and organizational needs." Welcome Bonus: "This position is eligible for a $25,000 Welcome Bonus for qualified candidates. Bonus eligibility and payment terms apply." Benefits: "What's in It for You? Flexible work environment A team mentality – work with friendly, like-minded professionals Work with innovative, cutting edge technologies Enjoy Extremely Competitive Compensation And Benefits A work-life balance you can count on Opportunities to grow and advance your career on our dime The Benefits You Get with Freedom Amazing benefits including matching 401k, fully paid medical, and more Generous paid time off – including paid site closure days Competitive salary offerings Paid training and tuition reimbursement Referral bonuses Fully paid life and disability Annual logo wear allowance Company sponsored events (game nights, holiday party, summer party, happy hours)" Also "Interested in learning more about Freedom and our culture? Contact us today! We're constantly hosting hiring events in our office and elsewhere, to help you get a sense of what life is like at Freedom before joining the team." This is more like application instructions? Might be considered boilerplate? It's not strictly application instructions but maybe we can keep as part of About the role? Might be considered promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Contact us today!" and "hosting hiring events" could be considered application instructions? It's more like promotional. Might be okay to keep as part of About the role? But safer to omit as it's not substantive job description. However we need to preserve all substantive information; promotional content might be considered not essential but still part of posting. The instruction says remove application instructions. This is not exactly instructions to apply, but encouraging contact. Might be considered fluff. I'd lean to omit. We need sections: About the role (intro description), Responsibilities (list of duties), Requirements (required qualifications), Qualifications (maybe education/experience?), Skills (technical skills), Benefits, Pay, Schedule. We must not create sections with filler. So we need to see if we have content for each. Let's extract: About the role: Could be the introductory paragraphs describing mission, team, role overview. That's substantive. Responsibilities: The bullet list of duties: design, modernize, secure, sustain enterprise apps; modernize legacy systems; automate business processes; integrate commercial technologies; deliver innovative solutions; contribute to development of full-stack app using React and Java/Spring Boot; build modern responsive UIs in React; integrate with backend services; support migration of legacy app to modern architecture; refactor existing functionality into React and Java-based services; integrate with Camunda workflow services; interface with Pega-based workflows; develop and optimize data interactions with Oracle DB; collaborate with cross-functional teams; participate in code reviews, testing, debugging; support deployments, troubleshoot issues; contribute to improving system performance and stability. We can put these as

• . Requirements: Could be the required qualifications: TS/SCI with Full Scope Polygraph; bachelor's degree in technical discipline and 12 years experience; or 16 years experience may substitute for degree; strong proficiency in React and modern JS frameworks; strong experience with Java and Spring Boot; experience developing and integrating RESTful APIs; familiarity with Oracle databases and SQL; experience working in fast-paced agile dev environments; must be able to work core hours Mon-Fri 10am-2pm (exceptions case-by-case). That's required. Qualifications: Could be education/experience details? Might overlap with Requirements. But we can separate: Qualifications could be education (bachelor's degree) and experience (12 years) etc. However the instruction says prefer few substantive sections over many thin ones. Might combine Requirements and Qualifications? But they ask to use headings for sections like Requirements, Qualifications, Skills. We need to decide if we have distinct content for each. We have Required list (including clearance, degree/experience, technical skills, work hours). Desired list (willingness to learn COTS/PEGA, enthusiasm, Agile experience, willingness to get PEGA certification). Those could be Skills? Or Desired could be under Skills or Qualifications. Better: Use Requirements for mandatory items (clearance, degree/experience, technical proficiency, work hours). Use Skills for technical skills (React, Java/Spring Boot, REST APIs, Oracle DB, Agile). Use Qualifications for education/experience? But that duplicates. Alternatively: Use Requirements for clearance and degree/experience; Skills for technical skills; Qualifications for desired? Hmm. Let's think: The posting includes "Required:" block and "Desired:" block. So we can map Required to Requirements section, Desired to Skills or Qualifications? The Desired includes willingness to learn COTS/PEGA, enthusiasm, Agile experience, willingness to get PEGA certification. Those are more like soft skills or desired qualifications. Could go under Skills (maybe as desired skills) or Qualifications. But we also have explicit technical skills listed under Required: Strong proficiency in React, strong experience with Java/Spring Boot, experience developing RESTful APIs, familiarity with Oracle DB, experience in fast-paced agile environments. Those are technical skills. So we could put those under Skills. Thus: - About the role: intro paragraphs. - Responsibilities: list of duties. - Requirements: TS/SCI with Full Scope Polygraph; bachelor's degree in technical discipline and 12 years experience (or 16 years experience may substitute); must be able to work core hours Mon-Fri 10am-2pm (exceptions case-by-case). Possibly also include that it's a Senior React Developer/Full Stack Software Engineer? But that's role title. - Skills: Strong proficiency in React and modern JavaScript frameworks; Strong experience with Java and Spring Boot; Experience developing and integrating RESTful APIs; Familiarity with Oracle databases and SQL; Experience working in fast-paced, agile development environments; Desired: A strong willingness to learn about COTS products and integrations, particularly with PEGA services; Enthusiasm for tackling new challenges while working in a collaborative, fast-paced environment; Experience working in an Agile Development environment; Willingness to get relevant PEGA certification. But note that some of these overlap with Required technical skills. We could combine them: Required technical skills plus Desired soft skills. However we must not duplicate lines. We need to preserve all substantive info, but we can combine similar items without duplication. For example, "Experience working in fast-paced, agile development environments" appears both in Required and Desired? Actually Required includes "Experience working in fast-paced, agile development environments". Desired includes "Experience working in an Agile Development environment". That's essentially same. We should not duplicate. So we can include once under Skills. Similarly, "Strong proficiency in React and modern JavaScript frameworks" and "Strong experience with Java and Spring Boot" are Required. Desired includes willingness to learn COTS/PEGA etc. Thus Skills section can list: Strong proficiency in React and modern JavaScript frameworks; Strong experience with Java and Spring Boot; Experience developing and integrating RESTful APIs; Familiarity with Oracle databases and SQL; Experience working in fast-paced, agile development environments; Willingness to learn about COTS products and integrations, particularly with PEGA services;