Principal Production Engineer

#WeAreParamount on a mission to unleash the power of content… you in?

We’ve got the brands, we’ve got the stars, we’ve got the power to achieve our mission to entertain the planet – now all we’re missing is… YOU! Becoming a part of Paramount means joining a team of passionate people who not only recognize the power of content but also enjoy a touch of fun and uniqueness. Together, we co-create moments that matter – both for our audiences and our employees – and aim to leave a positive mark on culture.

  Summary   The Principal Production Engineer is the senior technical authority for the Integration Team’s delivery: architecting and shipping stakeholder-facing AI workflow solutions that are reliable, observable, secure, and maintainable. This role is a hands-on solver who tackles the hardest integration problems, defines solution-layer reference architectures and standards, and ensures multiple concurrent engagements execute with consistent technical quality. They bridge product intent and engineering execution by translating ambiguous workflow needs into scalable technical designs and production-ready implementations.   Key Responsibilities   Portfolio Architecture & Hard Problem Solving  

• Own reference architecture for the solution layer across engagements (boundaries, data flows, error/fallback behavior, safe UX patterns, operational controls). Lead the design for complex integrations. This involves working with several systems, limited environments, and secure VPC or on-prem setups. You will also conduct threat modeling and apply privacy-by-design when necessary.
• Take point on the hardest integration work: performance bottlenecks, reliability gaps, deployment constraints, data quality edge cases, and cross-system failure modes.
• Build or guide critical-path components and reference implementations; create reusable libraries where leverage is high.

    Standards, Guardrails & Production Readiness  

• Define and evolve reference patterns for delivery shapes (API/MCP, plugin, automation, batch, embedded service, secure enterprise patterns).
• Ensure that platform modules follow the rules for interfaces. This includes validating schemas, pinning versions, checking compatibility, mapping dependencies, and managing changes.
• Set the production definition of done. This includes telemetry, dashboards, alerts, runbooks, rollback plans, and supportability. Conduct readiness reviews for high-impact releases.
• Run architecture reviews and targeted technical audits to reduce integration churn and regressions.

  Platform Interface Influence & Feedback Loop  

• Partner with Core AI/Research & Platform to improve module usability and integration fit (latency budgets, failure modes, data formatting, eval needs).
• Identify recurring integration issues. Propose improvements for the platform. These improvements should aim to reduce the need for custom solutions. This can involve using shared components, observability hooks, and standardized contracts.
• Plan for cross-brand compatibility when the platform changes. Create playbooks for upgrades and deprecations. These playbooks will help protect existing solutions.

  Reliability, Telemetry & Operational Excellence  

• Standardize reliability patterns across the portfolio. This includes rate limiting and backoff strategies. It also includes retries, circuit breakers, caching, idempotency, and graceful degradation.
• Ensure end-to-end instrumentation standards are met (usage, success/failure, latency, cost proxies, workflow KPIs).
• Lead production hardening on critical engagements. This means validating stability, participating in incidents, and making improvements based on postmortem reviews. Follow through on ongoing actions.
• Ensure operability artifacts exist and are usable (dashboards, alerts, runbooks, escalation paths).

  Knowledge Capture & Reuse  

• Ensure the quality and consistency of the Solution Bundle. This means maintaining architecture notes. It also includes managing integration patterns, operational learnings, reusable components, and known issues.
• Build and maintain shared scaffolding (templates, SDK wrappers, test harnesses, telemetry middleware) to accelerate repeat engagements.
• Find ways to create standardized integration packages from successful patterns. Also, think about related capabilities of the platform.

  Decision Rights & Ownership