Senior Full Stack Developer
Trinity Solar · Iselin, NJ · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. No filler like "commensurate with experience". The posting does not mention Benefits, Pay, Schedule explicitly. So we should not include those sections. We need to include sections for About the role (maybe intro), Responsibilities (What You'll Do), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Experience?), Skills (maybe Technical Environment?), but we must avoid duplication. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content.
We need to preserve all substantive information. We'll parse the posting.
Key sections:
- Intro: "Senior Full Stack Developer – .NET / C# / React / Angular / Azure Build Enterprise Technology. Solve Complex Problems. Help Shape What’s Next. Trinity Total Home is seeking an experienced Senior Full Stack Developer to design, develop, integrate, and enhance enterprise applications that support our growing business. This is a hands-on full-stack software engineering role for a developer with strong experience across the Microsoft technology stack, including C#, .NET/.NET Core, .NET 8+, ASP.NET Core, React.js, Angular, TypeScript, REST APIs, SQL Server, Microsoft Azure, and Azure DevOps. You’ll work across the full Software Development Life Cycle (SDLC)—from architecture and database design through front-end development, API and enterprise integrations, testing, CI/CD, deployment, and production support. You'll also have opportunities to work with Generative AI, AI-assisted development tools, intelligent automation, and AI-enabled applications as we continue to modernize our technology environment. If you're a hands-on developer who enjoys solving complex problems, learning new technology, and building applications that directly impact the business, we'd like to hear from you."
That's about the role.
- What You'll Do (Responsibilities): list of bullet points.
- AI & Intelligent Automation (maybe part of responsibilities or separate? Could be part of Responsibilities or maybe separate section but not required headings. We could include under Responsibilities as part of bullet list.
- Required Qualifications: list.
- Preferred Experience: list.
- Technical Leadership: description.
- Our Technology Environment: list of tech.
- Who Will Succeed Here?: description.
- Physical & Work Requirements: list.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can treat:
- About the role: intro paragraph.
- Responsibilities: "What You'll Do" plus AI & Intelligent Automation bullet points.
- Requirements: maybe "Required Qualifications".
- Qualifications: maybe "Preferred Experience" (or could be Skills). But we need both Requirements and Qualifications sections if content exists. We have both Required and Preferred.
- Skills: maybe "Our Technology Environment" or "Technical Leadership"? Could be Skills.
We must not invent sections with placeholder. So we include sections only if we have real content.
We must not repeat job title as heading. Already not.
We must not include Job ID etc.
We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must output only HTML fragment.
We'll produce:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content.
We need to preserve all substantive information. We'll parse the posting.
Key sections:
- Intro: "Senior Full Stack Developer – .NET / C# / React / Angular / Azure Build Enterprise Technology. Solve Complex Problems. Help Shape What’s Next. Trinity Total Home is seeking an experienced Senior Full Stack Developer to design, develop, integrate, and enhance enterprise applications that support our growing business. This is a hands-on full-stack software engineering role for a developer with strong experience across the Microsoft technology stack, including C#, .NET/.NET Core, .NET 8+, ASP.NET Core, React.js, Angular, TypeScript, REST APIs, SQL Server, Microsoft Azure, and Azure DevOps. You’ll work across the full Software Development Life Cycle (SDLC)—from architecture and database design through front-end development, API and enterprise integrations, testing, CI/CD, deployment, and production support. You'll also have opportunities to work with Generative AI, AI-assisted development tools, intelligent automation, and AI-enabled applications as we continue to modernize our technology environment. If you're a hands-on developer who enjoys solving complex problems, learning new technology, and building applications that directly impact the business, we'd like to hear from you."
That's about the role.
- What You'll Do (Responsibilities): list of bullet points.
- AI & Intelligent Automation (maybe part of responsibilities or separate? Could be part of Responsibilities or maybe separate section but not required headings. We could include under Responsibilities as part of bullet list.
- Required Qualifications: list.
- Preferred Experience: list.
- Technical Leadership: description.
- Our Technology Environment: list of tech.
- Who Will Succeed Here?: description.
- Physical & Work Requirements: list.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can treat:
- About the role: intro paragraph.
- Responsibilities: "What You'll Do" plus AI & Intelligent Automation bullet points.
- Requirements: maybe "Required Qualifications".
- Qualifications: maybe "Preferred Experience" (or could be Skills). But we need both Requirements and Qualifications sections if content exists. We have both Required and Preferred.
- Skills: maybe "Our Technology Environment" or "Technical Leadership"? Could be Skills.
We must not invent sections with placeholder. So we include sections only if we have real content.
We must not repeat job title as heading. Already not.
We must not include Job ID etc.
We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must output only HTML fragment.
We'll produce:
About the role
...
Responsibilities
- ... each bullet
Requirements
- ... Required Qualifications bullets
Qualifications
- ... Preferred Experience bullets
Skills
Our Technology Environment: ... list maybe as ul.
Could also be ul. We need to preserve all substantive information. So we need to include all bullet points from Responsibilities, Required Qualifications, Preferred Experience, Technology Environment, Technical Leadership, Who Will Succeed Here?, Physical & Work Requirements maybe as part of Skills or separate? But we have no heading for those; we could incorporate them into Skills or maybe another section like "Additional Information". But only allowed headings are those listed. We could put extra content under Skills or maybe under About the role? But we must preserve all substantive info; we can embed them as paragraphs under appropriate sections. We could add a section "Skills" that includes Technical Environment, Technical Leadership, Who Will Succeed Here?, Physical & Work Requirements as paragraphs/lists. But we must not create sections like "Physical & Work Requirements" unless heading matches allowed list. Not allowed. So we need to fit them somewhere. We could add a paragraph under Skills summarizing those points, but we must preserve all info, not summarize away detail. Summarizing may lose detail. Better to keep them as lists under Skills. Thus under Skills we can have multiple sub-sections? Not allowed to add extra headings. But we can include multiple- lists under the Skills section, each preceded by a
describing the category? That's okay. We must not invent headings; we can keep the content as is. Thus:
Skills
Technology Environment:
- ... list of technologies
Technical Leadership:
- ... bullets
Who Will Succeed Here?
- ... bullets
Physical & Work Requirements:
- ... bullets