Manager, Software Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting: It includes sections: About Delinea (company description) maybe not needed? The posting includes "About Delinea" then "Summary" then "What You’ll Do" then "What You’ll Need" then "We’d Love To See" then "For this Job, Delinea is not considering candidates that need any type of US work authorization..." then "Why work at Delinea?" then core values, benefits etc. We need to map to headings: About the role (maybe summary), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Qualifications (maybe We’d Love To See?), Skills (maybe specific technical skills?), Benefits (Why work at Delinea? benefits), Pay (not mentioned), Schedule (not mentioned). So we should only include sections with actual content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Pay and Schedule omitted because not specified. We must not create sections with filler like "commensurate with experience". So we omit Pay and Schedule. Now we need to extract content for each. About the role: Could be the "Summary" paragraph: "This position is on the Fastpath Access Governance engineering team, where you will manage the team that designs, builds, and operates Delinea's application access governance product. Fastpath Access Governance helps customers manage segregation of duties risk, run user access reviews, automate compliant provisioning, and track changes across their business applications — so auditors and security teams can prove control over who has access to what. As an engineering manager you will oversee a team of engineers responsible for core Fastpath Access Governance development using .NET, RESTful APIs, and background workers, as well as the deployment and operation of those services in Kubernetes on Microsoft Azure. You will also oversee a team of specialists responsible for key integrations with ERP and business applications including Oracle, NetSuite, SAP, Microsoft Dynamics, Workday, and Salesforce. This role reports directly to the Engineering Director. Delinea is an AI-first engineering organization. Our engineers use AI tools every day to write and review code, build tests, and work through design problems, and we expect our managers to work the same way. You'll be hands-on with AI tools yourself and push your teams to get more out of them." That seems appropriate for About the role. Responsibilities: "What You’ll Do" bullet list: Manage a sprint team of software engineers — both the people and the work they deliver. Manage a team of integration specialists building and maintaining connectors to customer ERP and business applications. Own the technical roadmap, delivery, quality, and operational health of the Fastpath Access Governance services. Lead the effort to bring Fastpath Access Governance capabilities to the Delinea Platform natively. Partner with PM, UX, and Architecture in a Scrum model to shape requirements, propose technical solutions, and drive architectural decisions. Drive adoption of AI coding assistants, design tools, and test automation across your teams, and set the bar for what good AI-assisted engineering looks like. Build a team culture where engineers feel safe doing their best work and can grow their careers. We need to put each as

inside

. Requirements: "What You’ll Need": Bachelor’s or higher degree in Computer Science, Software Engineering, or a related field; 5+ years of experience managing Agile engineering teams, with a strong track record of delivery and team development; 5+ years of hands-on software development, with deep fluency in .NET/C# or comparable backend technologies; Strong technical skills with experience making architecture decisions in distributed systems; Experience building and operating cloud-native services on Azure or AWS at scale; Excellent communication and collaboration skills to effectively interact with engineers, product, and senior leadership; Experience using AI coding assistants (GitHub Copilot, Claude Code, or similar), AI design tools, and AI-based test automation in software development. We need to list as
• . Qualifications: "We’d Love To See": Background in identity governance (IGA), access management, or security software — experience with segregation of duties, access certification, or audit and compliance workflows is a strong plus; Hands-on experience building or integrating with ERP, HCM, or CRM systems (Oracle, NetSuite, SAP, Microsoft Dynamics, Workday, Salesforce) — particularly their APIs and permission models; Experience owning integrations with third-party systems at scale, where upstream APIs change and customer configurations vary; Experience scaling engineering teams in a fast-growing SaaS or enterprise software environment; Experience setting AI-first engineering practices at the team or org level: tooling standards, workflow integration, and measuring AI's impact on delivery outcomes; Depth in .NET and cloud-native development on Kubernetes and Azure; A track record of staying current with industry trends, security best practices, and emerging technologies in cloud-native platform development. These are qualifications/preferred. Skills: Could be extracted from the requirements and qualifications? But we already have Requirements and Qualifications. The instruction says we can have Skills section if there is real specific content. Could we separate out technical skills like .NET, Kubernetes, Azure, AI tools, etc. But we might combine them into Requirements and Qualifications. However we need to avoid duplication. Perhaps we can treat Requirements as mandatory, Qualifications as preferred, and Skills as maybe a summary of technical skills? But we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one? But they ask to use headings for sections like Requirements, Qualifications, Skills. We can include all three if they have distinct content. Let's see: Requirements list includes degree, years managing Agile, hands-on .NET, architecture decisions, cloud-native services, communication, AI coding assistants. Qualifications list includes IGA background, ERP/HCM/CRM integration experience, scaling teams, AI-first engineering practices, depth in .NET/K8s/Azure, staying current. There's some overlap but distinct enough. Skills: Could be a list of specific technical skills like .NET/C#, RESTful APIs, Kubernetes, Azure, AI coding assistants, etc. But those are already in Requirements. Might be redundant. Better to omit Skills if not distinct. Benefits: "Why work at Delinea?" includes: "We're passionate problem-solvers helping the world's largest organizations protect what matters most: their human and machine identities. We invest in people who are smart, self-motivated, and collaborative. What we offer in return is meaningful work, a culture of innovation and great career progression. At Delinea, our core values are STRONG and guide our behaviors and success: Spirited - We bring energy and passion to everything we do Trust - We act with integrity and deliver on our commitments Respect - We listen, value different perspectives, and work as one team Ownership - We take initiative and follow through Nimble - We adapt quickly in a fast-changing environment Global - We embrace diverse people and ideas to drive better outcomes We believe weaving these core values into our day-to-day actions, and our process for hiring, evaluating, and promoting employees, helps us cultivate a work environment that embraces collaboration and camaraderie. We take care of our employees. We offer competitive salaries, a meaningful bonus program, and excellent benefits, including healthcare insurance, as well as pension/retirement matching, comprehensive life insurance, an employee assistance program, time off plans, and paid company holidays." We need to extract benefits: competitive salaries, meaningful bonus program, excellent benefits including healthcare insurance, pension/retirement matching, comprehensive life insurance, employee assistance program, time off plans, paid company holidays. Also core values maybe not benefits but could be included. We'll put benefits as list. We must not include EEO, legal, etc. Also must not include the work authorization restriction (that's a requirement? It's a restriction: "For this Job, Delinea is not considering candidates that need any type of US work authorization now or in the future." This is a requirement (or a note). Should we include it? It's substantive info about eligibility. It's not boilerplate; it's a specific requirement. Should we include under Requirements? Probably yes as a requirement: "Must be authorized to work in the US without sponsorship" etc. But the instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This is not minor metadata; it's a requirement. So we should include it in Requirements. Also we must not include the "About Delinea" company description? That might be considered boilerplate? It's about the company, not the role. The instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Delinea" paragraph is company overview; it's substantive but maybe not needed for the role? However it's part of the posting. The instruction says to preserve ALL substantive information. So we should include it somewhere. Where? Could be under About the role? But About the role is about the role, not company. Perhaps we could add a section "About Delinea" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. So we need to fold that info into existing sections, maybe as a short paragraph under About the role or Benefits? The instruction: "fold minor metadata into a short

  or drop it." The company description is not minor metadata; it's substantive. But we don't have a heading for it. Could we include it as a

  before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside sections. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. So we can have prose paragraphs outside headings. So we can include a

    with the company description before the first heading. Thus structure:

    About Delinea ...

    then

    About the role

    with prose summary, then

    Responsibilities

    with
    , then

    Requirements

    with
    (including work auth restriction), then

    Qualifications

    with
    , then

    Benefits

    with
    . No Skills section if not distinct. We must ensure we don't include filler like "commensurate with experience". Not present. Now craft the HTML. We need to escape any HTML special characters? The text includes punctuation like em dashes, etc. Should be fine as plain text. Let's write:

    About Delinea Delinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamlessly govern their interactions across the modern enterprise. Leveraging AI-powered intelligence, Delinea’s leading cloud-native Identity Security Platform applies context throughout the entire identity lifecycle – across cloud and traditional infrastructure, data, SaaS applications, and AI. It is the only platform that enables you to discover all identities – including workforce, IT administrator, developers, and machines – assign appropriate access levels, detect irregularities, and respond to threats in real-time. With deployment in weeks, not months, 90% fewer resources to manage than the nearest competitor, and a 99.995% uptime, Delinea delivers robust security and operational efficiency without compromise. Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube. Join our passionate, global team at Delinea and help us make the world a safer and more secure place. Our success is driven by world-class product leadership,