Original listing text, shown exactly as published by the company.
Qualifications
Required
- 5+ years in Solutions Engineering, Technical Account Management, DevOps, Platform Engineering, or similar technical roles.
- Strong hands-on expertise in:
- Docker and container ecosystems
- Secure software supply chain practices
- CI/CD pipelines and modern cloud-native architecture
- Experience designing and executing structured PoCs with defined success criteria.
- Ability to present complex technical topics clearly to senior engineering audiences.
- Strong written communication skills; experience producing technical blogs or deep technical content.
Preferred
- Hands-on experience with AI/ML development workflows, including model packaging, dependency management, reproducibility, and governance considerations within containerized environments.
- Practical Experience with AI coding agent runtimes and sandboxed execution environments (e.g., agent isolation, MCP tool governance)
- Familiarity with Docker SBX and MCP Gateway as enterprise controls for agentic AI workloads
- Familiarity with secure software supply chain practices, including SBOM generation and consumption, artifact signing, provenance (e.g., SLSA concepts), vulnerability management, and policy enforcement.
- Deep understanding of the container image lifecycle, including build optimization, image hardening, base image strategy, registry governance, promotion workflows, and lifecycle management from development through production.
- Practical experience implementing or advising on Secure Software Development Lifecycle (SSDLC) practices, including secure build pipelines, policy-as-code, compliance controls, and DevSecOps integration.
- Exposure to governance frameworks or regulatory models impacting modern development environments (e.g., NIST guidance, EU AI Act, internal enterprise policy frameworks).
- Experience designing reusable lab environments, demo frameworks, or reference architectures for engineering audiences.
- Background in Platform Engineering, DevSecOps, or Security Architecture roles where architectural decisions directly influenced developer experience and risk posture.
What to ExpectFirst 30 Days – Technical Immersion & Signal Mapping
- Primary Goal: Build product mastery, understand recurring customer friction patterns, and identify high-leverage enablement opportunities.
- Deeply immerse in Docker platform capabilities across security, supply chain, governance, and developer workflows, with particular focus on AI Gov and MCP Gateway as emerging customer conversation areas ahead of GA.
- Review existing CXE, SE, and Post-Sales materials to identify:
- Common architectural blockers
- Repeated SE/SA escalation themes
- Gaps in advanced technical documentation
- Shadow live enablement sessions and recent PoCs to understand maturity gaps.
- Audit current technical assets (recordings, demos, blogs) for depth and reusability.
- Define 2–3 high-impact technical themes where scalable enablement can reduce friction.
Outcome by Day 30
- Clear map of recurring advanced technical questions.
- Identified priority PoC/use-case patterns to formalize.
- Proposed first scalable technical asset or session outline.
First 60 Days – Build & Deliver Scalable Technical ImpactPrimary Goal: Launch repeatable technical enablement and codify structured PoC frameworks.
- Design and deliver at least one advanced 1:many technical session (live or recorded).
- Build a structured PoC framework for a priority adoption scenario:
- Defined success criteria
- Clear architectural reference pattern
- Reusable demo environment or walkthrough
- Publish at least one deep technical asset (e.g., advanced blog, architecture guide, recorded lab).
- Establish lightweight intake process for non-support technical advisory questions.
- Partner with SE/Post-Sales to ensure technical consistency across pre- and post-sales.
Outcome by Day 60
- At least one repeatable enablement session running.
- One codified PoC pattern reusable across customer cohorts.
- Measurable reduction in repeated advanced technical questions in a target area.
First 90 Days – Scale, Influence & OptimizePrimary Goal: Operate as the recognized post-sales technical authority and multiplier.
- Deliver a structured enablement series aligned to a customer maturity theme (e.g., secure pipelines, governance implementation).
- Expand PoC frameworks into reusable “customer-ready” kits.
- Develop a technical content backlog aligned to customer journey stages.
- Contribute field-informed feedback to Product and Engineering based on:
- Architectural friction
- Governance gaps
- Adoption blockers
- On exception, lead 1:1 advanced workshop or guided PoC for a high-impact customer use case.
Outcome by Day 90
- Demonstrable lift in technical adoption across a defined customer cohort.
- Library of scalable technical assets supporting key journey stages.
- Recognized internally as the go-to SME for advanced post-sales architecture questions.
Docker does not offer visa sponsorship for this role.
