Outtake
Software Engineer (Security)
New York City$160k–$265kfulltimemidAdded 2 weeks ago
About this role
Outtake is seeking a Software Engineer specializing in security to play a key role in developing their cloud infrastructure security. This position offers significant ownership over security functions and the opportunity to shape the security posture as the company grows.
What you'll do
- Establish the security framework for cloud infrastructure
- Enhance detection and response capabilities
- Manage secrets and access control architecture
- Collaborate with engineering for secure development patterns
- Integrate security measures as the platform evolves
- Be a pivotal team member shaping security functions
What they're looking for
- 3+ years in infrastructure security or operations
- Hands-on Kubernetes security experience
- Architecting D&R SIEM/SOAR systems
- Proficient in coding
- Incident response experience
- Understanding of security and developer experience tradeoffs
- Knowledge of AI/ML security is a plus
- Experience with endpoint security operations is a plus
Benefits
- 100% company-paid medical, dental, and vision
- Flexible PTO
- In-person team collaboration
- Annual company retreats
- Stunning waterfront office location
- Commitment to diversity and inclusion
Opens the official application on the employer’s site. No login required.
Outtake
Outtake builds an AI-driven platform focused on combating digital impersonation, fraud, and security threats through innovative cloud infrastructure solutions. The company is hiring Software Engineers across full-stack, platform, and security specializations, along with Sales Engineers who bridge technical expertise and customer relationships.
View all jobs at OuttakeLikely interview questions
- Walk us through your experience designing and operating secrets, credential, and access management systems. What challenges did you encounter and how did you solve them?
- Describe your hands-on experience with Kubernetes security. Have you implemented RBAC, network policies, or admission controllers in production, and what were the trade-offs you had to make?