Full Stack Developer

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. Only include sections that have real specific content. The posting includes: description of role, responsibilities list, qualifications list, salary range $110k - $150k, physical demands (maybe not a section). Also mentions "Must adhere to 8570.01M CWF Requirements - IAT Level II", security clearance, US citizenship, etc. Also mentions "What Your Experience Working For Us Will Be Like" (culture) and "About Synectic Solutions, Inc." (company description). Also "Ready to apply?" etc which is application instruction - we should remove. Also "Powered by JazzHR ..." remove. We need to decide sections: About the role (maybe the introductory paragraph). Responsibilities (list). Qualifications (list). Skills (maybe list of technical skills). Benefits (none explicit). Pay (salary range). Schedule (none). Could also include "Requirements" maybe combine with qualifications? The instruction says use headings for those categories if content exists. We have qualifications (education/experience, clearance, etc). We have skills (technical). We have pay. We have responsibilities. We have about the role (intro). We could also include "Requirements" maybe duplicate of qualifications; but we can include both if distinct. The posting has "Qualifications:" section with education/experience, clearance, etc. Also earlier "Must adhere to 8570.01M CWF Requirements - IAT Level II" and security clearance etc. That's qualifications. Skills: list of languages, frameworks, databases, etc. So we can have sections: About the role, Responsibilities, Qualifications, Skills, Pay. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities and qualifications and skills. We need to format lists with

• . For prose use

  . We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove "Ready to apply? If this job sounds like a fit for you, then click on the ‘apply’ button below. Good luck!" and "Powered by JazzHR hskiqlTPVh". Also remove "What Your Experience Working For Us Will Be Like" maybe that's culture description; could be considered substantive? It's about company culture; maybe we can include under About the role or a separate section? There's no heading for culture; but we could incorporate into About the role paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we can merge culture into About the role. Also "About Synectic Solutions, Inc. (SSI)" is company description; could be part of About the role or separate section? There's no heading for About the company; but we could include in About the role as well. However we must not invent sections; we can include a paragraph about the company under About the role. Thus About the role paragraph will include: Synectic Solutions seeking Full Stack Developer to join team supporting Program Office for NSWC Corona in Norco, California. The Full Stack Developer will work directly with client analyzing complex and unique technical support assignments and lead or collaborate with other system administrators, cybersecurity personnel, and program analysts within an agile environment. Also include culture description and company overview. Now Responsibilities: list all items after "Responsibilities:" until before "Qualifications:". We need to capture each responsibility sentence. The text after "Responsibilities:" is a long sentence with many items separated by commas and maybe line breaks. We need to split into list items. Let's extract: - Work with development teams and product managers to ideate software solutions - Design client-side and server-side architecture - Build the front-end of applications through appealing visual design - Develop and manage well-functioning databases and applications - Write effective APIs - Test software to ensure responsiveness and efficiency - Troubleshoot, debug and upgrade software - Create security and data protection settings - Build features and applications with a mobile responsive design - Write technical documentation - Work with data scientists and analysts to improve software - Maintain, troubleshoot, and implement network security tools including firewalls, anti-virus, and intrusion detection services - Answering questions about installation, operation, configuration, and customization - Applying advanced diagnostic techniques to identify problems, investigate causes and recommend solutions to correct common failures - Specific support consists of troubleshooting hardware, software, and network related issues encountered by users - Installation of new software releases, system upgrades, evaluation and installation of patches and to resolve software related issues and Information Assurance Vulnerabilities (IAVs) - Assist with the maintenance and monitoring of the organizational mailbox to ensure that all users receive timely support in response to their requests for assistance - Maintain and develop IT related procedures required to support the organization - Support also includes working with the organizations Information Systems Security Officer (ISSO) for achieving system accreditation - Provide recommendation to future IT needs of the organization - Maintain data files and monitors system configuration to ensure data integrity - Assist in the preparation of a monthly progress and status report We need to ensure each is a separate

• . Some start with verb forms; keep as is. Now Qualifications: after "Qualifications:" until before "$110k - $150k". The text: "A high school degree, or a GED, and more than seven (7) years of relevant Full Stack Development experience, OR a bachelor's degree in a relevant field and four (4) years of relevant Full Stack Development experience, A master's degree in a relevant field and two (2) years of relevant Full Stack Development experience, Must adhere to 8570.01M CWF Requirements - IAT Level II SECURITY CLEARANCE REQUIREMENTS: Must currently hold a Secret Security Clearance. US Citizenship is a requirement for Secret clearance at this location Proven experience as a Full Stack Developer or similar role Experience developing desktop and mobile applications Familiarity with common stacks Knowledge of multiple front-end languages and libraries (e.g. HTML/ CSS, JavaScript, XML, jQuery) Knowledge of multiple back-end languages (e.g. C#, Java, Python) and JavaScript frameworks (e.g. Angular, React, Node.js) Familiarity with databases (e.g. MySQL, MongoDB), web servers (e.g. Apache) and UI/UX design" We need to split into list items. However some items are more like requirements (education/experience) and some are skills. But we have separate Skills section later; but the qualifications list includes also technical skills. To avoid duplication, we could treat the qualifications section as education/experience/clearance etc, and skills section as technical skills. However the instruction says we must preserve all substantive information; we can split but ensure not to duplicate. Let's parse: Qualifications bullet points: - A high school degree, or a GED, and more than seven (7) years of relevant Full Stack Development experience - OR a bachelor's degree in a relevant field and four (4) years of relevant Full Stack Development experience - A master's degree in a relevant field and two (2) years of relevant Full Stack Development experience - Must adhere to 8570.01M CWF Requirements - IAT Level II - Must currently hold a Secret Security Clearance - US Citizenship is a requirement for Secret clearance at this location - Proven experience as a Full Stack Developer or similar role - Experience developing desktop and mobile applications - Familiarity with common stacks - Knowledge of multiple front-end languages and libraries (e.g. HTML/ CSS, JavaScript, XML, jQuery) - Knowledge of multiple back-end languages (e.g. C#, Java, Python) and JavaScript frameworks (e.g. Angular, React, Node.js) - Familiarity with databases (e.g. MySQL, MongoDB), web servers (e.g. Apache) and UI/UX design But many of those are skills; we could still include them under Qualifications, but then Skills section would be duplicate. Better to have Qualifications cover education/experience/clearance etc, and Skills cover technical skills. However the posting lumps them together; we need to decide. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect Qualifications and Skills separate. So we should split accordingly. Thus Qualifications section will contain education/experience, clearance, citizenship, proven experience as Full Stack Developer, experience developing desktop/mobile apps (maybe that's skill but could stay). But to avoid duplication, we can put the technical skills under Skills. Thus Qualifications items: - A high school degree, or a GED, and more than seven (7) years of relevant Full Stack Development experience - OR a bachelor's degree in a relevant field and four (4) years of relevant Full Stack Development experience - A master's degree in a relevant field and two (2) years of relevant Full Stack Development experience - Must adhere to 8570.01M CWF Requirements - IAT Level II - Must currently hold a Secret Security Clearance - US Citizenship is a requirement for Secret clearance at this location - Proven experience as a Full Stack Developer or similar role - Experience developing desktop and mobile applications Now Skills items: - Familiarity with common stacks - Knowledge of multiple front-end languages and libraries (e.g. HTML/ CSS, JavaScript, XML, jQuery) - Knowledge of multiple back-end languages (e.g. C#, Java, Python) and JavaScript frameworks (e.g. Angular, React, Node.js) - Familiarity with databases (e.g. MySQL, MongoDB), web servers (e.g. Apache) and UI/UX design Now Pay: "$110k - $150k". We'll put under Pay heading as a

  maybe. Schedule: none. Benefits: none. Now About the role paragraph: combine intro, client work, culture, company overview. Let's craft:

  Synectic Solutions is seeking a Full Stack Developer to join our team supporting the Program Office for NSWC Corona in Norco, California. The Full Stack Developer will work directly with the client analyzing complex and unique technical support assignments and lead or collaborate with other system administrators, cybersecurity personnel, and program analysts within an agile environment. Synectic Solutions, Inc. (SSI) is an award‑winning, 20‑year government contracting agency focused on logistics, engineering, management, and information technology. SSI is a growing organization committed to exceeding customer expectations, continually improving all products, services, and processes, and performing all work with the highest standards and ethics. Employees describe SSI as a great place to work with an upbeat and positive culture, continuously improving performance to enhance the mission of the agencies served while expanding opportunities for employees and the company.

  We must ensure we didn't miss any substantive info: The posting also mentions "Physical Demands: Must be able to lift up to 10-25 pounds, stand and walk for prolonged amounts of time, twist, bend and squat periodically." This is substantive; we need to include it somewhere. There's no heading for Physical Demands; but we could add a section maybe "Physical Demands" but not in allowed headings list. The instruction says use those headings for section headings; but we could still include as a

  under About the role or maybe under a generic section? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings if needed, but they said "e