Lead Engineer II - F5 Technical Lead/SME

We need to output HTML fragment with sections: About the role? The posting includes intro about KPMG and role description. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to decide what sections to include. Content: - Intro paragraph about KPMG being great place to work, etc. Could be "About the role" or maybe "About KPMG"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" containing the introductory description about KPMG and the role. - Responsibilities: list of bullet points under "Responsibilities:" heading. - Qualifications: list under "Qualifications:" heading. - Benefits: there is mention of benefits package, medical, dental, vision, disability, life insurance, 401(k), personal well-being, PTO, holidays, breaks. Also mention "Total Rewards package includes ...". So we can have Benefits section. - Pay: there is mention of salary ranges, link to pay transparency, statement about complying with local/state regulations regarding displaying salary ranges. It says "If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed." No actual numbers given. It says "KPMG offers a comprehensive compensation and benefits package." But no specific pay figure. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since pay is not specified with numbers, but they mention salary ranges and link. Is that considered stating them? It says they comply with displaying salary ranges if required, and provide a link. There's no actual range given. This might be considered placeholder? The instruction says never create Pay section unless posting actually states them. Since they didn't give actual numbers, but they mention that ranges are displayed via URL. I'd argue that is stating that salary ranges exist and can be found via link. However, the rule says avoid filler like "commensurate with experience". This is more like they provide a link to see ranges. I think we can include Pay section with a note that salary ranges are available via link. But we must not invent details. We can include a

stating that salary ranges are available via the provided link (the URL). That is preserving info. - Schedule: there is mention of standard work hours, PTO, holidays, breaks. It says "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." That's schedule-related info (work hours, PTO, holidays). So we can include Schedule section. - Skills: Not explicitly listed as a separate section; qualifications cover skills. Could combine qualifications and skills? But we have Qualifications heading already. Could also have Skills heading if there is explicit list of skills. The qualifications include many technical skills. Might be better to keep Qualifications and maybe not have Skills separate to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. Or we could have Qualifications and Skills separate if there is distinct content. The qualifications list includes experience, education, certifications, mastery, expertise, proficiency, track record, authorization. That's more qualifications than skills. Skills could be implied but not separate. I'd omit Skills section to avoid thin. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't repeat job title as heading. The job title is "Associate Director, Network Engineer – F5 Technical Lead". We should not put that as heading. We need to strip boilerplate: EEO statements, visa sponsorship details? The visa sponsorship info is substantive? It says "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)". That is a requirement about work authorization. Should we keep it? It's part of qualifications/requirements. It's substantive. We'll keep it within Qualifications. We need to remove duplicated lines, navigation, legal, EEO, scam-warning, application instructions like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc. Also remove the Los Angeles County applicants section? That seems like legal boilerplate about fair chance. Might be considered EEO/legal. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the Los Angeles County applicants section and the EEO statements. Also remove the link to benefits & how we work? That's part of benefits info; we can keep benefits description but maybe drop the link? The link is "Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." That's a reference; we could keep it as part of benefits description but it's not essential. Might keep as a sentence. Also remove the link for salary ranges? We need to keep the info about salary ranges being available via link. The link is provided: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6682_9_26. We can keep that. We must not include markdown code fences. Output only HTML fragment. Let's craft:

About the role

Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others. If you're as passionate about your future as we are, join our team. KPMG is currently seeking an Associate Director, Network Engineer – F5 Technical Lead to join our Digital Nexus organization.

Responsibilities

• Serve as the Subject Matter Expert (SME) and lead architect for enterprise-wide F5 Application Delivery Controller (ADC) platforms, defining strategic roadmaps, modernization initiatives, capacity planning, and multi-datacenter disaster recovery (DR) architectures
• Design and implement high-performance global and local load balancing (GLB), traffic steering, content switching, and custom programmatic traffic policies utilizing advanced iRules and iRulesLX across multi-region environments
• Architect, deploy, and manage comprehensive F5 security solutions including Advanced WAF (AWAF/ASM), AFM, APM, Bot Defense, and DDoS Protection partnering with cybersecurity teams to enforce Zero Trust and robust application defense
• Drive DevOps integration by developing automated provisioning, configuration management, and self-service deployment frameworks using Python, Ansible, Terraform, PowerShell, and REST APIs
• Establish operational standards, lead firmware/lifecycle management, and resolve complex enterprise incidents through deep root cause analysis across TCP/IP, SSL/TLS, routing, DNS, and authentication flows
• Provide senior engineering leadership, mentor cross-functional network and application teams, lead technical design reviews and technology assessments, and serve as the primary escalation point for mission-critical platform events
• Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment

Qualifications

• Minimum eight years of recent experience in enterprise network engineering, with a minimum six years of dedicated F5 engineering and architecture in large-scale, high-availability environments (experience in highly regulated sectors like financial services or healthcare preferred)
• Bachelor's degree from an accredited college or university is preferred; minimum of a high school diploma or GED is required; advanced technical certifications are strongly preferred, such as F5-CSE, F5-CTP, F5-CA, CISSP, CCNP Enterprise, or CCIE Enterprise Infrastructure
• Expert-level mastery across the F5 ecosystem, including BIG-IP (LTM, DNS/GTM, APM, ASM/AWAF, AFM), BIG-IQ, next-gen hardware architectures (VELOS, rSeries, iSeries, VIPRION), and F5OS
• Comprehensive expertise in core networking protocols and enterprise security architectures, including BGP, TCP/IP, DNS, HTTP/HTTPS, SSL/TLS, routing & switching, as well as implementing Zero Trust frameworks and enterprise WAF/DDoS mitigation
• Demonstrated hands-on proficiency in network automation and modern provisioning workflows using Python, Ansible, Terraform, Git, REST APIs, and Infrastructure-as-Code (IaC) practices, with familiarity in Kubernetes ingress/service mesh or multi-cloud networking
• Proven track record in strategic technology planning, high-stakes problem resolution, architecture documentation, risk mitigation, and executive-level cross-functional communication to lead major migrations and mentor engineering teams
• Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)

Benefits

• Comprehensive, competitive benefits package including medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support mental health
• Personal Time Off per fiscal year based on job classification, standard work hours, and years of service
• Annual holiday calendar and two additional breaks each year (year‑end and around July 4th) where eligible employees are not required to use Personal Time Off
• Additional details about benefits can be found on the KPMG US Careers site at Benefits & How We Work

Pay

KPMG complies with local/state regulations regarding displaying salary ranges. Salary ranges for this role are available via the pay transparency link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=6682_9_26. Compensation is determined based on skills, responsibilities, experience, degrees, certifications, and market considerations.

Schedule