Skip to content
Chimera readability score 51 out of 100, Graduate reading level.

Teams use Codex with GPT‑5.5 to review code and develop an agent to manage on-call rotation work, improving the developer experience and boosting productivity.
At Ramp, engineers are using Codex with GPT‑5.5 to accelerate code review and develop internal agentic tooling, helping teams get substantive pull request feedback in minutes instead of hours. Thanks to its reasoning capabilities, Codex with GPT‑5.5 is uniquely able to reduce the amount of manual, hands-on work they’d otherwise have to do.
“Codex code review catches things that I miss and that other engineers miss and that other AI code reviewers definitely miss.”
Ramp’s AI Developer Experience team is using Codex to improve software development velocity and code quality.
“Codex code review is industry gold standard. We’ve been relying on it for a long time here at Ramp,” explains Austin Ray, who leads AI DevEx. “It’s incredible, and our engineers ask for it by name. They look forward to its comments on every PR, and it’s become a mandatory part of a lot of code review flows.”
Ramp engineers who used to wait hours for a first review can now get substantive feedback from Codex in minutes. Codex stands apart from other tools because it deeply reasons against the codebase, resulting in what Ray describes as “a level of thoroughness that most human reviewers don’t have time for.”
Codex matches this depth with an experience that, Ray says, “meets engineers where they are.” Engineers who prefer to work close to the metal can work from the CLI, and the Codex app provides visual cues, utilities, and additional features for those who want them. Ray, typically a CLI user, felt drawn to the app. “It feels like the app shepherds you toward higher productivity in your engineering workflows,” Ray says.
“Codex with GPT-5.5 is incredibly adept at dealing with that complexity in a way that would take me a ton of mental effort, a lot of sleep, and a lot of single-minded focus on the problem to figure out.”
Ray is also using Codex to support the development of On-Call Assistant, an agentic tool that takes on most of the burden for Ramp engineers during on-call rotations.
“On call is hard,” Ray explains. “We have a lot of business logic, domain knowledge, and heavy incidents. You have to keep a ton of things in context and reason through a lot of complexity.”
For an engineer, this can be difficult. It takes a lot of mental effort and even more single-minded, unbroken focus.
“There’s just a ton of complexity,” Ray says. “There are plenty of concurrency bugs, a tricky balance to strike between external events and internal events, and long-running incident investigations with evolving details you have to keep working in.”
With Codex, Ray can depend on its “incredibly adept” reasoning capabilities to support development. As a result, On-Call Assistant has become significantly faster to build, and Ray is more confident about every improvement shipped.
“Our product surface area is pretty immense,” Ray says. “Codex with GPT‑5.5 handles it like it’s nothing.”
Ray is a platform engineer, first and foremost, and he evaluates all developer tools, including AI-driven ones, through that lens. As he puts it: “Does it actually change how people ship code, or is it just a demo?”
And that’s what Ray recommends for other leaders: Focus on the hands-on experience and real-world results.
- Demonstrate the potential of AI tools first-hand: “Get your engineers to install Codex, sit down with them, and guide them through a really solid first session. Paint the picture of what development could be for them.”
- Build a path to trust and iteration: “Most engineers don’t fully understand or trust that they’re going to have a good experience with this. They treat it as something experimental. By guiding them through that first experience, you change their perspective and make them willing to explore and iterate themselves until they become one of your best AI users.”
- Invest in the feedback loop: “We work directly with the Codex team on feedback. When we hit issues, we have a direct line. That feedback loop is what makes a vendor relationship worth investing in, and we’ve made incredible progress with the Codex team.”
“Codex is the real deal. Codex definitely helps us ship faster.”
Codex is changing how fast Ramp engineers can work and giving them the resources to support even greater ambitions. For Ray, this indicates a new way to think of engineering as a whole.
“Engineers are going to become orchestrators. The skill is no longer writing every line of code yourself. It’s knowing how to direct AI tools like Codex, when to trust them, and when to push back. At Ramp, our best engineers learn that fastest.”

Facts Only

* Ramp engineers use Codex with GPT-5.5 to accelerate code review.
* Codex with GPT-5.5 is used to develop internal agentic tooling.
* Codex is used to provide substantive pull request feedback in minutes.
* Codex is relied upon for code review by Ramp engineers.
* Codex is used to support the development of the On-Call Assistant.
* Engineers use Codex to manage complexity in on-call rotations, which involves business logic, domain knowledge, and incident investigation.
* Codex is able to reason against the codebase, resulting in thorough feedback.
* Engineers utilize the Codex app, which provides visual cues and utilities for CLI users.
* Codex handles the complexity of the product's immense surface area.
* Engineers are developing the skill of orchestrating AI tools like Codex.

Executive Summary

Ramp engineers utilize Codex with GPT-5.5 to accelerate code review and develop internal agentic tooling, aiming to improve software development velocity and code quality. Codex is employed for code review, providing feedback that engineers find thorough and essential, positioning it as an industry gold standard. This capability allows engineers to receive substantive feedback in minutes rather than hours, significantly reducing manual review work. Furthermore, engineers use Codex to support the development of the On-Call Assistant, an agentic tool designed to manage the complexity of on-call rotations, which involves handling business logic, domain knowledge, and complex incident investigations. The application of Codex is framed as allowing engineers to shift their focus from manual execution to orchestration, enabling them to handle immense product complexity.

Full Take

The narrative positions AI tools not merely as productivity boosters but as tools for redefining the role of the engineer, shifting the focus from writing code to orchestrating AI. The core implication is that advanced AI reasoning can handle the immense complexity of modern software systems, freeing human capacity for higher-level decision-making and problem structuring. The claims regarding Codex being an "industry gold standard" appeal to a form of trust built on demonstrated efficacy, which the text argues must be driven by real-world, hands-on experience rather than mere demonstration. This creates a tension between the perceived ease of AI-driven acceleration and the necessity of maintaining human oversight, particularly in high-stakes environments like incident response. The pattern suggests that the most successful adoption of powerful AI involves integrating it into established, high-friction workflows, establishing trust through predictable quality and direct feedback loops. The challenge lies in ensuring that the pursuit of speed does not erode the deep, contextual understanding required for handling true complexity, particularly when engineers transition to being "orchestrators" of AI rather than sole executors of logic.

Sentinel — Human

Confidence

The text reads as an internal interview focusing on real-world engineering experiences, displaying strong human voice and specific, contextual detail rather than generic, synthetic reporting.

Signals Detected
low severity: Irregular sentence length and conversational rhythm, mixed with high-register technical vocabulary. Not uniformly metronomic.
low severity: Strong, specific focus on anecdotal experience and internal company philosophy. Absence of generic, balanced 'both sides' framing.
low severity: Specific, non-generic quotes about internal processes ('industry gold standard') and detailed operational challenges (concurrency bugs, incident investigations). No obvious verbatim talking point matching across unrelated sources.
low severity: The narrative structure aligns with a human-centered business case presentation (tooling leads to better outcomes), making claims appear anchored in specific, lived experience rather than abstract statistics.
Human Indicators
The text contains highly specific, qualitative quotes that focus on subjective experience, emotional weight (mental effort, sleep), and internal workflow philosophy, which are difficult for generic LLMs to fabricate authentically.
The focus on real-world engineering pain points (concurrency bugs, on-call complexity) provides specific, idiosyncratic context that suggests direct human input rather than generalized synthesis.
How Ramp engineers accelerate code review with Codex — Arc Codex