Full Stack .NET Software Engineer (Eatontown, NJ / Hybrid)

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting: It includes company overview, job description, responsibilities (What You Will Do), qualifications (What YOU Will Bring To C&F), benefits (What C&F Will Bring To You). Also Pay info: salary range $82,800 to $130,100. Also maybe schedule not mentioned. Benefits: they list many benefits: Competitive compensation package, Generous 401K employer match, Employee Stock Purchase plan with employer matching, Generous Paid Time Off, Excellent benefits beyond health, dental & vision, programs for whole family wellness, tuition reimbursement, industry-related certifications, professional training, dynamic work environment, spirit of social and community responsibility, matching donation program, volunteer opportunities, employee-driven corporate giving program, belonging, inclusivity, accommodations, EEO statement (but we should remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement lines. Also remove the California resident privacy notice? That's legal boilerplate; remove. Also remove duplicated lines like "If you require special accommodations, please let us know." appears twice; we can keep one? Probably remove duplicates. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the benefits list as is but maybe condense into bullet list. We need sections: About the role? Could be company overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: About the role could be a brief description of the role (maybe from job description). Could combine company overview? But "About the role" maybe a short paragraph describing the position. The posting includes: "Crum & Forster seeks an experienced Full-Stack Software Engineer with a strong background in Microsoft technologies." That's about the role. Also earlier description of division. We could put that under About the role. Responsibilities: from "What You Will Do" list. Requirements: maybe from "What YOU Will Bring To C&F" includes education, experience, Agile, etc. Could be Requirements. Qualifications: maybe overlapping with Requirements; but we could separate: Requirements = mandatory, Qualifications = preferred? However the posting doesn't separate; we could combine into one section. But we need to follow instruction: include a section ONLY when posting has real specific content for it. We could have Requirements and Qualifications both with content; but we need to avoid duplication. Let's parse: "What YOU Will Bring To C&F" includes Bachelor’s degree, 3-5+ years experience, Agile, ASP.NET Core, etc. That's basically requirements. There's also "Experience with GraphQL a plus." That's a preferred qualification. Could treat that as Qualifications. Skills: maybe list technical skills: React, Angular, TypeScript, Azure, DevOps, SQL/NoSQL, Git, etc. Could be separate. Benefits: from "What C&F Will Bring To You". Pay: salary range. Schedule: not mentioned, so omit. We must not include headings with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Crum & Forster’s Accident & Health division seeks an experienced Full-Stack Software Engineer with a strong background in Microsoft technologies to design, develop, and maintain full-stack applications using React, Angular, ASP.NET Core, .NET Core, and EF Core, while working with Azure services, DevOps practices, and SQL/NoSQL databases.

Responsibilities

• Design, develop, and maintain full-stack applications using React, Angular, ASP.NET Core, .NET Core, and EF Core.
• Develop and consume RESTful APIs to support various applications.
• Implement and manage Azure services for cloud-based applications.
• Collaborate with cross-functional teams to design and implement new features and enhancements.
• Utilize DevOps practices to automate deployment and ensure continuous integration and delivery.
• Work with both relational and non-relational databases to design and optimize data storage solutions.
• Utilize AI coding tools to assist with development.
• Write clean, maintainable, and efficient code following best practices and coding standards.
• Conduct code reviews and provide constructive feedback to peers.
• Troubleshoot and resolve software defects and performance issues.
• Stay current with emerging technologies and industry trends to continuously improve skills and contribute to the team’s knowledge base.
• Perform other duties as assigned.

Requirements

• Bachelor’s degree in computer science, Engineering, or a related field, or equivalent work experience.
• Minimum of 3‑5+ years of professional experience in software development with a focus on full‑stack development.
• Hands‑on experience working in a fully Agile environment (e.g., SCRUM) and a comprehensive understanding of Agile principles and methodologies.
• Proven experience with ASP.NET Core, .NET Core, and EF Core.
• Strong understanding of RESTful APIs.
• Experience with front‑end frameworks React, Angular, leveraging TypeScript.
• Familiarity with Azure services and cloud‑based application development.
• Experience with DevOps practices and tools such as CI/CD pipelines.
• Proficiency in working with SQL and NoSQL databases.
• Experience with version control systems such as Git.
• Ability to establish responsible deadlines and work plans; manages time and prioritizes multiple tasks effectively.
• Change champion who effectively manages the implementation of new ideas.
• Continually defines ways to increase customer satisfaction.
• Able to readily adapt to shifting priorities and rapid change due to multiple demands.
• Demonstrated motivation and initiative.
• Ability to work autonomously.
• Strong communication and cross‑functional collaboration skills.
• Creative problem solver with ability to think abstractly; strong analytic skills.

Qualifications

• Experience with GraphQL a plus.
• Experience with coding tools including Claude Code or GitHub Copilot.

Skills

• React
• Angular
• TypeScript
• ASP.NET Core
• .NET Core
• EF Core
• RESTful APIs
• Azure services
• DevOps / CI/CD
• SQL and NoSQL databases
• Git
• Agile/SCRUM
• AI coding tools (Claude Code, GitHub Copilot)

Benefits

• Competitive compensation package
• Generous 401K employer match
• Employee Stock Purchase plan with employer matching
• Generous Paid Time Off
• Excellent benefits that go beyond health, dental & vision (programs focused on whole family’s wellness: physical, mental, financial)
• Tuition reimbursement
• Industry‑related certifications and professional training
• Dynamic, ambitious, fun and exciting work environment
• Spirit of social and community responsibility: matching donation program, volunteer opportunities, employee‑driven corporate giving program
• Inclusive culture where you will BELONG
• Accommodations available upon request

Pay

The annualized base pay for this position ranges from a minimum of $82,800 to a maximum of $130,100, with actual compensation determined by market pay, responsibilities, skills, and employee performance. Discretionary equity (stock)‑based compensation and/or performance‑based variable pay may also be available.

We must ensure we didn't include any boilerplate like EEO, California privacy notice, duplicated lines. We removed duplicates. Also we removed the line "If you require special accommodations, please let us know." but we kept a bullet "Accommodations available upon request" under Benefits; that's okay as it's a benefit. The original had that line twice; we kept one. Check for any leftover boilerplate: The sentence "At C&F you will BELONG" we kept as bullet. The sentence "If you require special accommodations, please let us know." we turned into bullet. The EEO statement about race etc removed. The California resident privacy notice removed. The statement about Crum & Forster committed to ensuring a workplace free from discriminatory pay disparities and complying with applicable pay equity laws - that's somewhat legal but maybe considered boilerplate? It's about pay equity; could be considered legal. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is about pay equity, which is related to EEO. Safer to remove. We didn't include it. Check for any duplicated lines: we didn't repeat. Now ensure we didn't miss any substantive info: Company overview details (200-year history, $6.2bn premium, A+ rating, 3000 employees, locations US/India, awards, part of Fairfax Financial Holdings). Should we include that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive. Should we include it somewhere? Possibly under About the role or a separate section like "About the company". But the allowed headings list does not include "About the company". However we could incorporate into About the role? The About the role section could include company overview? But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when appropriate; but we could also add other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to them. However we need to preserve all substantive information, including company overview. Where to put it? Could be part of About the role? But About the role is about the role, not company. However we could treat About the role as including both role and company overview? Might be okay. But we might lose some details like awards, financials. Could we add a paragraph under About the role that includes company overview? That would preserve it. Let's incorporate company overview details into About the role paragraph. Thus About the role paragraph: "Crum & Forster (C&F) provides market leading property & casualty, accident & health, specialty and standard commercial lines insurance solutions. A true underwriting company with a 200‑year history, $6.2 billion annual gross written premium, and an A+ (Superior) AM Best