Drimva

Kikoff

Senior Security Engineer, Data Security

$268K–$321K

San Francisco +1 · Senior · Full-time · Posted Sep 9, 2026

Location
San Francisco
San Francisco, California, United States
Experience
6+ years in security engineering.

About the job

Owns Kikoff’s data security strategy and roadmap, protecting sensitive data across cloud infrastructure, databases, analytics systems, and AI agents.

What you'll do

  • Design and implement data classification, access controls, encryption, tokenization, and secure data flows across AWS, Snowflake, RDS, and internal pipelines.
  • Build least-privilege access, audit logging, and data access monitoring; threat model new data flows and support privacy engineering for new markets and regulations.
  • Partner with Legal, Compliance, and Engineering to translate data-handling requirements into infrastructure and reusable secure practices.

What they ask for

  • 6+ years in security engineering with hands-on data security experience in encryption, tokenization, access control design, and key management.
  • Strong command of AWS security primitives, including IAM, KMS, S3 security, and VPC controls.
  • Experience securing Snowflake or a comparable data warehouse and production relational databases; experience designing and shipping access control systems.
  • Fluency in at least one automation language; hands-on infrastructure-as-code experience with Terraform or Pulumi; comfortable in a regulated environment.

Nice to have

  • Experience securing data access for AI/LLM systems and agentic workloads; tokenization at scale in fintech or payments.
  • Experience building audit logging and data access monitoring, privacy engineering depth, or a consumer fintech or financial services background.

Pay

$268,000 — $321,000 USD base salary

Tools

AWS, Snowflake, RDS, IAM, KMS, S3, Python, Go

AI focus

Define and enforce least-privilege access controls for AI agents; experience securing AI/LLM systems and agentic workloads is a bonus.

Model-written summary · the original posting is authoritative

First seen Oct 29, 2026 · Last verified Nov 4, 2026 (UTC)