---
title: "Growth Intern to Procurement New Grad"
description: "A 2023 summer internship on Ramp’s growth engineering team changed the author’s view of software engineering and led to a return as a new graduate engineer. The team accelerated outbound sales through fast experiments, metric ownership, and decisions about whether promising tactics deserved scalable systems, rather than following the thorough specification process typical of regular projects. His work included reducing third-party data-enrichment costs, building AI-driven outbound-sales tools, adding observability and service monitors, and conducting competitive intelligence projects. He returned to join the new procurement product line, where he helped match card transactions to purchase orders and led additional projects. The post also recommends rapidly building system context through code review and on-call shadowing, while full-time engineers should weigh velocity against maintainability and take initiative on less-defined problems."
---

# Growth Intern to Procurement New Grad

[Ramp](https://yomu.fyi/company/ramp) · Aaron Abraham · Apr 3, 2025

**Type:** Explainer

## Summary

A 2023 summer internship on Ramp’s growth engineering team changed the author’s view of software engineering and led to a return as a new graduate engineer. The team accelerated outbound sales through fast experiments, metric ownership, and decisions about whether promising tactics deserved scalable systems, rather than following the thorough specification process typical of regular projects. His work included reducing third-party data-enrichment costs, building AI-driven outbound-sales tools, adding observability and service monitors, and conducting competitive intelligence projects. He returned to join the new procurement product line, where he helped match card transactions to purchase orders and led additional projects. The post also recommends rapidly building system context through code review and on-call shadowing, while full-time engineers should weigh velocity against maintainability and take initiative on less-defined problems.

## Context

After several backend internships at large companies, the author wanted a final internship at a hyper-growth company and sought to improve the skill of shipping software at speed. The internship experience, Ramp’s culture, and the opportunity to work with its people led him to return as a new graduate engineer on the procurement team.

## Approach / What changed

The growth team emphasized fast experimentation, monitoring north star and input metrics, analyzing results, and deciding when to scale a successful tactic into a system. The author worked on third-party data-enrichment cost reduction, AI-driven outbound-sales tools, observability and service monitoring, and competitive intelligence, then joined procurement and worked on matching card transactions to purchase orders.

## Takeaways

- Growth engineering required testing ideas quickly, measuring results, and deciding whether a strategy justified building a scalable system.
- The author’s procurement work included matching card transactions to purchase orders to track spend against procurement requests.
- For the transition to full-time engineering, the author recommends code review, on-call shadowing, recording unanswered questions, considering maintainability, and taking initiative on ambiguous problems.

**Tags:** [Monitoring](https://yomu.fyi/topic/monitoring), [Onboarding](https://yomu.fyi/topic/onboarding)

- Source: [Ramp](https://builders.ramp.com/post/intern-to-new-grad-aaron-abraham)
- Source URL: https://builders.ramp.com/post/intern-to-new-grad-aaron-abraham
- Ingested by Yomu: 2026-09-01T01:34:31.595Z

[Read original post](https://builders.ramp.com/post/intern-to-new-grad-aaron-abraham)
