Software Engineer, Codex App

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified

Was this benefit information wrong? Tell us.

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Software Engineer, Codex App San Francisco, California, United States, Seattle, London, UK About the Team The Codex App team owns the desktop application and IDE extension that bring Codex into developers' daily workflows. We build product experiences end-to-end, and we care equally about usability, performance, and reliability. Our stack is centered on a TypeScript/Node/Electron application that interfaces with external systems including the Codex CLI and app server (Rust). Building great features here often means designing clean boundaries between UI, local services, and native processes - and making the whole system observable and resilient. About the Role We're hiring a Full Stack Software Engineer to build and evolve the systems that power the Codex desktop app and IDE extension. “Full stack” here means owning flows from UI → Node/TypeScript backend layers → IPC/process orchestration → integration with Rust services. This is a product-minded role. You'll help define workflows, pick the right abstractions, and ship features that feel fast and dependable in real developer environments. What You'll Do - Build end-to-end features across the Electron app (UI + Node/TypeScript backend layers). - Design robust integrations with the Codex CLI and app server (Rust), including process lifecycle, streaming output, and error handling. - Own IPC architecture and patterns (renderer/main boundaries, message schemas, backpressure, safety, debugging). - Build systems for orchestration: long-running tasks, incremental progress updates, cancellation, retries, and state synchronization. - Improve reliability, observability, and performance (logging/tracing/metrics, profiling, crash/debug tooling). - Partner with design and product to turn ambiguous needs into crisp, shippable

Read the full description at jobs.ashbyhq.com. FewerJobs shows a source-linked preview and links to the original posting.