Operating Systems Engineer | Consumer Devices

OpenAI OpenAI · AI Frontier · San Francisco, CA · Consumer Products

OpenAI's Consumer Devices team is seeking an Operating Systems Engineer to build and harden the OS foundations for their AI-powered consumer products. This role involves deep systems ownership across the OS kernel, core services, security, privacy, performance, and power, with a focus on debugging and reliability from development through production. Collaboration with various engineering teams is key, and experience with hardware bring-up is a plus.

What you'd actually do

  1. Work on end-to-end OS capabilities spanning the OS kernel, userspace services, application frameworks, UI toolkits, and application-facing APIs.
  2. Develop, integrate, and maintain OS components, both kernel-bound and in userspace, including scheduling, memory management, filesystems, drivers, IPC/RPC mechanisms, and security-relevant subsystems.
  3. Build and maintain core OS services and daemons (init, service management, device discovery, networking primitives, time, logging, update hooks, crash handling, and so on).
  4. Design and implement security and privacy mechanisms:
  5. Establish a performance and power discipline:

Skills

Required

  • systems programming
  • Linux
  • BSD
  • kernel development
  • core OS subsystems
  • platform enablement
  • C
  • C++
  • low-level systems development
  • core OS services
  • platform software
  • system services
  • daemons
  • init/service management
  • device management
  • logging/telemetry pipelines
  • complex issue debugging
  • kernel/userspace boundaries
  • tracing
  • profiling
  • structured root cause analysis
  • security fundamentals in OS design
  • isolation boundaries
  • privilege separation
  • secure IPC
  • attack surface reduction
  • vulnerability mitigation practices

Nice to have

  • Rust
  • systems contexts
  • kernel-adjacent tooling
  • userspace services
  • security-sensitive components
  • performance-critical libraries
  • OS security hardening
  • SELinux/AppArmor policy
  • sandboxing
  • seccomp
  • namespaces/cgroups
  • secure boot chains
  • exploit mitigations
  • operationalizing observability
  • eBPF-based tooling
  • perf pipelines
  • automated regression detection
  • performance and power optimization
  • measurement methodology
  • power rails
  • battery instrumentation
  • thermal constraints
  • closed-loop tuning
  • supporting application or UI frameworks
  • OS boundary
  • Wayland/compositors
  • graphics pipeline performance
  • input latency
  • lifecycle/permission models
  • hardware bring-up
  • bootloader/early boot debugging
  • device tree/ACPI
  • board revisions
  • peripheral enablement
  • OTA/update systems
  • partitioning strategies
  • rollback/health checks
  • update security
  • signing
  • provenance
  • upstream open source projects
  • Linux kernel
  • system components
  • long-lived downstream patches

What the JD emphasized

  • deep debugging and systems ownership
  • security and privacy primitives
  • performance and power
  • debugging and observability
  • security fundamentals in OS design
  • security hardening
  • performance and power optimization