Senior Security Engineer (Contract)

We need to output HTML fragment with sections: About the role? Actually we have "Who we are", "Why Worldwide", "What The Senior Security Engineer Does At Worldwide", "What You Will Do", "What You Bring To The Role", "Your Experience", "Promotion to the next level...", "At Worldwide Clinical Trials, we are committed to fostering an inclusive...". Also salary range. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings appropriately. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, no boilerplate. We need to remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. We need to output only HTML fragment. We need to decide which sections to include. Let's extract content: - Who we are: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Who we are" describing company. Could be placed under "About the role"? Might be better to have "About the role" for role description, and maybe "About the company" not a standard heading. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. We can also possibly omit some if not relevant. We have responsibilities: "What You Will Do" list. We have requirements/qualifications: "What You Bring To The Role", "Your Experience", plus certifications etc. We have skills: maybe list of specific skills. We have Pay: salary range. We have Benefits: mention "competitive benefits package depending on location". That's benefits. We have Schedule: not mentioned. We have About the role: maybe combine "Who we are" and "What The Senior Security Engineer Does At Worldwide". Could be a brief overview. We need to avoid boilerplate like "Perform other duties as assigned." That's generic; we can keep as part of responsibilities? It's generic but maybe we should remove as it's filler? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Also "Preserve ALL substantive information; do NOT invent or summarize away detail." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Perform other duties as assigned." is generic boilerplate; might be considered boilerplate. I'd consider removing it. Also "The duties and responsibilities listed above are representative of the nature and level of work assigned and are not necessarily all-inclusive." That's also boilerplate; remove. Also "Promotion to the next level is not automatic based on years of experience. Personnel are evaluated on proven competency, level of responsibility, and ability to work independently." That's maybe not boilerplate but could be considered generic HR statement; but it's substantive about promotion policy. Might keep? It's not a standard heading; we could fold into a paragraph under Requirements or Qualifications? It's about promotion; maybe we can include under a short paragraph after Qualifications. Also "At Worldwide Clinical Trials, we are committed to fostering an inclusive and equitable workplace by providing transparent compensation." That's boilerplate EEO? It's about inclusive workplace; could be considered boilerplate but it's about compensation transparency. Might keep as part of Benefits or Pay? It's about compensation transparency; could be included under Pay section. Also "We ensure pay equity and transparency and comply with all applicable labor laws." That's also boilerplate. Also "Salary information will be discussed during the interview process, and we encourage candidates to inquire about compensation at any stage." That's also generic. Also "We love knowing that someone is going to have a better life because of the work we do." That's fluff. Also "To view our other roles, check out our careers page at Discover a world of difference at Worldwide! For more information on Worldwide, visit www.Worldwide.com or connect with us on LinkedIn." That's navigation/application instructions; remove. Thus we need to extract substantive content: - Company description: "We’re a global, midsize CRO that pushes boundaries, innovates and invents because the path to a cure for the world’s most persistent diseases is not paved by those who play it safe. It is built by those who take pioneering, creative approaches and implement them with quality and excellence. We are Worldwide Clinical Trials, and we are a global team of over 3,500+ experts, bright thinkers, dreamers and doers and, together, we are changing the way the world experiences CROs – in the best possible way. Our mission is to work with passion and purpose every day to improve lives and we are looking for others who value this same pursuit." - Why Worldwide: "We believe everyone plays an important role in making a world of difference for patients and their caregivers. From our hands-on, accessible leaders, to our cohesive and supportive teams, we are committed to enabling professionals from all backgrounds and experiences to succeed. We prioritize cultivating a diverse and inclusive environment that continues to promote collaboration and creativity. We are proud to be a workplace where people thrive by being themselves and are inspired to do their best work every day." - Role overview: "Worldwide Clinical Trials is hiring a Senior Security Engineer to own and mature the Microsoft and Azure security capabilities that protect our identity, endpoint, cloud, and network environments. The primary focus is on Microsoft Entra ID and privileged access, Azure Key Vault, endpoint application control, and Microsoft Sentinel. As we advance our Zero Trust, cloud-native model, this role will engineer security services that need to be built well once and operated reliably for years. You'll be a senior individual contributor and the go-to subject-matter expert for your domains, partnering daily with Security Operations, Identity and Access Management, and application teams, and helping shape the engineering standards you work within rather than only executing against them." - Responsibilities (What You Will Do): list items: * The enterprise secrets-management service on Azure Key Vault. Provisioning, access governance, rotation and recovery, separation of duties, and lifecycle. Kept healthy and audit-ready as the environment grows. * Azure privileged-access controls end to end: RBAC, PIM, restricted administration, approvals, and access reviews, evolving them alongside IAM's Entra ID and Conditional Access direction to keep escalation risk low as the tenant scales. * Azure security baselines across tenants, subscriptions, and workloads including identity, logging and monitoring, network segmentation, encryption, and posture. Maintained and improved as new services come online. * The endpoint application-control and PowerShell-hardening capability, from standards and work instructions through exception handling and ongoing tuning, in partnership with endpoint engineering and application owners. * Developing Microsoft Sentinel detection and automation for privileged-access, Active Directory, and Azure high-risk events, growing the analytics and playbook library in step with Security Operations' runbooks and response processes. * Automation and Infrastructure-as-Code practices that make secure, policy-based configuration the default and reduce manual effort over time. * Technical direction for your services: design reviews, production-readiness and rollback standards, documentation, and the operational runbooks that let the wider team support what you build. - What You Bring To The Role (skills/qualifications): * Endpoint application control, PowerShell security, and code-signing depth. * Experience with Active Directory * Experience with Zscaler (ZIA, ZPA, or ZDX). * Experience in a GxP-regulated, clinical-research, healthcare, or pharmaceutical environment. * Microsoft AZ-500 or SC-300 certification; CISSP or CCSP a plus. - Your Experience: * Bachelor’s degree in Computer Science, Information Technology, or related field with a minimum of 5 years of experience in enterprise security engineering, with at least 2 years directly supporting Zscaler solutions or high school diploma/GED with a minimum of 7 years of experience in enterprise security engineering, with at least 2 years directly supporting Zscaler solutions. * Hands-on experience with ZIA, ZPA, and ZDX in a production environment. * Strong understanding of cloud security concepts, identity management, and Zero Trust principles. * Experience with automation for security operations and policy management using APIs. * Zscaler certifications (ZCCA-IA, ZCCA-PA, ZCCP) are highly desirable. - Promotion paragraph: "Promotion to the next level is not automatic based on years of experience. Personnel are evaluated on proven competency, level of responsibility, and ability to work independently." - Compensation transparency statements: maybe include under Pay. - Salary range: "The salary range for this position is annually (For hourly paid positions, the stated salary range reflects hourly rates): United States of America - $121,500.00 - $240,500.00" - Benefits: "In addition to base salary, we offer a competitive benefits package depending on location." We need to map to headings: - About the role: could combine company description + role overview? Or we could have "About the role" for role overview, and maybe "About the company" not a standard heading. Since only allowed headings are those listed, we might put company description under "About the role" as well, but that may be odd. However instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. Thus we need sections: - About the role: maybe a brief description of the role and company? Could include "Who we are" and "Why Worldwide" and role overview. - Responsibilities: the list of tasks. - Requirements: maybe combine "What You Bring To The Role" and "Your Experience"? But we also have Qualifications and Skills headings. We could split: Requirements for mandatory experience/education, Qualifications for certifications, Skills for specific technical skills. Let's decide: - About the role: company description + role overview. - Responsibilities: the bullet list. - Requirements: education + experience (Bachelor's degree or HS + years, Zscaler experience, etc.) - Qualifications: certifications (AZ-500 or SC-300; CISSP/CCSP a plus; Zscaler certifications highly desirable) maybe also GxP-regulated experience. - Skills: specific technical skills: Endpoint application control, PowerShell security, code-signing depth, Active Directory experience, Zscaler experience, cloud security concepts, identity management, Zero Trust, automation/IaC, etc. - Benefits: competitive benefits package depending on location. - Pay: salary range. - Schedule: not present, so omit. We also have promotion paragraph and compensation transparency statements; we could fold them into Pay or Benefits as a short paragraph. We must not include boilerplate like "Perform other duties as assigned." etc. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can reformat. We can keep the sentences as is, maybe split into

or

. We should not change meaning. Thus we need to copy the substantive sentences exactly (or close) into appropriate elements. Let's extract exact sentences: Company description: