Senior Security Engineer, AI/ML

We need to output HTML fragment with sections: About the role? Actually we have sections: Company Overview, Position Overview, Key Responsibilities (with subparts Build, Break, Lead & Communicate), Required Qualifications, Preferred Qualifications, Our Work Environment, Why Join Us? Also Pay (salary range) and Benefits (mention benefits). We need to use

for section headings. Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — none present. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out "Qualys is an Equal Opportunity Employer, please see our EEO policy." Also maybe "Please note this range reflects base salary..." is part of Pay section but we can keep as prose. Also "We also offer a comprehensive and highly competitive benefits package." is part of Benefits. We need to preserve all substantive information. So we need to include sections: About the role? The posting has "Company Overview", "Position Overview". Could combine? But we need headings only when there is real specific content. So we can have headings: Company Overview, Position Overview, Responsibilities (maybe split into Build, Break, Lead & Communicate as subheadings? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those generic headings. But we can also have subheadings? Not specified; we can just use

  for main sections. Within Responsibilities we can have

  • items. For Build, Break, Lead & Communicate we could embed as part of list items with description. Or we could make subheadings using

    ? Not allowed? Only said use

    for section headings (list). It didn't forbid other headings, but safer to stick to

    for sections and use

    or

    • for content. Thus sections: Company Overview, Position Overview, Responsibilities, Requirements (maybe split into Required Qualifications and Preferred Qualifications? Could combine into Requirements). Benefits, Pay. Possibly also Work Environment and Why Join Us could be part of Benefits or separate? But we have headings list includes Benefits, Pay, Schedule. Not Work Environment. However we must include all substantive info; we could incorporate Work Environment and Why Join Us into a section like "About the team" or "Culture". But the instruction says prefer a few substantive sections over many thin ones. Could create a section "Work Environment & Culture". But they didn't list that as example; but we can still use

      for any section heading, not limited to those examples. The examples are just examples. So we can create headings like "Work Environment", "Why Join Us". That's fine. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and benefits package, so we can include Pay and Benefits sections. Schedule not mentioned, so omit. We need to remove duplicated lines. Ensure no filler like "commensurate with experience". Not present. Now craft HTML. We'll start with

      Company Overview

      then

      ...

      . Company Overview text: "Come work at a place where innovation and teamwork come together to support the most exciting missions in the world! Qualys is a leading provider of cloud-based security and compliance solutions, processing vast amounts of data to help our global customers secure their networks, devices, and applications. With a strong focus on innovation and scale, Qualys empowers organizations to achieve continuous security and compliance through real-time visibility and analytics. As we continue to grow, we are looking for passionate and skilled professionals to join our mission in redefining the future of cybersecurity." We can keep that as prose. Next

      Position Overview

      then

      ...

      containing the position overview paragraph. Position Overview: "We are seeking a Senior Security Engineer – AI/ML who sits at the intersection of hands-on AI/ML engineering and offensive security research. You will both build and break: designing and deploying GenAI and agentic systems that power next-generation threat detection, while red teaming those same systems to uncover prompt injection exploits, adversarial inputs, model manipulation, and other emerging AI threats. This is a senior, dual-mandate role for an engineer who is equally comfortable orchestrating multi-agent pipelines and RAG architectures as they are tearing them apart to find weaknesses. You will set the technical bar for secure-by-design AI at Qualys, mentor other engineers, and translate research into production hardening strategies." Next

      Responsibilities

      then
      • items. We need to capture Build, Break, Lead & Communicate sections. Could make each as a list item with sub-bullets? But we can just have list items each containing a paragraph describing the responsibilities. Could embed subheadings inside
      • using maybe. But we must not invent headings inside? It's okay. We'll create list items: - Build: Build and deploy GenAI applications using LangChain, LlamaIndex, or similar frameworks, and orchestrate agentic AI workflows with tools such as AutoGen, CrewAI, or custom agent-based architectures. Design, train, and evaluate ML models from scratch, spanning both classical ML and deep learning, and develop end-to-end pipelines for ingestion, preprocessing, training, evaluation, and deployment. Implement and optimize RAG pipelines using embeddings and vector databases (e.g., FAISS, Pinecone, Qdrant), with security and data-leakage controls built in from the start. Write robust backend APIs in Python to serve models, process data, and integrate with cloud infrastructure; monitor model performance, latency, and accuracy in production and iterate continuously. - Break: Conduct in-depth research on security vulnerabilities in LLMs and AI systems, including prompt injection, jailbreaks, data leakage, model theft, and adversarial attacks. Design and execute offensive security assessments and red teaming campaigns against GenAI and ML-powered systems, including the agentic pipelines built in-house. Identify and classify novel threat vectors targeting model inference, training pipelines, and model-serving architectures. Contribute to and build internal tooling for scanning, fuzzing, and automating LLM vulnerability discovery. - Lead & Communicate: Collaborate cross-functionally with product and engineering teams to design secure AI-powered features and define hardening strategies. Develop proof-of-concepts, technical whitepapers, or blog posts on emerging threats and best practices; monitor threat intelligence and academic research on AI model security and supply chain risks. Represent Qualys in security and AI research communities through speaking, publishing, or standardization efforts, and mentor engineers on secure AI development. Next

        Required Qualifications

        then
        • items. List each bullet: - 6+ years of combined experience across software engineering / machine learning and security research, penetration testing, or exploit development, with a focus on application or cloud security. - Strong programming skills in Python, including building APIs and backend components, plus scripting and automation for testing and PoC development. - Experience training ML models using Scikit-learn, TensorFlow, or PyTorch, and a strong working knowledge of LLM architectures (transformers, embeddings, fine-tuning, RAG). - Hands-on experience with LangChain, LlamaIndex, or other GenAI frameworks, and with building multi-agent or autonomous AI workflows. - Familiarity with GenAI-specific risks such as prompt injection, model evasion, hallucination-based exploits, data leakage, or model theft, and with LLM deployment scenarios (e.g., OpenAI, HuggingFace, custom-hosted models) and their threat surfaces. - Ability to analyze logs, API interactions, inference responses, and prompt chains to identify anomalous or risky behavior. - Working knowledge of SQL, Pandas, and large-scale data processing, with experience developing and deploying ML systems in Agile environments. - Strong analytical mindset, excellent technical writing skills, and familiarity with responsible disclosure practices, bug bounty programs, or security research ethics. Next

          Preferred Qualifications

          then
          • items. List: - Background in AI/ML security red teaming or adversarial ML. - Knowledge of vector database risks, insecure RAG pipelines, model fingerprinting, and AI model supply chain attacks. - Experience using or contributing to tools such as AutoGen, CrewAI, MetaGPT, Guardrails.ai, LLM Guard, or Tracer. - Familiarity with LLMs such as GPT-4, Claude, Mistral, LLaMA, or Falcon, and integrating them via APIs. - Experience with cloud platforms (AWS, GCP, Azure), containerized deployments, and MLOps tooling for monitoring, retraining, and CI/CD automation. - Familiarity with Secure SDLC and threat modeling frameworks (e.g., STRIDE, MITRE ATLAS) and AI-specific security checklists. - Publications or presentations at conferences such as Black Hat, DEF CON, USENIX, NeurIPS, or OWASP, and contributions to AI/ML projects in security, compliance, or enterprise applications. Next

            Work Environment

            then

            maybe bullet list? The text: "Collaborative & Transparent: We use virtual collaboration and pairing tools to share ideas openly. Siloed work is discouraged — teamwork is our strength. Agile & Flexible: We focus on delivering incremental value, adapting processes only when they serve our goals. Diverse & Inclusive: We believe in building teams with diverse perspectives, which fuels creativity and innovative problem-solving. People-Focused: Our people are our most valuable asset. We invest in personal growth and align individual strengths to company objectives." We could make a

            • for each bullet. Let's do that. Next

              Why Join Us?

              then
              • items. List: - Leadership Impact: Help drive a security-first culture and shape the defense landscape of next-generation AI systems at global scale. - Cutting-Edge Technology: Build and harden real-world LLM, GenAI, and agentic systems on scalable, cloud-native infrastructure. - Professional Growth: Access broad resources, mentorship, certifications, and exposure to cutting-edge research. - Inclusive Culture: Join a team that values diverse thinking, critical research, openness, and continuous improvement. - Competitive Compensation: We offer a comprehensive benefits package, including healthcare, retirement plans, and more. The salary range for this position is $115,000 - $140,000 per year. Final compensation will be determined based on several factors, including but not limited to skills, relevant experience, and work location. Please note this range reflects base salary and does not include incentive compensation or potential equity grants. We also offer a comprehensive and highly competitive benefits package. But we have separate Benefits and Pay sections; maybe we should split compensation and benefits. The instruction says to include Pay and Benefits sections only if posting actually states them. It does state salary range and benefits package. So we could have Pay section with salary range details, and Benefits section with description of benefits package. The "Why Join Us?" includes Competitive Compensation bullet that mentions benefits and salary; we could move that to Pay/Benefits sections and keep Why Join Us focusing on other aspects (Leadership Impact, Cutting-Edge Technology, Professional Growth, Inclusive Culture). However the bullet also mentions Competitive Compensation; we could keep it but then duplicate. Better to separate: Keep Why Join Us with Leadership Impact, Cutting-Edge Technology, Professional Growth, Inclusive Culture. Then Pay section with salary range details. Benefits section with description of benefits package. Thus adjust Why Join Us bullets accordingly (remove Competitive Compensation). We'll keep four bullets. Now Pay section:

                Pay

                then

                with salary range and note. Benefits section:

                Benefits

                then