SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Instructure is seeking a Senior Software Engineer to own Developer Experience—the systems every engineer at the company touches, including build and CI, source control and migration, deployment paths, and the data infrastructure that tracks ownership and deployment safety.
You will own two connected workstreams, both with designs and stakeholders but neither currently staffed:
1. Build the AI SDLC Pipeline: Stand up automated review across the pull request lifecycle, including risk-based triage that determines scrutiny level, security review backed by Instructure's global security tenets, quality review, and architecture review, all tied together with Slack integration. You'll build on top of internal tools already in production.
2. Embed Architecture, Security, and Quality Gates Across the SDLC: Extend the security deployment gate proven on one deploy surface to three others, ensuring no path to production can ship a known critical vulnerability regardless of pipeline. Wire the shared engineering data layer so architecture, security, and quality checks all read from one authoritative source. Fold in existing quality work so it reports through the same pipeline.
Key Responsibilities:
- Design and build the automated review pipeline with triage, security, quality, and architecture passes, including prompts, tooling, and evaluations that keep output trustworthy.
- Build and maintain deployment gates that block critical vulnerabilities across every deploy surface.
- Extend the shared data layer so any team can answer ownership, security, and quality questions about any repo on demand without one-off integrations.
- Instrument the pipeline: measure review turnaround, gate coverage, false positive rates, and cost per run, then act on findings.
- Build logging and audit layers that make AI-assisted and AI-delegated work reviewable after the fact.
- Partner with security, quality engineering, and platform teams to drive gate adoption; write docs and runbooks for self-service.
- Treat false positives and noise as first-class bugs; a gate teams route around isn't a gate.
Requirements:
- Five or more years building and operating CI/CD systems, developer tooling, or platform infrastructure.
- Hands-on depth in at least two of: Jenkins, GitHub Actions, or comparable pipeline systems, plus solid Git and GitHub API experience.
- Strong programming skills in a language used for tooling (Python, Go, TypeScript, or Ruby).
- Practical experience wiring security scanning into a pipeline, with clear judgment on where gates belong and when they should block.
- Comfort with data work: pulling from multiple sources, modeling it, and making it queryable for others.
- Experience building with large language models in production: agents or automated workflows, prompt design, tool use, and evaluating output quality.
- Track record of shipping tooling other engineers actually adopted, with judgment to recognize when adoption failed because the tool was wrong.
