Sr. Software Engineer Web Applications

We need to output HTML fragment with sections: About the role (maybe "About the role" heading), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key info: - Title: Senior Full-Stack Software Engineer (but we don't repeat as heading) - Location: Stanford Health Care, Palo Alto, 1830 Embarcadero, California (Hybrid) - FTE: 1.0 FTE Full time Day - 08 Hour (so schedule: Day - 08 Hour) - Hybrid: yes - Job ID etc ignore. - Overview: "Stanford Health Care’s Technology & Digital Solutions team is seeking a Senior Full-Stack Software Engineer to support, maintain, and evolve a suite of mission-critical custom applications that advance all three missions of the Stanford Medicine: education, research, and patient care. This role interacts with teams across Stanford University, Stanford Health Care, and Stanford Children's Health. In this role, you will suggest and use modern, state-of-the-art technologies to deliver meaningful impact. You are expected to leverage cloud-native platforms and AI-enabled capabilities to design and build scalable, reliable solutions. Working within small, focused teams, you will have end-to-end ownership of applications - from technical design and development through deployment, operations, and continuous improvement. This is a Stanford Health Care job." - "A Brief Overview The Senior Full-Stack Software Engineer is responsible for designing, developing, testing, deploying, and maintaining secure, scalable, mission-critical web applications and services for Stanford Health Care. This hands-on role requires strong expertise across both front-end and back-end development, as well as demonstrated experience building and operating applications in cloud-native environments. Working in a fast-paced Agile environment, the Senior Full-Stack Software Engineer partners with product managers, UX/UI designers, engineers, infrastructure teams, and business stakeholders to deliver reliable, accessible, and user-centered digital solutions. The role contributes throughout the full software development lifecycle, including requirements gathering, architecture and technical design, implementation, testing, deployment, production support, and continuous improvement." - "What You Will Do" list: many bullet points. - Education Qualifications: Bachelor’s degree in IT, CS, Software Engineering, Web Design or related field. Required. Master's Degree Preferred. - Experience Qualifications: 5+ years of directly related experience Required. - Required Knowledge, Skills And Abilities: list many. - Licenses and Certifications: None. - Base Pay Scale: Generally starting at $76.97 - $102.01 per hour. Also note: salary of finalist set based on factors. - No explicit benefits listed. - Schedule: Day - 08 Hour (full-time day shift). Could include Schedule section. - Benefits: none explicit, so we should not create Benefits section. - Pay: we have pay scale, so include Pay section. - About the role: could be the overview paragraph(s). Could be a short prose. - Responsibilities: the "What You Will Do" list. - Requirements: could combine Education Qualifications and Experience Qualifications? Or separate sections: Education, Experience. But we have headings: Qualifications, Skills, etc. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Possibly also Education and Experience could be under Qualifications? But we have Qualifications heading; we could put education and experience there. Skills heading for knowledge, skills, abilities. We must not repeat job title as heading. Must not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from "What You Will Do", all bullet points from Required Knowledge, Skills And Abilities, education qualifications, experience qualifications, pay scale, schedule. We must not include boilerplate like EEO, etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

... overview paragraphs ...

Responsibilities

• ... each bullet from What You Will Do ...
...

Requirements

Maybe we can combine Education and Experience? But we have Qualifications heading separate. Could do Requirements for education+experience? But we also have Qualifications heading. Let's decide: Use Requirements for education and experience (since they are requirements). Use Qualifications for maybe "Preferred Master's Degree"? But that's also qualification. Actually education qualifications: Bachelor's degree required, Master's preferred. Experience: 5+ years required. So we can put those under Requirements. Then Skills heading for knowledge, skills, abilities list. Pay:

Pay

Base Pay Scale: Generally starting at $76.97 - $102.01 per hour. The salary of the finalist selected for this role will be set based on a variety of factors, including but not limited to, internal equity, experience, education, specialty and training. This pay scale is not a promise of a particular wage.

Schedule:

Schedule

Day - 08 Hour (full-time day shift), Hybrid.

Also mention location? Location could be in About the role or separate? Not required heading. Could include location in About the role paragraph. We must not create Benefits section because no specific benefits. We must not create sections with filler. Now need to ensure we preserve all substantive information: The overview paragraphs, the "What You Will Do" list (many items), the education qualifications, experience qualifications, the knowledge/skills/abilities list, pay, schedule. Let's extract the "What You Will Do" bullet points exactly as they appear (they are sentences separated by periods but each bullet seems to be a sentence). We'll convert each to

. List: - Design, develop, test, deploy, and maintain secure, full-stack web applications, APIs, services, and integrations. - Build responsive, accessible, and user-centered front-end experiences using HTML, CSS, JavaScript, and modern web development frameworks. - Design and develop robust back-end services, APIs, integrations, and data-access layers using technologies such as Java, Python - Work with relational and NoSQL databases to design data models, develop queries, optimize performance, and support application integrations. - Build and support public-facing and internal applications that meet high standards for availability, performance, usability, security, and maintainability. - Translate functional requirements, wireframes, and design specifications into scalable technical designs and high-quality software solutions. - Collaborate with product managers, designers, stakeholders, and engineering teams to clarify requirements, define technical approaches, and deliver iterative product improvements. - Participate in all phases of the software development lifecycle, including analysis, technical design, development, code review, testing, deployment, production support, and documentation. - Develop automated unit, integration, and end-to-end tests to improve software quality, reliability, and release confidence. - Troubleshoot and resolve complex production issues across the user interface, APIs, application services, integrations, databases, and cloud infrastructure. - Design and improve application architecture and engineering practices to enhance performance, security, reliability, scalability, and maintainability. - Develop, deploy, and operate applications in cloud-native environments using containers, CI/CD pipelines, automated testing, monitoring, logging, and observability tools. - Partner with infrastructure, platform, and security teams to ensure applications comply with organizational standards for cloud operations, security, privacy, and resilience. - Contribute to the selection and adoption of development frameworks, tools, standards, and best practices. - Stay current with full-stack, cloud-native, and AI-enabled software development technologies and practices; identify opportunities to apply them responsibly to improve development efficiency and user outcomes. - Mentor team members, provide technical guidance, and champion engineering best practices across the organization. Check for any missing bullet: after "Design and develop robust back-end services, APIs, integrations, and data-access layers using technologies such as Java, Python" maybe missing a period but okay. Now Knowledge, Skills And Abilities list: - Strong proficiency in full-stack software development, including modern front-end, back-end, API, database, and integration technologies. - Strong proficiency in HTML, CSS, JavaScript, and modern front-end frameworks and responsive web development practices. - Strong proficiency in back-end development using Java, Python, .NET, or comparable languages and frameworks. - Experience designing, developing, securing, and supporting RESTful APIs, application services, and system integrations. - Experience working with relational and NoSQL databases, including data modeling, query development, and performance tuning. - Demonstrated experience designing, building, deploying, and operating scalable applications in cloud-native environments. - Knowledge of cloud-native tools and practices, including containers, CI/CD pipelines, automated testing, infrastructure as code, monitoring, logging, and observability. - Experience with one or more major cloud platforms, such as Microsoft Azure, AWS, or Google Cloud Platform. - Knowledge of secure software development practices, application security principles, authentication and authorization patterns, and common web application vulnerabilities. - Knowledge of software architecture, design patterns, algorithms, data structures, web technologies, protocols, and cross-browser compatibility. - Ability to build and support high-performing, reliable, production-quality applications for large and demanding user audiences. - Knowledge of accessibility, usability, responsive design, human-computer interaction, and interaction design patterns. - Strong troubleshooting, debugging, analytical, and problem-solving skills. - Ability to communicate complex technical concepts effectively to technical and nontechnical stakeholders. - Ability to work effectively in a fast-paced, collaborative, and evolving Agile environment. - Ability to influence technical direction, mentor peers, and champion engineering standards and best practices. Also Licenses and Certifications: None (we can ignore as no substantive content? It's a statement but maybe we can include under Requirements? But it's not a requirement; it's just "None". Could be omitted as not substantive? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "None" is substantive? It's a statement that there are no licenses/certs required. Could be included but we don't have a specific heading for Licenses and Certifications. Could fold into Requirements or Qualifications as a short note. But we have no heading for Licenses and Certifications; we could include a

under Requirements: "No specific licenses or certifications are required." That preserves the info. Now Education Qualifications: Bachelor’s degree in Information Technology, Computer Science, Software Engineering, Web Design or a directly related field from an accredited college or university. Required. Master's Degree Preferred. Experience Qualifications: 5+ years of directly related experience Required. We'll put these under Requirements. Now About the role: combine the introductory paragraphs before "A Brief Overview". Actually there is some introductory fluff: "If you're ready to be part of our legacy of hope and innovation, we encourage you to take the first step and explore our current job openings. Your best is waiting to be discovered." That's generic boilerplate? Might be considered promotional but still substantive? It's not about the role. Might be considered boilerplate but not explicitly listed as to remove. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That sentence is not those categories; it's more like a call to action. Could be considered application instructions? It's encouraging to explore openings. Might be considered application instruction. Safer to omit? The instruction says remove application instructions. That sentence is basically an invitation to explore openings, which is application instruction. So we should omit it. Also the line "Day - 08 Hour (United States of America)" maybe duplicate. We'll keep the substantive overview: "Stanford Health Care’s Technology & Digital Solutions team is seeking a Senior Full-Stack Software Engineer to support, maintain, and evolve a suite of mission-critical custom applications that advance all three missions of the Stanford Medicine: education, research, and patient care. This role interacts with teams across Stanford University, Stanford Health Care, and Stanford Children's Health