Senior Full Stack Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. Key parts: - Job#: 3053660 (metadata, drop) - Job Description: Senior Full Stack Developer (title, not heading) - Location: Jersey City, NJ/Addison, TX (Hybrid) - Employment Type: Contract - Contract Duration: 12 Months - Role Overview: paragraph. - Key Responsibilities: list items. - Required Qualifications: includes Experience, Technical Skills, Professional Skills. - Preferred Qualifications: list. - Then company description Everforth Apex ... benefits overview etc. - Benefits: described. - Pay: not mentioned. - Schedule: not mentioned (maybe hybrid location but not schedule). So we should not include Pay or Schedule sections. We need sections: About the role (maybe from Role Overview). Responsibilities (Key Responsibilities). Requirements (maybe combine Required Qualifications? but we have separate sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: Role Overview paragraph. - Responsibilities: Key Responsibilities list. - Requirements: maybe the "Experience: A minimum of 10 years..."? Or could be "Required Qualifications" as Requirements. - Qualifications: maybe "Preferred Qualifications". - Skills: maybe technical skills list? But we already have technical skills under Required Qualifications. Could separate: Skills heading for technical skills list. However we must not create thin sections. We need to decide. We have content: Required Qualifications includes Experience, Technical Skills, Professional Skills. Preferred Qualifications list. We could treat: - About the role: Role Overview. - Responsibilities: Key Responsibilities. - Requirements: Experience (minimum 10 years) maybe plus location/contract? But location is metadata; we could include location in About the role? Might be better to put location in About the role paragraph? The instruction: do not repeat job title as heading, but we can include location etc in a short p. We could have a short p for metadata: Location, Employment Type, Contract Duration. But they said fold minor metadata into a short

or drop it. So we can include a p after About the role maybe. But we need to avoid creating sections with filler. So we will include:

About the role

Senior Full Stack Developer position located in Jersey City, NJ/Addison, TX (Hybrid). Contract role for 12 months.

Role Overview: We are seeking a Senior Full Stack Developer with at least 10 years of experience, including work within the financial sector. The ideal candidate will possess strong communication and delivery skills. This role requires a working knowledge of GIT or similar source code repositories, as well as experience with continuous build and deployment strategies using Jenkins and Ansible.

But we must not repeat the job title as heading; we can still mention it in paragraph. Then Responsibilities:

Responsibilities

• Contribute to story refinement and defining requirements.
• Participate in and guide the team in estimating work necessary to realize a story or requirement through the delivery lifecycle.
• Perform proof-of-concept work as necessary to mitigate risk or implement new ideas.
• Code solutions and perform unit tests to deliver requirements per the defined acceptance criteria and compliance standards.
• Utilize multiple architectural components (data, application, business) in the design and development of client requirements.
• Assist the team with resolving technical complexities involved in realizing story work.

Then Requirements: maybe the "Experience: A minimum of 10 years of professional experience is required." plus maybe "Experience within the financial sector"? Actually that was in Role Overview. But we can include. We could also include "Working knowledge of GIT or similar source code repositories, experience with continuous build and deployment strategies using Jenkins and Ansible." but those were in Role Overview. Might duplicate. Better to put Requirements as the mandatory experience and maybe location/contract? But we already put location in About the role. Thus Requirements:

A minimum of 10 years of professional experience is required.

But that seems thin. However we could combine Experience and maybe "Experience within the financial sector" as part of Requirements. That is from Role Overview but we could move. But we must preserve all substantive info; we can't lose the financial sector experience mention. So we need to include that somewhere. We could include in About the role paragraph: "Seeking a Senior Full Stack Developer with at least 10 years of experience, including work within the financial sector." Thus Requirements could be just the 10 years requirement. But maybe better to have Requirements: "Minimum 10 years professional experience, including financial sector experience." That's still thin but okay. Qualifications: Preferred Qualifications list. Skills: Technical skills list from Required Qualifications: Core Java, web services (REST/SOAP), relational and non-relational databases, ETL (Informatica), JavaScript, Relational DBs (Oracle/SQL Server), ASP MVC, .Net Core, WCF, building distributed scalable complex services and robust microservices, proficiency with RedHat OpenShift. Also professional skills: analytical/problem-solving, organizational/communication, team-oriented. We could split: Skills heading for technical skills, and maybe Professional Skills under Qualifications? But we already have Qualifications for preferred. Could also have Skills for both technical and professional. Given instruction to prefer few substantive sections over many thin ones, we could combine Technical Skills and Professional Skills under Skills heading. Thus:

Skills

• Core Java
• Experience with web services development, including REST and SOAP interfaces
• Experience with relational and non-relational databases, including ETL processes (e.g., Informatica)
• Experience with technologies such as JavaScript, Relational DBs (Oracle/SQL Server), ASP MVC, .Net Core, and WCF
• Experience building distributed, scalable complex services and robust microservices
• Proficiency with RedHat OpenShift
• Demonstrated analytical and problem-solving skills
• Organizational and communication skills
• Team-oriented individual who seeks input and involves others

Then Qualifications: Preferred Qualifications list. Benefits: from Everforth Apex Benefits Overview. We need to capture benefits: medical, dental, vision, life, disability, other insurance plans; ESPP; 401K with company match after 12 months; HSA on HDHP plan; SupportLinc EAP up to 8 free counseling sessions; corporate discount savings program and other discounts; on-demand training program; access to certification prep and library of technical and leadership courses/books/seminars after 6+ months tenure; certification discounts and perks to associations (CompTIA, IIBA); dedicated customer service team for consultants; certified Career Coach; Welcome Packet. We should preserve all that. We must not include boilerplate like equal opportunity, etc. Thus Benefits section with ul. Now ensure we don't include Pay or Schedule sections. Now produce HTML fragment. Check for any repeated lines: we should not duplicate. Let's craft. We need to ensure we don't include any markdown fences. Output only HTML. Let's write:

About the role

Senior Full Stack Developer position located in Jersey City, NJ/Addison, TX (Hybrid). Contract role for 12 months.

We are seeking a Senior Full Stack Developer with at least 10 years of experience, including work within the financial sector. The ideal candidate will possess strong communication and delivery skills. This role requires a working knowledge of GIT or similar source code repositories, as well as experience with continuous build and deployment strategies using Jenkins and Ansible.

Responsibilities

• Contribute to story refinement and defining requirements.
• Participate in and guide the team in estimating work necessary to realize a story or requirement through the delivery lifecycle.
• Perform proof-of-concept work as necessary to mitigate risk or implement new ideas.
• Code solutions and perform unit tests to deliver requirements per the defined acceptance criteria and compliance standards.
• Utilize multiple architectural components (data, application, business) in the design and development of client requirements.
• Assist the team with resolving technical complexities involved in realizing story work.

Requirements

A minimum of 10 years of professional experience is required.

Skills

• Core Java
• Experience with web services development, including REST and SOAP interfaces
• Experience with relational and non-relational databases, including ETL processes (e.g., Informatica)
• Experience with technologies such as JavaScript, Relational DBs (Oracle/SQL Server), ASP MVC, .Net Core, and WCF
• Experience building distributed, scalable complex services and robust microservices
• Proficiency with RedHat OpenShift
• Demonstrated analytical and problem-solving skills
• Organizational and communication skills
• Team-oriented individual who seeks input and involves others

Qualifications

• Demonstrated ability to get things done and make things happen; resourceful, seizes opportunities, and is an innovator
• Experience developing an understanding of stakeholder needs to help create and envision solutions
• Ability to analyze stakeholder processes to build efficiencies and improve software implementation
• Experience gathering and cataloging functional, non-functional, and technical requirements for stakeholder requests
• Ability to analyze functional and data requirements to determine software function and information storage
• Experience assisting users and development teams with application testing and troubleshooting
• Capability to identify, document, and troubleshoot application-related problems
• Experience documenting processes, procedures, and workflows associated with applications
• Experience creating and maintaining training materials for end-users
• Experience with JIRA tool and infrastructure

Benefits

• Medical, dental, vision, life, disability, and other insurance plans offering optional financial protection
• ESPP (employee stock purchase program)
• 401K program with company match after 12 months of tenure (contributions typically allowed within 30 days of starting)
• HSA (Health Savings Account) on the HDHP plan
• SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions
• Corporate discount savings program and other discounts
• On-demand training program
• Access to certification prep and a library of technical and leadership courses/books/seminars after 6+ months of tenure
• Certification discounts and other perks to associations including CompTIA and IIBA
• Dedicated customer service team for consultants to address benefits and other resources
• Certified Career Coach
• Welcome Packet containing full list of benefits, programs, support teams and resources

Check that we didn't include any boilerplate like equal opportunity, privacy policy, etc. Good. We didn't include Pay or Schedule sections. We preserved all substantive info: location, contract duration, role overview, responsibilities, required experience, technical skills, professional skills, preferred qualifications, benefits. We omitted job ID, company description fluff like awards, etc. That's okay as not required?