Lead Digital Engineer

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. The posting includes About The Role (we can map to About the role). Responsibilities: Key Responsibilities section. Requirements: maybe Required Qualifications. Qualifications: maybe Preferred Qualifications? But we need to decide: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to include sections only when posting has real specific content. The posting includes "About The Role", "Key Responsibilities", "Required Qualifications", "Preferred Qualifications", "Technical Skills", "Core Competencies", "Why join Sonata Software?" (maybe not needed). Also includes "Job Title", "Experience", "Job type", "Location", "Level", "Function". Those metadata we can fold into a short

or drop. We should not repeat job title as heading. We should not put Job ID etc. We need to preserve all substantive information. Remove boilerplate like EEO etc. Also remove navigation/cookie etc. The posting includes a paragraph about Sonata Software at top; that's substantive about company; we could include maybe as a

before sections? Not required but we can include as intro. The instruction: "Prefer a few substantive sections over many thin ones." We could combine some. We need sections: About the role (we have About The Role). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (Technical Skills and Core Competencies). Benefits, Pay, Schedule: not present, so we should NOT include those sections. Thus output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the content from each section as is, but formatted. We need to be careful not to include boilerplate like "Sonata Software is an Equal Opportunity Employer..." etc. Remove that. Also remove duplicated lines. Let's extract content. First, intro paragraph about Sonata Software: "Sonata Software, with over $1.2 Billion Revenue, is a leading AI-first Modernization Engineering company, powered by our unique PlatformationTM framework. Our 6400+ AI Engineers are helping enterprises transform from systems to intelligent business platforms leveraging partner ecosystem to drive speed, efficiency and growth. Our bouquet of Modernization Engineering Services with AI -first approach cuts across Cloud, Data, AI, Dynamics, Test Automation, and Managed Services. Sonata’s AI-led modernization is enabled by a powerful suite of proprietary tools and assets. At the core is the Harmoni.AI Enterprise Platform, which includes Agent Bridge-a governance and observability framework; Agent Builder-a development toolkit for fungible agents integrated into enterprise systems; and the Agent Marketplace-an internal ecosystem for modular, reusable agents. Headquartered in Bengaluru, India, Sonata Software has a strong global presence, including key regions US, UK, India, Malaysia, Mexico, Australia, DACH (Germany/Switzerland) & Nordics (Finland). We are a trusted partner of Fortune 500 companies in Banking, Financial Services and Insurance; Healthcare and Lifesciences; Telecom, Media, and Technology; and Retail, Manufacturing and Distribution space." We can keep that as a

  before sections. Then metadata: "Job Title :Infrastructure Penetration tester Experience: 8+ years Job type :Contract Location :San Jose CA(Onsite from Day 1) Level: Senior Security Engineer / Senior Penetration Tester Function: Cybersecurity / Offensive Security". We can fold into a short

  maybe: "

  Job Title: Infrastructure Penetration Tester • Experience: 8+ years • Type: Contract • Location: San Jose, CA (Onsite from Day 1) • Level: Senior Security Engineer / Senior Penetration Tester • Function: Cybersecurity / Offensive Security

  ". Not a heading. Now About The Role section: The paragraph after that: "We are seeking an experienced Senior Infrastructure Penetration Tester to join our Offensive Security organization. The ideal candidate will have approximately 6+ years of hands-on penetration testing experience in large-scale technology environments and a strong understanding of enterprise infrastructure, cloud platforms, identity systems, networks, and modern attack techniques. In this role, you will conduct sophisticated security assessments across corporate infrastructure, cloud environments, data centers, production services, identity platforms, and internet-facing assets. You will work closely with infrastructure, cloud, engineering, security operations, and incident response teams to identify exploitable weaknesses and drive measurable risk reduction. The successful candidate should be comfortable operating independently, developing attack paths, chaining vulnerabilities, and communicating technical findings to both engineers and senior leadership." We'll put that in

  under

  About the role

  . Responsibilities: Under "Key Responsibilities" there are bullet-like paragraphs each starting with a bold heading? Actually the text: "Key Responsibilities Infrastructure Penetration Testing Plan and execute internal and external infrastructure penetration tests across large enterprise environments. Assess Windows, Linux, Unix, network, virtualization, container, and hybrid infrastructure. Conduct network, host, service, and application-layer security testing. Identify vulnerabilities and demonstrate realistic attack paths and business impact. Perform authenticated and unauthenticated penetration testing. Conduct lateral movement, privilege escalation, credential-access, and persistence assessments within authorized environments. Evaluate segmentation and security controls between corporate, production, R&D, cloud, and restricted environments. Assess security of common enterprise services including DNS, DHCP, VPN, SSH, HTTP/S, LDAP, Kerberos, SMB, RDP, databases, proxies, and authentication infrastructure. Active Directory & Identity Security Perform penetration testing of Active Directory and enterprise identity environments. Assess Kerberos, NTLM, LDAP, Group Policy, trusts, privileged accounts, service accounts, and delegation configurations. Identify paths to domain administrator and other high-value privileges. Evaluate identity federation, SSO, MFA, privileged access management, and service identities. Assess identity attack paths across hybrid environments such as on-premises Active Directory and cloud identity providers. Cloud & Modern Infrastructure Conduct penetration testing across AWS, Azure, and/or GCP environments. Assess cloud IAM, roles, policies, storage, compute, networking, APIs, secrets, and management interfaces. Test cloud-to-corporate and cloud-to-production attack paths. Assess Kubernetes, containers, Docker, service meshes, and cloud-native infrastructure. Identify privilege-escalation and lateral-movement opportunities across cloud environments. Evaluate infrastructure-as-code and configuration risks where applicable. External Attack Surface Perform continuous and point-in-time assessments of internet-facing infrastructure. Identify exposed services, misconfigurations, vulnerabilities, weak authentication, and attack paths. Conduct reconnaissance and attack-surface analysis using both commercial and open-source technologies. Validate findings from vulnerability scanners through manual exploitation and controlled testing. Assess perimeter security, WAFs, firewalls, VPNs, reverse proxies, CDN infrastructure, and other defensive controls. Adversary Simulation Develop realistic attack scenarios based on current threat actor techniques. Chain multiple weaknesses to demonstrate realistic compromise scenarios. Collaborate with Red Team, Purple Team, Detection Engineering, and Security Operations teams. Develop proof-of-concept exploits and attack automation where appropriate. Validate preventive and detective security controls. Translate offensive findings into actionable defensive improvements. Automation & Tool Development Develop scripts and tooling to improve penetration-testing efficiency and scalability. Automate reconnaissance, vulnerability validation, attack-path discovery, evidence collection, and reporting. Integrate offensive-security tooling into enterprise security workflows. Leverage Python, PowerShell, Bash, and other scripting/programming languages. Evaluate and responsibly use AI-assisted security testing tools while maintaining human validation and authorization controls. Reporting & Risk Management Produce high-quality penetration-testing reports that clearly communicate: Vulnerability Attack path Exploitability Business impact Affected assets Evidence Remediation recommendations Present findings to engineering teams, security leadership, and executive stakeholders. Work with infrastructure owners to validate remediation and perform retesting. Track recurring weaknesses and identify systemic security issues. Help establish security metrics such as remediation rates, exploitability, attack-path reduction, and risk exposure." We need to turn each of these into list items? The instruction: Use
  • for any list of duties/requirements/benefits. So we should treat each major bullet as a list item. However the content is not explicitly bullet list; it's paragraphs with headings. We could split by the headings: Infrastructure Penetration Testing, Active Directory & Identity Security, Cloud & Modern Infrastructure, External Attack Surface, Adversary Simulation, Automation & Tool Development, Reporting & Risk Management. Each heading followed by sentences. We could make each heading as a
  • with the description inside maybe as

    inside

  • ? But simpler: make each heading as a
  • and include the sentences as part of that
  • . Could also break into multiple
  • for each sentence but that would be too granular. We'll treat each section as a list item. Thus
    with
    • containing the heading bold? We'll just put plain text. We'll need to preserve all substantive information; we can keep the sentences as is. Thus:

      Responsibilities

      • Infrastructure Penetration Testing: Plan and execute internal and external infrastructure penetration tests across large enterprise environments. Assess Windows, Linux, Unix, network, virtualization, container, and hybrid infrastructure. Conduct network, host, service, and application-layer security testing. Identify vulnerabilities and demonstrate realistic attack paths and business impact. Perform authenticated and unauthenticated penetration testing. Conduct lateral movement, privilege escalation, credential-access, and persistence assessments within authorized environments. Evaluate segmentation and security controls between corporate, production, R&D, cloud, and restricted environments. Assess security of common enterprise services including DNS, DHCP, VPN, SSH, HTTP/S, LDAP, Kerberos, SMB, RDP, databases, proxies, and authentication infrastructure.
      • Active Directory & Identity Security: Perform penetration testing of Active Directory and enterprise identity environments. Assess Kerberos, NTLM, LDAP, Group Policy, trusts, privileged accounts, service accounts, and delegation configurations. Identify paths to domain administrator and other high-value privileges. Evaluate identity federation, SSO, MFA, privileged access management, and service identities. Assess identity attack paths across hybrid environments such as on-premises Active Directory and cloud identity providers.
      • Cloud & Modern Infrastructure: Conduct penetration testing across AWS, Azure, and/or GCP environments. Assess cloud IAM, roles, policies, storage, compute, networking, APIs, secrets, and management interfaces. Test cloud-to-corporate and cloud-to-production attack paths. Assess Kubernetes, containers, Docker, service meshes, and cloud-native infrastructure. Identify privilege-escalation and lateral-movement opportunities across cloud environments. Evaluate infrastructure-as-code and configuration risks where applicable.
      • External Attack Surface: Perform continuous and point-in-time assessments of internet-facing infrastructure. Identify exposed services, misconfigurations, vulnerabilities, weak authentication, and attack paths. Conduct reconnaissance and attack-surface analysis using both commercial and open-source technologies. Validate findings from vulnerability scanners through manual exploitation and controlled testing. Assess perimeter security, WAFs, firewalls, VPNs, reverse proxies, CDN infrastructure, and other defensive controls.
      • Adversary Simulation: Develop realistic attack scenarios based on current threat actor techniques. Chain multiple weaknesses to demonstrate realistic compromise scenarios. Collaborate with Red Team, Purple Team, Detection Engineering, and Security Operations teams. Develop proof-of-concept exploits and attack automation where appropriate. Validate preventive and detective security controls. Translate offensive findings into actionable defensive improvements.
      • Automation & Tool Development: Develop scripts and tooling to improve penetration-testing efficiency and scalability. Automate reconnaissance, vulnerability validation, attack-path discovery, evidence collection, and reporting. Integrate