Senior Full Stack Developer

We need to output only HTML fragment, no /. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have Position Overview (we can treat as About the role). Then Key Job Responsibilities (Responsibilities). Then Required Qualifications (Qualifications). Preferred Qualifications (maybe Skills? Actually Preferred Qualifications could be Skills). Also Competency Group (maybe Skills). Work Environment (maybe Schedule? Actually schedule not given; we have work environment description: office work, up to 20% travel, irregular hours, on-call status. That's schedule info? Could be Schedule section. But we need to include Schedule only if posting actually states them. It does mention working times may include irregular hours and on-call status, including days, evenings, weekends, holidays. That's schedule info. So we can include Schedule section. Pay: Salary Pay Range given: $102,371.00 - $133,083.00. So we can include Pay section. Benefits: The posting mentions "Encore is committed to providing the best benefits options for our employees and families. Click here to view the benefits options..." That's generic, not specific benefits. It says "Click here to view the benefits options". No specific benefits listed. According to rules: never create Benefits section unless posting actually states them. It does not list specific benefits, just a link. So we should not include Benefits section. Skills: Could be derived from Preferred Qualifications and Competency Group. We can include Skills section with bullet list of specific skills mentioned: e.g., Next.js, TypeScript, .NET Core/.NET 8+, C#, ASP.NET Web API, Azure Functions, microservices, RESTful APIs, SQL Server, Azure SQL, Entity Framework Core, Azure DevOps, CI/CD, Infrastructure as Code, software architecture, design patterns, security, scalability, problem solving, Agile/Scrum, etc. Also Preferred: PWA, Azure API Management, Azure Service Bus, Event-Driven Architecture, Serverless, Docker, Kubernetes, Front-end performance optimization, Angular, Application Insights, Azure Monitor, Git, Bitbucket, Jira, Confluence, Azure certifications. Also Competency Group: Deliver World Class Service, Hospitality Ownership, Do The Right Thing, Demonstrates Self-Awareness, Drive Results, Ensures Accountability, See The Big Picture, Decision Quality, Manages Complexity, Value People, Collaborates. Those are competencies/behaviors; could be considered Skills. We'll include them. Requirements: Required Qualifications (education, years experience). We'll put that in Requirements section? Actually we have Qualifications and Requirements both possible headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which to use. We have both Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements section, and Preferred Qualifications + Competency Group to Skills section. Or we could have Qualifications section for Required Qualifications, and Skills for Preferred. But we have both headings available; we need to avoid duplication. Let's think: The posting includes "Required Qualifications" and "Preferred Qualifications". So we could have a Requirements section for Required Qualifications, and a Skills section for Preferred Qualifications + Competency Group. Or we could have Qualifications section for Required Qualifications, and Skills for Preferred. The instruction says we can use those headings; we just need to include sections only when posting has real specific content. We'll include both Requirements and Skills. Thus sections: - About the role (Position Overview) - Responsibilities (Key Job Responsibilities) - Requirements (Required Qualifications) - Skills (Preferred Qualifications + Competency Group) - Pay (Salary Pay Range) - Schedule (Work Environment details about hours, travel, on-call) We should not include Benefits. Now we need to format: Use

for each section heading. Then content: For prose use

. For lists use

• . We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract content. About the role: Position Overview paragraph: "The Senior Full Stack Developer aligns with Encore’s Application Development Team to deliver on strategic technology initiatives. This role supports all phases of the product management lifecycle, from defining the right solution to delivering and supporting it to scale. This role is part of an Agile team to provide subject matter expertise through clear and concise business analysis, identifying and quantifying the impact of business challenges, and using a flexible and adaptive approach that emphasizes teamwork and collaboration across business units. This role reports to the Director of Applications." We'll put that in a

  . Responsibilities: Key Job Responsibilities includes several bullet-like paragraphs but not formatted as list. We need to convert to

  • for any list of duties/requirements/benefits. The responsibilities are a series of sentences each starting with a bold heading? Actually they are grouped under headings: Software Development, Project Management, Production Support & Continuous Improvement, Documentation, Mentorship & Knowledge Sharing. Each heading followed by sentences. We should treat each bullet as a list item? The instruction: Use
    • for any list of duties/requirements/benefits. So we can make each responsibility item as
    • . Could also keep headings inside
    • maybe as . We'll preserve the content. Let's list responsibilities: Software Development: - Work with product managers, business analysts, quality assurance engineers, architects, DBA team, other developers, and/or any 3rd party vendors when necessary to design, develop, and test applications. - Adhere to the defined software development methodologies to ensure milestones are met, and technology standards are followed. - Take ownership of the project and drive it to completion. - Develop solutions and create system design and programming specification documents. - Work with DBA to develop database structure for applications. - Think outside of the box to provide solutions for technical challenges. - Work with Quality Assurance users to perform testing to maintain quality standards. - Function as project / technical lead when needed. - Actively build and maintain user relationships. - Stay in touch with new technologies and technology trends. Project Management: - Lead the project team on assigned projects. - Work directly with the product manager and agree to project delivery dates. - Ensure that assigned projects are completed within allocated budgets and schedules while meeting business objectives. - Communicate project milestones, priorities, and deliverables to business partners and team members. - Manage and appropriately escalate delivery impediments, risks, issues, and changes tied to the team’s development initiatives. - Manage project team’s tasks, identify necessary resources, and develop schedules to meet project completion deadlines. - Coach Junior Developers on agile supporting processes and guide the project team to adopt and embrace change. - Delegate tasks to the project team based on the individual’s skill set and availability. Production Support & Continuous Improvement: - Support and improve production applications - Troubleshoot complex issues related to performance, reliability, and data quality - Improve observability, monitoring, and operational maturity of Encore applications - Identify opportunities to improve development workflows, automation, and deployment practices Documentation, Mentorship & Knowledge Sharing: - Create and maintain the technical process, code, and design documentation. - Help establish an environment for team and project collaboration. - Maintain the knowledge base of the application development process and technical standards. We'll put each as
    • . Could also group under headings inside
    • but it's okay. Requirements (Required Qualifications): - Bachelor's degree in Computer Science, Software Engineering, or a related technical field. - 8+ years of professional software development experience in enterprise applications within corporate or consulting environments. - 6+ years of hands-on experience developing modern web applications using Next.Js and TypeScript. - 6+ years of experience designing and developing RESTful APIs and backend services using .NET Core/.NET 8+, C#, ASP.NET Web API, and Azure Functions. - Strong experience designing, building, and consuming scalable microservices and distributed systems. - Experience integrating enterprise applications with external systems such as CRM platforms, ERP systems, Oracle databases, and third-party APIs. - Strong knowledge of relational databases, including SQL Server 2019+, Azure SQL, query optimization, indexing, and performance tuning. - Experience with Entity Framework Core and modern data access patterns. - Experience building and supporting cloud-native applications in Microsoft Azure. - Hands-on experience with Azure DevOps, CI/CD pipelines, automated deployments, and Infrastructure as Code concepts. - Strong understanding of software architecture principles, design patterns, security best practices, and system scalability. - Strong problem-solving, troubleshooting, and analytical skills. - Experience working in Agile/Scrum environments and participating in sprint planning, grooming, and technical design discussions. We'll put as
      • . Skills (Preferred Qualifications + Competency Group): Preferred Qualifications: - Experience with Progressive Web Applications (PWA). - Experience with Azure API Management, Azure Service Bus, Event-Driven Architecture, and Serverless solutions. - Experience modernizing legacy applications and migrating solutions to cloud-based architectures. - Experience with containerization technologies such as Docker and Kubernetes. - Familiarity with Front-End performance optimization and modern Angular architecture patterns. - Experience with monitoring and observability tools such as Application Insights, Azure Monitor, or similar platforms. - Experience with Git, Bitbucket, Jira, and Confluence. - Microsoft Azure certifications (AZ-204, AZ-305, or related certifications) are preferred. Competency Group (list): - Deliver World Class Service - Hospitality Ownership - Do The Right Thing - Demonstrates Self-Awareness - Drive Results - Ensures Accountability - See The Big Picture - Decision Quality - Manages Complexity - Value People - Collaborates We'll combine into one
        • list. Pay: - Salary Pay Range: $102,371.00 - $133,083.00 - Additional note: The compensation offered for this role is determined based on the qualifications outlined in the job posting for the specified location. Final compensation is based on a number of factors including location, travel, relevant work experience, or particular skills and expertise. In addition, some positions may be eligible for other compensation such as potential overtime, bonuses or incentives. We'll put as

          maybe with bullet? It's not a list but we can keep as

          . The instruction: Use

          for prose. So we can put that as a paragraph. Schedule (Work Environment): - Office Work is performed primarily in an office environment, and up to 20% of the time will be required for travel and normal business operations in corporate offices. - Working times may include irregular hours and on-call status, including days, evenings, weekends, and holidays. - Team members must adhere to appearance guidelines as defined by Encore based in an office environment and when traveling on an individual venue or a representation of venues in that city or area. We'll put as

          or

          • . Since it's a list of statements, we can use
            • . But the instruction says use
              • for any list of duties/requirements/benefits. Schedule is not exactly those but still a list. Safer to use

                for prose. We'll combine into a paragraph. Now we need to output only HTML fragment, no markdown fences. Let's construct:

                About the role

                ...

                Responsibilities

                • ...
                ...

                Requirements

                • ...
                ...

                Skills

                • ...
                ...

                Pay

                ...

                Schedule

                ...

                Make sure