Threat Level: green Handler on Duty: Brad Duncan

SANS ISC: InfoSec Jobs InfoSec Jobs

Participate: Learn more about our honeypot network
https://isc.sans.edu/honeypot.html

Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!
Sr. Staff Software Engineer, Security
Company Slack
Location San Francisco, CA
Preferred GIAC Certifications GSEC
Travel 0%
Salary Competitive
URL https://slack.com/careers/2100405/sr-staff-software-engineer-security
Contact Name Scott Nelson Windels
Contact Email swindels/at/slack-corp.com
Expires 2020-08-12

Job Description

Our Security team supports the unwritten fourth tenet of Slack’s mission: make people’s working lives more secure. We’re serious about protecting our infrastructure, operations, and most importantly, our customers’ data. We take a systemic approach to security and strive to ensure that we provide low friction high-impact security across everything we do. We’re looking for a senior developer to help lead our Security Engineering team. Significant in-field experience is a hard requirement but an interest in software development outweighs all.

We’d like you to have the vision to identify areas where we can fundamentally make Slack more secure, then propose, build and operate tools to see that to fruition. The role includes noteworthy autonomy towards defining problem spaces and a mandate to build viable tools that are both internally and externally facing. While we don’t ascribe to the “architect” title, this role is to step into an existing team, learn what we do, and to be a technical lead, working closely with our team. This is the team which wrote Nebula and go-audit; we look forward to what we can build with your ideas.

A significant part of this job is meant to attract a multidisciplinary engineer; you probably feel skeptical of any job posting with the word “DevOps” in it, but that (or even SecDevOps) is your day to day. We would ask for your help in evaluating tooling pragmatically—particularly when the right time is to spend some money or when months of development would be advantageous. Critically weighing the tradeoffs of using an AWS higher level service versus writing our own is a base expectation.

Slack has a positive, diverse, and supportive culture—we look for people who are curious, inventive, and work to be a little better every single day. In our work together we aim to be smart, humble, hardworking and, above all, collaborative. If this sounds like a good fit for you, why not say hello?