Jobs · Information Technology · California

Senior Product Security Engineer

Verily Health · Mountain View, CA · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We have content: "Who We Are" description about Verily Health. That could be "About the role"? Actually "Who We Are" is about company. Could map to "About the role" maybe? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have description of role: "Verily is seeking an exceptional information security engineer to support our Information Security and Privacy Risk Management function." That's about role. Could put under

About the role

with paragraph. Responsibilities: bullet list. Qualifications: includes Minimum Qualifications and Preferred Qualifications. Could combine under

Qualifications

with paragraphs/lists. Skills: maybe separate? The posting includes "Strong knowledge of cloud security architecture, web application security, Vulnerability management, and security engineering." That's skill. Could be under Skills. Benefits: posting mentions "+ bonus + equity + benefits" but not specific benefits. It says "benefits" generically but not specific. The rule: do NOT create Benefits section unless posting actually states them. It only says "+ bonus + equity + benefits" but not enumerated. Likely not enough specific content. So omit Benefits. Pay: posting includes salary range: "The US base salary range for this full-time position is $165,500 - $185,500 + bonus + equity + benefits." That's pay info. So we can include Pay section with that paragraph. Schedule: not mentioned (full-time). It says full-time position. Could we consider schedule? It says full-time. That's schedule info. The rule: only create Schedule if posting actually states them. It says full-time. That's schedule. So we could include Schedule with "Full-time". However we need to avoid filler like "not specified". It's specified: full-time. So include. We must not include boilerplate like EEO, accommodation, etc. Remove those. We need to preserve all substantive information. So include company description, role description, responsibilities, qualifications (min and preferred), skills, pay, schedule. We must not repeat job title as heading. No Job ID. We must use

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

    for prose. We need to decide which content goes under which heading. Potential sections: - About the role: includes company description and role overview? Could be two paragraphs: company description (Who We Are) and role description. - Responsibilities: bullet list. - Qualifications: could have two sub-sections? But we only have heading Qualifications. Could include both Minimum and Preferred as paragraphs or lists. - Skills: maybe separate heading Skills for technical skills. - Pay: paragraph with salary range. - Schedule: paragraph with full-time. We must not create sections with filler. Ensure each heading has substantive content. Let's extract specifics. Company description: "Verily Health is a data platform and technology company purpose-built to power AI-enabled precision health solutions that accelerate research and improve care for individuals and communities. Uniquely positioned at the intersection of technology, data science, and healthcare, Verily transforms multimodal health data into insights, models, and actions that make healthcare more personalized, predictive, and precise." Role description: "Verily is seeking an exceptional information security engineer to support our Information Security and Privacy Risk Management function. The Information Security Engineer position combines a deep understanding of common information security technologies with a strong information security background. This individual will work closely with Verily’s Governance, Risk and Compliance team to ensure weekly/monthly/annual contractual compliance is established and maintained, especially as it relates to vulnerability management." Responsibilities bullet points (from text): - Manage tools and inputs that are part of the Vulnerability Management program. - Track remediation tasks, engage with systems/services owners and stakeholders to ensure vulnerability management compliance. - Ensure that regulator weekly/monthly reports are provided for continual FedRAMP certifications and/or necessarily remediations (e.g., POA&M). - Apply prior understanding and experience of federal government compliance (e.g., FISMA, FedRAMP) to regularly report on process and operational readiness. - Keep abreast of new threats and vulnerabilities, and validate the risk of reported threats using vulnerability management, scanning and red team operations. Qualifications Minimum: - BA/BS degree in Computer Science, Engineering, Management Information Systems. - 5 years of experience in the Information Security or related domain(s). - 3 years experience with NIST/FedRAMP compliance audits. - Strong knowledge of cloud security architecture, web application security, Vulnerability management, and security engineering. - Excellent written and verbal communication skills. Preferred Qualifications: - Experience with FedRAMP Moderate or higher. - Experience with GCP (preferred) or AWS, and also containerized environments (Kubernetes). - Experience with vulnerability management tools such as bug bounty programs, scanning and offensive security frameworks. - Qualified applicants must not require employer sponsored work authorization now or in the future for employment in the United States. Skills: Could be the strong knowledge etc. But we already have that under qualifications. Might duplicate. Perhaps we treat "Strong knowledge of cloud security architecture, web application security, Vulnerability management, and security engineering." as Skills. And maybe also list "Experience with GCP or AWS, containerized environments (Kubernetes)" as Skills. But to avoid duplication, we could put technical skills under Skills heading, and keep qualifications focusing on education/experience. Let's decide: - Qualifications: education, years experience, compliance audit years, communication skills. - Skills: technical skills: cloud security architecture, web application security, vulnerability management, security engineering, FedRAMP, GCP/AWS, Kubernetes, vulnerability management tools (bug bounty, scanning, offensive security frameworks). But we need to ensure we don't lose any info. Let's parse: Minimum Qualifications includes: BA/BS degree, 5 years experience, 3 years experience with NIST/FedRAMP compliance audits, Strong knowledge of cloud security architecture, web application security, Vulnerability management, and security engineering, Excellent written and verbal communication skills. Preferred Qualifications includes: Experience with FedRAMP Moderate or higher, Experience with GCP (preferred) or AWS, and also containerized environments (Kubernetes), Experience with vulnerability management tools such as bug bounty programs, scanning and offensive security frameworks, Qualified applicants must not require employer sponsored work authorization now or in the future for employment in the United States. Thus we could have:

    Qualifications

    with two sub-sections? But we only allowed headings from list; we cannot add custom headings like Minimum Qualifications. So we need to embed both minimum and preferred within Qualifications section, perhaps as paragraphs or lists. We could do:

    Minimum Qualifications:

    • ...

    Preferred Qualifications:

    • ...
    That's acceptable. Skills: maybe we could omit Skills heading because technical skills already covered under qualifications. But we have a heading Skills in allowed list; we could still include it if we have specific skill content not already covered. However to avoid duplication, we could still include Skills with the technical skills, but then we would be duplicating the strong knowledge etc. Might be okay but risk of duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but could be considered redundant. Better to avoid duplication but still preserve info. We could place technical skills under Skills and keep qualifications focusing on education/experience/communication/work auth. Let's see if we can split. Minimum Qualifications includes strong knowledge of cloud security architecture, web application security, Vulnerability management, and security engineering. That's a skill. Preferred includes experience with FedRAMP, GCP/AWS, Kubernetes, vulnerability management tools. Those are also skills. Thus we could put all technical skills under Skills heading, and under Qualifications we put education, years experience, compliance audit years, communication skills, work authorization requirement. Let's check if we lose any info: we still have all. Thus: Qualifications: - BA/BS degree in Computer Science, Engineering, Management Information Systems. - 5 years of experience in the Information Security or related domain(s). - 3 years experience with NIST/FedRAMP compliance audits. - Excellent written and verbal communication skills. - Qualified applicants must not require employer sponsored work authorization now or in the future for employment in the United States. Skills: - Strong knowledge of cloud security architecture, web application security, vulnerability management, and security engineering. - Experience with FedRAMP Moderate or higher. - Experience with GCP (preferred) or AWS, and also containerized environments (Kubernetes). - Experience with vulnerability management tools such as bug bounty programs, scanning and offensive security frameworks. That covers all. Now Pay: include salary range paragraph. Schedule: full-time. Now About the role: include company description and role description. Let's craft HTML. We must not include any extra text outside HTML fragment. We'll output:

    About the role

    Verily Health is a data platform and technology company purpose-built to power AI-enabled precision health solutions that accelerate research and improve care for individuals and communities. Uniquely positioned at the intersection of technology, data science, and healthcare, Verily transforms multimodal health data into insights, models, and actions that make healthcare more personalized, predictive, and precise.

    Verily is seeking an exceptional information security engineer to support our Information Security and Privacy Risk Management function. The Information Security Engineer position combines a deep understanding of common information security technologies with a strong information security background. This individual will work closely with Verily’s Governance, Risk and Compliance team to ensure weekly/monthly/annual contractual compliance is established and maintained, especially as it relates to vulnerability management.

    Responsibilities

    • Manage tools and inputs that are part of the Vulnerability Management program.
    • Track remediation tasks, engage with systems/services owners and stakeholders to ensure vulnerability management compliance.
    • Ensure that regulator weekly/monthly reports are provided for continual FedRAMP certifications and/or necessarily remediations (e.g., POA&M).
    • Apply prior understanding and experience of federal government compliance (e.g., FISMA, FedRAMP) to regularly report on process and operational readiness.
    • Keep abreast of new threats and vulnerabilities, and validate the risk of reported threats using vulnerability management, scanning and red team operations.

    Qualifications

    • BA/BS degree in Computer Science, Engineering, Management Information Systems.
    • 5 years of experience in the Information Security or related domain(s).
    • 3 years experience with NIST/FedRAMP compliance audits.
    • Excellent written and verbal communication skills.
    • Qualified applicants must not require employer sponsored work authorization now or in the future for employment in the United States.

    Skills

    • Strong knowledge of cloud security architecture, web application security, vulnerability management, and security engineering.
    • Experience with FedRAMP Moderate or higher.
    • Experience with GCP (preferred) or AWS, and also containerized environments (Kubernetes).
    • Experience with vulnerability management tools such as bug bounty programs, scanning and offensive security frameworks.

    Pay

    The US base salary range for this full-time position is $165,500 - $185,500 + bonus + equity + benefits.

    Schedule

    Full-time

    Check for any boilerplate: we omitted EEO, accommodation,

Similar jobs