Director of Software Applications Engineering

We need to output HTML fragment with sections: only include sections that have real specific content. We have: - Position Summary (prose) - Key Responsibilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - Travel Requirements (maybe a short paragraph) - Compensation & Benefits (salary range, bonus/incentive, equity, benefits) - Possibly "Inclusion" etc but that's boilerplate? The intro about inclusion is part of company description; but we should not include generic fluff? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusion statement is part of company values but not EEO? It's more about inclusion; but it's not a section heading. It appears in the intro paragraph. We can keep it as part of prose? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the inclusion statement as part of the prose maybe in a

. However the intro also has repeated sentences about over 50k customers etc. Those are duplicated lines? There's duplication: first paragraph repeats later. We should remove duplicated lines. Keep only one instance. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can choose headings that match content: we have Position Summary (maybe "About the role"), Key Responsibilities ("Responsibilities"), Required Qualifications ("Requirements" or "Qualifications"), Preferred Qualifications maybe also under Qualifications? Could combine? But instruction: Prefer a few substantive sections over many thin ones. Could have sections: About the role (summary), Responsibilities, Requirements (including required and preferred?), Benefits (including compensation and benefits), Travel (maybe Schedule? but travel is not schedule). There's no explicit schedule. Travel could be under "Schedule"? Not exactly. Travel Requirements is separate; we could put under a heading "Travel". But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those that apply. We have Pay (compensation) and Benefits. Travel maybe not needed as separate heading; could be included in a paragraph under About the role? But it's specific. Could create a "Schedule" section? Not appropriate. Better to include Travel as a paragraph under About the role? Might lose detail. However instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can create a section for Travel if we have content. But the allowed headings list does not include Travel; but we could still use a heading like "Travel" if not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can use other headings if appropriate. Safer to stick to those examples. Travel could be placed under "About the role" or maybe under "Responsibilities"? Not ideal. Could create a "Travel" heading as

Travel

- it's not in the list but likely acceptable. However to be safe, we could put Travel under a

after Responsibilities. We also have "Compensation & Benefits" which includes Pay and Benefits. Could split into Pay and Benefits sections. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation and benefits. So we can have

Pay

with salary range and bonus/incentive/equity. And

Benefits

with medical, 401(k) match, etc. We also have "Required Qualifications" and "Preferred Qualifications". Could combine into Requirements and Qualifications? The examples include Requirements and Qualifications separate. We could have

Requirements

for required qualifications, and

Qualifications

for preferred qualifications. Or we could have Required under Requirements and Preferred under Qualifications. That matches. We also have "Key Responsibilities" ->

Responsibilities

. Position Summary ->

About the role

. Now we need to remove duplicated lines, boilerplate, EEO, legal, application instructions. Also remove repeated "Over 50,000 customers globally..." duplication. Keep one instance. We need to preserve all substantive information: inclusion statement, company description, etc. We'll embed them in About the role paragraph. Let's extract content: Intro: "Over 50,000 customers globally trust our end-to-end, cloud-driven networking solutions. They rely on our top-rated services and support to accelerate their digital transformation efforts and deliver unprecedented progress. With double-digit growth year over year, no provider is better positioned to deliver scalable outcomes than Extreme. Inclusion is one of our core values and in our DNA. We are committed to fostering an inclusive workplace that embraces our differences and creates an atmosphere where all our employees thrive because of their differences, not in spite of them. Become part of Something big with Extreme! As a global networking leader, learn why there’s no better time to join the Extreme team." Then "Position : Director of Software Applications Engineering Department: Cloud Networking Engineering Reports To: Vice President, Cloud Networking Engineering Location: Hybrid – Salem, United States Full-Time" We should not repeat job title as heading; we can include metadata in a short

. So after About the role heading, we can have a paragraph with that metadata. Then "Position Summary Extreme Networks is looking for a Director, Software Applications Engineering to lead the teams that design, build, and operate the cloud-native applications, APIs, and middleware/data services powering our cloud networking platform. This leader owns the technical roadmap and delivery quality for application-layer services that sit above the network fabric — provisioning, orchestration, telemetry, analytics, and customer-facing management applications — and partners closely with product management, platform/infrastructure engineering, and customer-facing teams to ship reliable, secure, and scalable software at cloud scale. Reporting to the VP of Cloud Networking Engineering, this role balances hands-on technical leadership with people management, resourcing, and cross-functional influence." That's the summary. Then "Key Responsibilities" bullet list. Then "Required Qualifications" bullet list. Then "Preferred Qualifications" bullet list. Then "Travel Requirements Occasional travel (up to 10–15%) for team offsites, customer engagements, and company events." Then "Compensation & Benefits The base salary range for this role is [$ 190000 – $240000 USD], determined by geographic location, relevant experience, and qualifications, in compliance with applicable US pay transparency laws. This position is also eligible for bonus/incentive compensation, equity, and Extreme Networks' full benefits package (medical, 401(k) match, and more)." Then EEO boilerplate etc to remove. Also there is repeated paragraph about over 50k customers etc later; remove duplicate. Also there is "Extreme Networks, Inc. ( EXTR ) creates effortless networking experiences..." etc; that's boilerplate? Might be considered company description but could be kept? It's somewhat promotional but not required? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That paragraph is substantive? It's more marketing fluff but still part of posting. However earlier we already have similar content. Might be considered duplicate. Safer to keep only one instance of the company overview. We'll keep the first paragraph that includes over 50k customers etc and inclusion etc. Remove the later duplicate. Now craft HTML. Structure:

About the role

Over 50,000 customers globally trust our end-to-end, cloud-driven networking solutions. They rely on our top-rated services and support to accelerate their digital transformation efforts and deliver unprecedented progress. With double-digit growth year over year, no provider is better positioned to deliver scalable outcomes than Extreme. Inclusion is one of our core values and in our DNA. We are committed to fostering an inclusive workplace that embraces our differences and creates an atmosphere where all our employees thrive because of their differences, not in spite of them. Become part of Something big with Extreme! As a global networking leader, learn why there’s no better time to join the Extreme team. Position: Director of Software Applications Engineering, Department: Cloud Networking Engineering, Reports To: Vice President, Cloud Networking Engineering, Location: Hybrid – Salem, United States, Full-Time.

Then maybe another

for Position Summary? Could combine but better separate.

About the role

Over 50,000 customers globally trust our end-to-end, cloud-driven networking solutions. They rely on our top-rated services and support to accelerate their digital transformation efforts and deliver unprecedented progress. With double-digit growth year over year, no provider is better positioned to deliver scalable outcomes than Extreme. Inclusion is one of our core values and in our DNA. We are committed to fostering an inclusive workplace that embraces our differences and creates an atmosphere where all our employees thrive because of their differences, not in spite of them. Become part of Something big with Extreme! As a global networking leader, learn why there’s no better time to join the Extreme team.

Position: Director of Software Applications Engineering, Department: Cloud Networking Engineering, Reports To: Vice President, Cloud Networking Engineering, Location: Hybrid – Salem, United States, Full-Time.

Extreme Networks is looking for a Director, Software Applications Engineering to lead the teams that design, build, and operate the cloud-native applications, APIs, and middleware/data services powering our cloud networking platform. This leader owns the technical roadmap and delivery quality for application-layer services that sit above the network fabric — provisioning, orchestration, telemetry, analytics, and customer-facing management applications — and partners closely with product management, platform/infrastructure engineering, and customer-facing teams to ship reliable, secure, and scalable software at cloud scale. Reporting to the VP of Cloud Networking Engineering, this role balances hands-on technical leadership with people management, resourcing, and cross-functional influence.

Then Responsibilities:

Responsibilities

• Own the strategy, architecture, and execution roadmap for cloud applications, APIs, and middleware/data services supporting the cloud networking platform.
• Lead, hire, and develop multiple engineering teams (managers and individual contributors), setting clear goals, career paths, and performance expectations.
• Partner with Product Management and the VP of Cloud Networking Engineering to translate business and customer requirements into a prioritized, achievable technical roadmap.
• Drive engineering excellence: code quality, CI/CD practices, test automation, observability, and secure software development lifecycle (SSDLC) across all owned services.
• Ensure the scalability, availability, and performance of cloud applications and data services running in multi-tenant, multi-region cloud environments.
• Collaborate with Platform Engineering, SRE/Cloud Operations, Security, and Support teams to manage incident response, capacity planning, and service-level objectives (SLOs).
• Evaluate and evolve the middleware and data-services architecture (APIs, messaging, event streaming, data pipelines) to support new product capabilities and integrations.
• Manage departmental budget, vendor/tooling decisions, and resource planning in partnership with the VP.
• Represent Software Applications Engineering in executive reviews, planning cycles, and cross-org initiatives; communicate status, risks, and trade-offs clearly to senior leadership.
• Champion Agile/Scrum or similar delivery practices, continuous improvement, and a strong engineering culture across distributed teams.

Then Requirements:

Requirements

• Bachelor's degree in Computer Science, Software Engineering, or a related field (or equivalent practical experience).
• 12+ years of progressive software