pythongoawsstartupapplication securitypenetration testingoffensive securitycloud securityred teamingai securityidentity and access
Вакансия из Hirify Global, списка международных tech-компаний Для мэтча и отклика нужен Plus
Пожаловаться
Зарплата и рынок
ЗП не указанаразвернуть
На похожих ролях по рынку
$193к$225кмедиана$270к
48 в выборке
На СНГ рынке: $3.9к/мес ($3.4к - $5.5к)
89
Крутая вакансия
развернуть
Чётко очерченная роль первого специалиста по безопасности даёт широкую ответственность за AI-, облачную и прикладную безопасность в стартапе с сильными инвесторами, но предполагает высокую личную нагрузку и постоянную работу в офисе.
?Большая ответственность
Безопасность AI
Сильные инвесторы
Только офис
Мэтч & Сопровод
Для мэтча с этой вакансией нужен Plus
Подключить Plus
Описание вакансии
Текст:
Hirify AI/Оригинал
TL;DR
Security Engineer (AI): Building security capabilities for an agentic enterprise pricing platform with an accent on offensive security, AI/LLM security, cloud infrastructure, and multi-tenant data protection. Focus on red-teaming AI agents, hardening AWS and identity controls, securing software supply chains, and leading incident response and security programs.
Location: San Francisco, United States; onsite
Company
hirify.global is building PQA (Prompt, Quote, Approve), an agentic enterprise platform intended to replace traditional CPQ software with a data model reflecting real-world pricing.
What you will do
Continuously assess the application, cloud infrastructure, identity systems, and software supply chain, producing risk assessments and partnering with engineering on remediation.
Red-team AI agents for prompt injection, tool abuse, and cross-tenant data leakage, and help design defenses.
Track vulnerabilities, attack techniques, breaches, and security tooling; publish a weekly security brief with analysis, investment recommendations, CTO decisions, and engineering actions.
Represent security in customer reviews with CISOs and security teams and build relationships across the security community.
Act as the first technical responder for security incidents, lead post-incident fixes, and own internal red-team exercises, external penetration-test scoping, and a future bug bounty program.
Provide technical security input for compliance controls, penetration-test evidence, and incident-response testing without owning audits or questionnaires.
Requirements
Strong offensive security background in penetration testing, red teaming, vulnerability research, or exploit development.
Senior or Staff-level security engineering experience, ideally at a SaaS company handling sensitive B2B data; exceptional earlier-career candidates may be considered with evidence such as published CVEs, recognized research, top CTF results, or meaningful bug bounty history.
Hands-on depth in at least two of application security, AWS cloud security, identity and access, or AI/LLM security.
Strong coding ability, including writing proof-of-concept exploits and helping ship fixes.
Close ongoing engagement with the security field.
Clear writing and communication with engineers, executives, and external CISOs.
First-year focus includes just-in-time customer data access, multi-tenant isolation across Postgres, the CDC pipeline and agent context, Salesforce credentials and non-human identities, Python and Go software supply-chain security, AI coding-agent guardrails, and AWS IAM, network segmentation, and secrets management.
Nice to have
Experience as the first or an early security hire at a startup.
Existing relationships with CISOs, researchers, or security conferences.
Interest in building and leading a security team over time.
Culture & Benefits
Full-time, in-office work in FiDi, San Francisco, as part of the founding engineering team.
Medical, dental, and vision benefits for the employee and family.
Lunch, dinner, snacks, and coffee provided.
Take-what-you-need vacation policy.
Будьте осторожны
Если работодатель просит войти в их систему, используя iCloud/Google, прислать код/пароль, запустить код/ПО, не делайте этого. Это мошенники. Обязательно жмите «Пожаловаться» или пишите в поддержку. Подробнее в гайде →