SkySlope
ActiveSecurity 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 ↗
Pick a marker, or open a requirement from the list.
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 ↗
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.mdOr 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.