May 20, 2026
How Ramp engineers accelerate code review with Codex
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.β
Running code reviews that teams can rely on
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.β
Developing internal tools with Codex
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.β
Leadership lessons
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.β
Whatβs next
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.β


