Sign in
SkySlope logo

SkySlope

Active

Security Engineering Manager

System Domain LeadAI-native required

You’ve applied to SkySlope. The hiring team has asked you to take the next step here: an evaluation run by Evidal — a conversation about real work you’ve done, not a form. What you say goes to the hiring team as a structured read of your experience.

This isn’t a resume. It’s a conversation about real work you’ve done — not bullet points, not titles, not buzzwords. Every evaluation runs the same way, for everyone. Nobody is filtered out by keywords. Learn more ↗

Security Engineering Manager

Position Title: Security Engineering Manager Classification: Exempt Reports to: Director of Engineering Purpose: The purpose of the Security Engineering Manager is to build and lead SkySlope's dedicated security engineering team in pursuit of making life better for every real estate agent, broker and service provider. This is a player-coach role: they will design the security engineering program, own its execution, hire and grow the team that delivers it, and stay hands-on in the technical work throughout. SkySlope is making a significant, sustained investment in security engineering, and this role is the foundation of that investment. Why This Role: This is a genuine greenfield leadership opportunity. You are not inheriting someone else's program, tooling decisions, or org chart. You will design the program, pick the tools, hire the team, and set the standards, with direct executive sponsorship and a Director of Engineering who currently leads the security function and is invested in your success. SkySlope is also an aggressively pro-AI engineering organization: we treat AI as a security force multiplier for review, triage, and detection engineering, operating within guardrails you will help define. If you want to build a modern security program from first principles, with AI in the toolbox rather than on the threat slide, this is that role. Essential Functions Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Responsible for designing and executing SkySlope's security engineering program. Own the security roadmap across its major domains: identity and credential standards (short-lived, machine-identity-based credentials and OIDC federation), least-privilege authorization, secrets management, managed-device standards, attack-surface governance, secure SDLC (commit signing and org-wide SAST, dependency and secret scanning), centralized logging and detection, vulnerability disclosure, and AI governance. Sequence and prioritize the program pragmatically, targeting the highest risk reduction per unit of engineering effort first. Own the security-debt register: maintain security work as a visible, prioritized engineering backlog rather than an audit artifact. Own security tooling and vendor decisions, including evaluation, selection, and build-vs-buy judgment. Deliver clear, honest executive reporting on program status, risk posture, and progress. Responsible for hands-on technical leadership (player-coach). Lead and participate directly in architecture and design reviews for security-relevant work. Contribute hands-on where it matters most: proofs of concept, detection logic, automation, and reviews. Set and uphold the technical bar for security engineering work across the team. Responsible for hiring and growing the security team. Hire security engineers across levels and build an effective, collaborative team. Coach and mentor each direct report through personal and performance management, including growing an early-career engineer into a strong contributor. Build a team culture where security work is engineering work: shipped, measured, and iterated. Responsible for partnering across the organization. Work with DevOps, IT, and product engineering teams to embed security standards into how work already gets done — paved roads over gates. Communicate early and often, building trust between security and the rest of engineering. Ensure security guidance is concrete and actionable, not theoretical. Responsible for making AI a security force multiplier. Apply AI tooling to security review, triage, and detection engineering, and define the guardrails under which it operates. Shape SkySlope's AI governance standards in partnership with engineering leadership. Other Duties: Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee for this job. Duties, responsibilities and activities may change at any time with or without notice. All team members are always encouraged to think outside the box and pursue opportunities to go above and beyond their job description and baseline expectations, in order to make our customers' lives better. Measurables: Security program milestones defined, communicated, and delivered Security-debt register established and demonstrably burning down Team hired, retained, and growing (manager and peer observations) Quality and clarity of executive reporting Experience and Qualities: Strong senior/staff-level individual contributor background in security engineering, infrastructure engineering, or platform engineering; you have personally built the kinds of systems you will now lead Demonstrated ability to design and drive a security program or comparable cross-cutting technical initiative from ambiguity to delivery Working depth in modern cloud security practice: cloud IAM, credential federation, secrets management, secure SDLC, and detection/logging (we run multi-cloud: primarily AWS, a growing GCP footprint, and a small amount of Azure; depth in one cloud and fluency across the rest is fine) Strong coaching and mentoring skills, with a track record of growing engineers, including those early in their careers Sound judgment on tooling and vendor decisions, including knowing when to build and when to buy Clear, direct communicator with executives and with engineers, in writing and in person Enthusiasm for using AI as a working tool in security engineering; we want practitioners who are energized by this, not skeptical of it Pragmatism: bias toward risk reduction that ships over frameworks that impress We care about demonstrated ability, not certifications or credentials. If you've built and led this kind of work, we want to talk to you regardless of which letters follow your name.

Start

Pick a marker, or open a requirement from the list.

requiredstrongly preferred

What this role needsWhat you’ll be asked about.

Read it before you start, then open a requirement to see why this team asks for it and what kind of story lands.

Required experience

Be ready to discuss a real project for each — one project can cover several.

Every one of these comes up.

01Cloud security engineeringDesigning identity and credential standards, OIDC federation, least-privilege IAM, and secrets management across AWS primarily, with GCP and Azure coverage.

Why this team asks for it

The role owns the entire security program across multi-cloud environments; depth in cloud IAM, credential federation, and secrets management is required from day one.

Written by the hiring team for this role.

What to bring

A project you personally built.

  • What you built yourself.
  • What you decided, and why.
  • What you would do differently now.

Any of: AWS IAM · GCP IAM · Azure AD · cloud credential federation · OIDC · secrets management

02Secure SDLC and supply-chain controlsEmbedding security controls into the engineering delivery pipeline; evaluating and deploying tooling for static analysis, dependency scanning, and secret detection.

Why this team asks for it

Owning org-wide SAST, dependency and secret scanning, and commit signing is an explicit domain responsibility.

Written by the hiring team for this role.

What to bring

A project you personally built.

  • What you built yourself.
  • What you decided, and why.
  • What you would do differently now.
03Detection engineering and centralized loggingDesigning logging architecture, writing and iterating detection rules, triaging alerts, and applying AI tooling to detection.

Why this team asks for it

Centralized logging and detection are named program domains; hands-on detection logic contribution is explicit.

Written by the hiring team for this role.

What to bring

A project you personally built.

  • What you built yourself.
  • What you decided, and why.
  • What you would do differently now.
04Security program design and roadmap ownershipDefining program milestones, maintaining the security-debt register, prioritizing work across domains, and delivering honest executive reporting on risk posture.

Why this team asks for it

Building the program from greenfield, sequencing by risk-reduction-per-engineering-effort, and maintaining a visible security-debt backlog are the role's defining leadership axes.

Written by the hiring team for this role.

What to bring

A situation you were accountable for.

  • The situation, in specifics.
  • How you handled it.
  • Where it ended up.
05Security tooling and build-vs-buy judgmentEvaluating vendors, running proofs of concept, and making durable tooling decisions without over-investing in frameworks.

Why this team asks for it

Owning vendor selection and build-vs-buy decisions across the security stack is an explicit accountability.

Written by the hiring team for this role.

What to bring

A situation you were accountable for.

  • The situation, in specifics.
  • How you handled it.
  • Where it ended up.
06Engineering team hiring and developmentRecruiting security engineers, running performance management, and growing contributors through direct coaching and mentorship.

Why this team asks for it

Hiring the team from scratch and coaching engineers at all levels, including early-career, are explicit responsibilities tied to the role's measurables.

Written by the hiring team for this role.

What to bring

A situation you were accountable for.

  • The situation, in specifics.
  • How you handled it.
  • Where it ended up.

Strongly preferred experience

An example you can talk through is enough.

These come up when there is time — and “not yet” is a real answer.

07AI tooling applied to security workflowsUsing AI tools for code review augmentation, alert triage, detection logic generation, and defining guardrails for AI use in security contexts.

Why this team asks for it

Applying AI to security review, triage, and detection and shaping AI governance standards are explicitly called out as role responsibilities.

Written by the hiring team for this role.

What to bring

A workflow you use today.

  • What it does, step by step.
  • Where it falls short.
  • What you still do by hand.
08Executive and cross-functional security communicationWriting and delivering executive status reports, partnering with DevOps and product teams to embed actionable security guidance without creating gates.

Why this team asks for it

Clear executive reporting on risk posture and progress, and embedding security standards across DevOps, IT, and product engineering via paved roads, are explicit responsibilities.

Written by the hiring team for this role.

What to bring

A situation you were accountable for.

  • The situation, in specifics.
  • How you handled it.
  • Where it ended up.

The same requirements are listed in skill.md so your agent can prepare from them. Open skill.md ↗

How to prepare

  • Have a few real projects in mind that you were involved in and that connect to what this role needs.
  • Know the boundary of what you did — what you built, what your team built, what you inherited.
  • Bring the decision, not only the outcome: what you chose, and what you gave up.
  • Say plainly where something did not work. Honest limits read better than a clean story.

Ready to get started?One way to apply — with your AI agent.

With your AI agent

Give your agent this link and ask it to apply for you. It reads the instructions and takes it from there.

https://evidal.ai/api/v1/company/skyslope/roles/security-engineering-manager/skill.md

Or paste this into your agent:

Read https://evidal.ai/api/v1/company/skyslope/roles/security-engineering-manager/skill.md and apply to this role on my behalf. Use what you already know about my work, and ask me for anything you're missing.