
Ramp hires high school dropouts, Minecraft modders, Olympians, and people who sold products their customers hated
Eric Glyman, co-founder of Ramp, gave a talk on how Ramp thinks about hiring. Ramp is about to cross 1,500 people. Half their spend goes to engineering, product, and design. Their SDRs carry 4x the quota of their closest competitor. The company runs on a simple test: does this save customers time or money? If yes, ship it. If not, don't.
Here's how they built the team behind that.
Before You Hire Anyone, You Need Taste
Ramp almost never hires "pure managers." They want people who've done the work sold the deals, written the copy, designed the interface. Not once, but consistently.
Eric still writes copy. Still reviews marketing collateral. Still gets involved in design decisions. The reason is simple: doing the work gives you taste. And taste is what lets you hire well.
He references Jiro Ono, the 99-year-old sushi master in Tokyo. Someone asks Jiro his secret. His answer: "In order to make delicious food, you need to eat delicious food. You must develop a palate capable of discerning good. Without good taste, you can't make good food."
You don't start by making sushi. You start by tasting it.

Before you open a single role, check three things:
-
Has this person done the work? Do they know the craft?
-
Is there a clear need and a person-problem match?
-
Do they have judgment and discernment?
If you can't check all three, you're not ready to hire.
Different Problems Need Different People
In the early days, Ramp had two archetypes of engineer.
The first: perfectionists. Ramp issues credit cards. If you swipe and it doesn't work, that's not funny. Parts of the stack need very low latency, very fast response time, zero tolerance for error. You want people who obsess over that.
The second: fast shippers. People who learn quickly, ship daily, sometimes hourly. Get customer feedback, fix it in 10 minutes. They can be a little sloppy that's okay in the right context. If a receipt match takes half a second sometimes and 10 seconds other times, that's not a crisis. As long as you detect it and respond.
"Good" isn't enough. Ask: good for what context?
You're in the People Business, Not the Tech Business
The team you build is the company you build. Especially early on, when you have very few dollars and you're competing in the world's most competitive market the market for people.
Eric's framework comes from Moneyball. Billy Bean ran the Oakland A's on a tiny budget. The old way was hiring well-rounded sluggers. Bean's approach: find very specific stats that stack together to produce the outcome you need. He assembled a strange-looking team guys who could hit but couldn't catch and they won far more than anyone expected.
Don't hire well-rounded. Assemble a set of spikes that produce the outcome you need.
Where to Find Mispriced Talent
Hire aliens. Ramp has hired 20–30 people through extraordinary ability visas (O-1/H-1B). Most companies won't put in the time to sponsor. That means less competition for excellent people. If you're willing to do the work, you get access to a talent pool most people ignore.
Spot talent early. Ramp offers winter internships, fall internships, spring internships. They met Calvin Lee when he was 18 a high school dropout at MIT looking for a four-week winter internship as a freshman. Nobody competes for that. They kept up with him, built a real relationship, and when it came time, convinced him to join instead of going to Citadel. If they'd waited until the normal recruiting window, he'd have been priced in.
Look for Black Sheep. One of Ramp's extraordinary engineers has autism, went to community college. Not an obvious resume. But he was very well known in the Minecraft community - he built complex private servers that showed extreme attention to detail. That skill was directly relevant to building complex databases. Non-traditional resumes can hide extreme capability. Look for evidence of obsession.
Hire for taste. Eric references Rick Rubin's interview with Anderson Cooper. Cooper asks: "Do you know how to work a soundboard?" Rubin says no. "Do you know anything about music?" No. "What are you being paid for?" Rubin's answer: "The confidence in my taste and my ability to express what I feel has proven helpful for many artists."

Early hires should have a strong, sometimes stubborn, point of view. Generalists are common. People with particular opinions who've built a specific craft are rare.
Be Careful with Lineage Hiring
People say things like "that company is known for great sales, hire from there." Eric's pushback: dig one layer deeper.
It's the difference between recruiting from the 1990s Chicago Bulls and the 2010s Chicago Bulls. Same name, very different caliber. Was this person the one who built the function, or did they just operate it at scale? Was it the right era?
There's also a hard negative. If a product is so good it sells itself like Figma you can't tell who's genuinely great at sales there. Eric's best early salesperson was Max, who was top of his leaderboard at Namely. Namely had scaled to $70–80M in revenue in a few years with an NPS of -40. How do you sell something people hate? That's a real salesperson. Bring them to a company with a great product and watch what happens.
Simplify What You're Selecting For
Most job descriptions have a long checklist of requirements. Every new requirement narrows your pool and raises your price. You might narrow from tens of thousands of potential candidates down to five.
Early-stage heuristic: pick one thing you're looking for. Maybe two. Probably one.
If you're looking for just one spike, you can search much more broadly, assess much more quickly, and compare candidates on the one vector that actually matters for your business.
Write unreasonably short job descriptions. Make it easy to assess someone's performance on one metric.

Slope Over Intercept
Someone with 10 years of experience starts higher on the value curve. That's intercept it's known, and it's priced in. The 18-year-old intern starts lower. But if the intern is on a steep slope built a video game, won a competition, obsessed over a craft the lines cross fast.
Hire for slope every time. "Zero defects" is not the goal. Weirdness is fine if the spike is real and the trajectory is steep.

Design Your Interviews to Measure Different Thing
Most companies run six interviews that all ask variations of the same question. "Tell me about your background." "Tell me about a project you're proud of." Half the time is wasted measuring the same note.
At Ramp, each interview is designed to extract a different signal. One might be a debate they'll find something you say and disagree with you. The goal isn't to trick you. It's to see how you handle disagreement, because if you put a bunch of determined, stubborn, spiky people together, debates are inevitable.
Be intentional: what signal are we trying to extract from this hour?
Strong Yes or Bust
Ramp grades candidates on four levels: strong no, no, yes, strong yes.
Six "yes" votes is a no. You want someone especially the hiring manager to pound the table. "I'm going to make this person successful." That conviction matters. One strong yes from the right person can overwhelm other hesitations, because it means someone is putting themselves on the line.
If nobody's pounding the table, keep looking.
The Uncomfortable Truth About Interviews
Spend eight hours interviewing a candidate. All the meetings, the dinner, the retro. Within two business days of them actually starting, you'll have more information about what it's like to work with them than your entire interview process gave you.
Most people aren't that good at interviews. Real work reveals reality fast.
The best tactic, especially early: hire from referrals. You or someone you trust has worked with, observed, and built things with a person for years. That's asymmetric information no interview process can replicate.
What Changes at Scale
Core sampling. As you grow, go deep into the org. Don't just do one-on-ones with direct reports. Go to their skip levels. Drill down to see if reality matches your assumptions.
Founder review. Ramp learned this from Facebook. For a long time, Mark Zuckerberg reviewed every hire up through 2,000 people. At Ramp, before anyone gets hired, Eric, Kareem, and Colin all sign off. It keeps the bar consistent, and it helps close candidates "the founders reviewed your packet and want you here" is a strong signal.
Measure by function. For sales roles, track payback period. G&A should shrink as a percentage of expenses as you grow. R&D output takes years to measure, so track input metrics productivity and throughput to see if the next hire speeds things up or slows things down.
On Conflict with High Conviction People
If you hire black sheep and founder types, expect fights. Eric's take: the goal of a debate isn't to outsmart the other person. It's to get to the truth faster together. Iron sharpens iron, but only if egos are low enough to separate yourself from your position.
He quotes a line from @FoundersPodcast : "Tolerate genius." People who are particularly good are stubborn and a little out there. That's the cost of unique output.
Best ideas should win, regardless of who's the boss. Done right, it attracts deeper thinkers.
All credit to @eglyman and the @tryramp team. These are my notes from his talk I just wrote them up so more people could learn from it. If you're a founder or planning to be one, watch the full video. It's worth the hour!
