Full Stack Software Engineer, Vice President – Corporate Functions Technology
About the role
then... paragraphs. - Responsibilities: The "What You Will Be Responsible For" section with bullet points under subheadings. We need to make a list
- for any list of duties/requirements/benefits. The responsibilities are grouped under subheadings: Full Stack Engineering & Solution Design, Cloud, DevOps & Production Operations, AI Integration & Data Platforms, Security, Risk & Compliance, Collaboration & Continuous Improvement. Each has bullet points. We can combine all responsibilities into a single list? Probably better to keep subheadings? But rule: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings allowed. So we cannot have subheadings like Full Stack Engineering etc as
. We could embed them inside
or
- text. The rule: Use
- for any list of duties/requirements/benefits. So we can create a
- with each bullet as
- . The bullet points are many; we can extract each bullet line.
Let's parse responsibilities:
Full Stack Engineering & Solution Design:
- Serve as a hands‑on lead engineer, owning the design and implementation of complex full stack features across front‑end, back‑end, APIs, and data layers.
- Lead technical design and solution architecture for key initiatives, translating functional requirements into scalable, maintainable systems.
- Build high‑quality user interfaces using component‑driven architectures and modern state management, with strong attention to usability, accessibility, and performance.
- Design and implement secure, resilient backend services and RESTful APIs that support enterprise workflows and AI‑enabled user journeys.
- Set and reinforce engineering standards for code quality, testing, documentation, and maintainability through design reviews and code reviews.
Cloud, DevOps & Production Operations:
- Design and implement cloud‑native architectures, leveraging containerization, resiliency patterns, horizontal scalability, and performance optimization.
- Build, own, and evolve CI/CD pipelines, infrastructure as code, automated testing, and release controls to enable rapid yet governed delivery.
- Ensure production systems meet enterprise expectations for availability, reliability, observability, and operational resilience.
- Own troubleshooting and resolution of complex issues across the full stack, leading root cause analysis and driving durable fixes.
- Champion best practices for monitoring, alerting, logging, and cost awareness in cloud environments.
AI Integration & Data Platforms:
- Integrate AI/ML capabilities into applications in close collaboration with AI and data teams, embedding them directly into user workflows.
- Implement evaluation controls, telemetry, and safe failure modes for AI‑enabled features, including human‑in‑the‑loop review checkpoints where appropriate.
- Design and integrate with databases and enterprise data platforms, including SQL/NoSQL systems and lakehouse technologies (e.g., Databricks).
- Build efficient data access patterns and support scheduled or recurring processes for continuous monitoring, analytics, and insights generation.
Security, Risk & Compliance:
- Embed security, privacy, and compliance requirements into system design and implementation from the ground up.
- Enforce secure coding practices, identity and access controls, audit logging and data protection standards.
- Partner with risk, security, and compliance stakeholders to ensure solutions meet regulatory and internal policy requirements in a regulated environment.
- Contribute to architectural decisions that balance innovation, usability, and risk management in an enterprise context.
Collaboration & Continuous Improvement:
- Collaborate closely with product owners, audit stakeholders, designers, AI teams, data engineers and platform partners to deliver production‑ready solutions.
- Help shape technical roadmaps, influence prioritization of technical debt, and drive continuous improvement across the engineering lifecycle.
- Lead by example in adopting and promoting modern engineering practices, tools, and patterns.
Now Requirements / Qualifications / Skills: The posting includes "What We Value" (skills and behaviors) and "Education & Preferred Qualifications" and "Nice to Have". We need to decide which sections to include: Requirements, Qualifications, Skills. We have to include sections only when posting has real specific content. We have content for Qualifications (Education & Preferred Qualifications). Also we have "What We Value" which could be Skills. Also "Nice to Have" could be additional qualifications but maybe we can include under Qualifications or Skills. We need to avoid filler like "commensurate with experience". Not present.
We'll create:
Qualifications
with- items from Education & Preferred Qualifications and maybe Nice to Have? But Nice to Have is separate; we could still include as part of Qualifications but maybe better to have Skills section for "What We Value". Let's map:
- Skills: "What We Value" list (strong full stack engineering expertise, technical leadership, ability to design scalable cloud-native systems, solid DevOps discipline, experience integrating AI/ML, strong understanding of secure coding, analytical problem-solving, strong collaboration, continuous learning mindset). We'll put those as
- .
- Qualifications: Education & Preferred Qualifications (Bachelor's degree..., Master's preferred; 7+ years experience; experience operating in senior/lead engineer capacity; proficiency in React, JS/TS, HTML5, CSS3; strong experience building backend services and RESTful APIs using Node.js, exposure to Python/Java; solid knowledge of SQL/NoSQL; hands-on experience with AWS/Azure; experience with container platforms such as Kubernetes; strong DevOps experience; experience integrating AI/ML via APIs; proficiency with Git). Also Nice to Have could be added as extra bullet points under Qualifications or maybe separate but we don't have a heading for Nice to Have; we could include them under Qualifications as additional bullet points.
We'll also include Benefits: The posting includes benefits description after Salary Range. So we need Benefits section with list of benefits.
Pay: Salary Range $120,000 - $202,500 Annual. So we need Pay section with that info.
Schedule: Not mentioned. So we omit Schedule.
Now we need to ensure we don't repeat job title as heading. Not needed.
We must not include boilerplate like EEO, legal, application instructions, etc. Remove those.
We need to output only HTML fragment.
Let's craft:
About the role
We are seeking a Full Stack Software Engineer to play a critical role in modernizing the technology ecosystem that supports Internal Audit. This role sits at the intersection of engineering excellence, cloud‑native delivery, and intelligent workflow enablement, with a strong focus on building enterprise‑grade systems that improve audit lifecycle efficiency, transparency, and data‑driven risk insights. This is an individual contributor position with end‑to‑end ownership of complex systems. You will actively design, build, test, and operate full stack, cloud‑native applications, while also serving as a technical leader—driving system design decisions, setting engineering standards, and leading by example through high‑quality code. You will deliver secure, scalable applications that embed AI‑enabled capabilities directly into user workflows—supporting structured content generation, workflow enhancement and planning experiences—while meeting enterprise standards for security, privacy, governance, and operational readiness.
Responsibilities
- Serve as a hands‑on lead engineer, owning the design and implementation of complex full stack features across front‑end, back‑end, APIs, and data layers.
- Lead technical design and solution architecture for key initiatives, translating functional requirements into scalable, maintainable systems.
- Build high‑quality user interfaces using component‑driven architectures and modern state management, with strong attention to usability, accessibility, and performance.
- Design and implement secure, resilient backend services and RESTful APIs that support enterprise workflows and AI‑enabled user journeys.
- Set and reinforce engineering standards for code quality, testing, documentation, and maintainability through design reviews and code reviews.
- Design and implement cloud‑native architectures, leveraging containerization, resiliency patterns, horizontal scalability, and performance optimization.
- Build, own, and evolve CI/CD pipelines, infrastructure as code, automated testing, and release controls to enable rapid yet governed delivery.
- Ensure production systems meet enterprise expectations for availability, reliability, observability, and operational resilience.
- Own troubleshooting and resolution of complex issues across the full stack, leading root cause analysis and driving durable fixes.
- Champion best practices for monitoring, alerting, logging, and cost awareness in cloud environments.
- Integrate AI/ML capabilities into applications in close collaboration with AI and data teams, embedding them directly into user workflows.
- Implement evaluation controls, telemetry, and safe failure modes for AI‑enabled features, including human‑in‑the‑loop review checkpoints where appropriate.
- Design and integrate with databases and enterprise data platforms, including SQL/NoSQL systems and lakehouse technologies (e.g., Databricks).
- Build efficient data access patterns and support scheduled or recurring processes for continuous monitoring, analytics, and insights generation.
- Embed security, privacy, and compliance requirements into system design and implementation from the ground up.
- Enforce secure coding practices, identity and access controls, audit logging and data protection standards.
- Partner with risk, security, and compliance stakeholders to ensure solutions meet regulatory and internal policy requirements in a regulated environment.
- Contribute to architectural decisions that balance innovation, usability, and risk management in an enterprise context.
- Collaborate closely with product owners, audit stakeholders, designers, AI teams, data engineers and platform partners to deliver production‑ready solutions.
- Help shape technical roadmaps, influence prioritization of technical debt, and drive continuous improvement across the engineering lifecycle.
- Lead by example in adopting and promoting modern engineering practices, tools, and patterns.
Skills
- Strong full stack engineering expertise, spanning front‑end, back‑end, APIs, and data layers in enterprise‑grade systems.
- Demonstrated technical leadership as a hands‑on engineer, leading by example through design, coding, and operational ownership.
- Ability to design scalable, cloud‑native systems with a focus on reliability, performance, and maintainability.
- Solid DevOps discipline, including CI/CD, infrastructure as code, automated testing, and observability.
- Experience integrating AI/ML capabilities into applications in a controlled, observable, and user‑centric way.
- Strong understanding of secure coding and compliance considerations in regulated enterprise environments.
- Analytical problem‑solving skills and the ability to translate complex requirements into pragmatic technical solutions.
- Strong collaboration and communication skills across engineering, AI, security, and business stakeholders.
- A continuous learning mindset and commitment to improving engineering practices and system quality.
Qualifications
- Bachelor’s degree in Computer Science, Software Engineering, or a related field, or equivalent practical experience; Master’s degree preferred.
- 7+ years of experience delivering enterprise full stack web applications and APIs in cloud environments, with ownership of production systems.
- Experience operating in a senior or lead engineer capacity, driving technical design decisions and mentoring other engineers.
- Proficiency in React, JavaScript/TypeScript, HTML5, and CSS3.
- Strong experience building backend services and RESTful APIs using Node.js, with exposure to Python and/or Java frameworks.
- Solid knowledge of SQL and NoSQL databases, data modeling, and efficient data access patterns.
- .
- Qualifications: Education & Preferred Qualifications (Bachelor's degree..., Master's preferred; 7+ years experience; experience operating in senior/lead engineer capacity; proficiency in React, JS/TS, HTML5, CSS3; strong experience building backend services and RESTful APIs using Node.js, exposure to Python/Java; solid knowledge of SQL/NoSQL; hands-on experience with AWS/Azure; experience with container platforms such as Kubernetes; strong DevOps experience; experience integrating AI/ML via APIs; proficiency with Git). Also Nice to Have could be added as extra bullet points under Qualifications or maybe separate but we don't have a heading for Nice to Have; we could include them under Qualifications as additional bullet points.
We'll also include Benefits: The posting includes benefits description after Salary Range. So we need Benefits section with list of benefits.
Pay: Salary Range $120,000 - $202,500 Annual. So we need Pay section with that info.
Schedule: Not mentioned. So we omit Schedule.
Now we need to ensure we don't repeat job title as heading. Not needed.
We must not include boilerplate like EEO, legal, application instructions, etc. Remove those.
We need to output only HTML fragment.
Let's craft:
- items from Education & Preferred Qualifications and maybe Nice to Have? But Nice to Have is separate; we could still include as part of Qualifications but maybe better to have Skills section for "What We Value". Let's map:
- Skills: "What We Value" list (strong full stack engineering expertise, technical leadership, ability to design scalable cloud-native systems, solid DevOps discipline, experience integrating AI/ML, strong understanding of secure coding, analytical problem-solving, strong collaboration, continuous learning mindset). We'll put those as
- . The bullet points are many; we can extract each bullet line.
Let's parse responsibilities:
Full Stack Engineering & Solution Design:
- Serve as a hands‑on lead engineer, owning the design and implementation of complex full stack features across front‑end, back‑end, APIs, and data layers.
- Lead technical design and solution architecture for key initiatives, translating functional requirements into scalable, maintainable systems.
- Build high‑quality user interfaces using component‑driven architectures and modern state management, with strong attention to usability, accessibility, and performance.
- Design and implement secure, resilient backend services and RESTful APIs that support enterprise workflows and AI‑enabled user journeys.
- Set and reinforce engineering standards for code quality, testing, documentation, and maintainability through design reviews and code reviews.
Cloud, DevOps & Production Operations:
- Design and implement cloud‑native architectures, leveraging containerization, resiliency patterns, horizontal scalability, and performance optimization.
- Build, own, and evolve CI/CD pipelines, infrastructure as code, automated testing, and release controls to enable rapid yet governed delivery.
- Ensure production systems meet enterprise expectations for availability, reliability, observability, and operational resilience.
- Own troubleshooting and resolution of complex issues across the full stack, leading root cause analysis and driving durable fixes.
- Champion best practices for monitoring, alerting, logging, and cost awareness in cloud environments.
AI Integration & Data Platforms:
- Integrate AI/ML capabilities into applications in close collaboration with AI and data teams, embedding them directly into user workflows.
- Implement evaluation controls, telemetry, and safe failure modes for AI‑enabled features, including human‑in‑the‑loop review checkpoints where appropriate.
- Design and integrate with databases and enterprise data platforms, including SQL/NoSQL systems and lakehouse technologies (e.g., Databricks).
- Build efficient data access patterns and support scheduled or recurring processes for continuous monitoring, analytics, and insights generation.
Security, Risk & Compliance:
- Embed security, privacy, and compliance requirements into system design and implementation from the ground up.
- Enforce secure coding practices, identity and access controls, audit logging and data protection standards.
- Partner with risk, security, and compliance stakeholders to ensure solutions meet regulatory and internal policy requirements in a regulated environment.
- Contribute to architectural decisions that balance innovation, usability, and risk management in an enterprise context.
Collaboration & Continuous Improvement:
- Collaborate closely with product owners, audit stakeholders, designers, AI teams, data engineers and platform partners to deliver production‑ready solutions.
- Help shape technical roadmaps, influence prioritization of technical debt, and drive continuous improvement across the engineering lifecycle.
- Lead by example in adopting and promoting modern engineering practices, tools, and patterns.
Now Requirements / Qualifications / Skills: The posting includes "What We Value" (skills and behaviors) and "Education & Preferred Qualifications" and "Nice to Have". We need to decide which sections to include: Requirements, Qualifications, Skills. We have to include sections only when posting has real specific content. We have content for Qualifications (Education & Preferred Qualifications). Also we have "What We Value" which could be Skills. Also "Nice to Have" could be additional qualifications but maybe we can include under Qualifications or Skills. We need to avoid filler like "commensurate with experience". Not present.
We'll create:
- for any list of duties/requirements/benefits. So we can create a