Refolk
June 6, 2026·9 min read

Ramp's $750M at $44B Closed June 5. Brex's Inspect Trade Has 30 Days.

Ramp's $750M Series F at $44B lands while Brex is mid-acquisition. Here's the 30-day counter-recruit playbook for fintech sourcing teams.

Ramp $750M funding roundRamp $44 billion valuation hiringBrex Ramp engineer poachingfintech engineer sourcing 2026spend management talent market
Ramp's $750M at $44B Closed June 5. Brex's Inspect Trade Has 30 Days.

On June 5, 2026, Ramp closed a $750M Series F led by ICONIQ, GIC, and Ontario Teachers' Pension Plan at a $44B valuation. If you recruit for Brex, Mercury, Navan, or any of the EU spend-management challengers, your calendar just changed. You have roughly 30 days before Ramp's offers go out, and the most valuable trade isn't the one Ramp will make first.

What the round actually buys

Ramp's valuation moved from $16B twelve months ago, to $32B seven months ago, to $44B on June 5. That isn't a runway raise. That's a hiring war chest with a clock on it. The Ramp $750M funding round arrived with new backers including Goldman Sachs Alternatives, D.E. Shaw, Morgan Stanley Investment Management, Generation Investment Management, Insight Partners, and BroadLight Capital. When that many tier-one names price a round in seven months, the company has already pre-committed the spend.

$44B
Ramp's valuation on June 5, 2026
Up from $16B twelve months earlier, a near-tripling that priced the next 18 months of hiring.

Annualized revenue is over $1B (Bloomberg puts the run-rate near $1.5B). Annualized purchase volume is over $200B. Enterprise customer growth is over 100% year-over-year, with more than 3,200 customers generating at least $100K in annualized revenue. The narrative for the next four quarters writes itself: agentic payments, accounting automation, procurement agents, and an EU launch this summer behind the Billhop and Juno acquisitions.

That's the surface. The thing recruiters need to internalize is which roles those product bets actually require, because the keyword searches most sourcers will run this week will miss them entirely.

The Brex symmetry nobody is saying out loud

Eric Glyman and Karim Atiyeh met in a Harvard CS class, built Paribus, sold it to Capital One in 2016, then founded Ramp in 2019 with Paribus engineer Gene Lee. Six years later, Capital One is acquiring Brex for roughly $5.15B, a deal announced in January 2026 and expected to close mid-year. The founders who sold to Capital One are now watching their largest competitor get bought by Capital One at a steep discount from Brex's $12B peak valuation.

For recruiters at Brex, this is not a vibes problem. It is a product-direction problem. Brex's roadmap is about to be re-prioritized against a bank's portfolio. The 234 currently open roles on Brex's board are real, and the comp is real (Glassdoor pegs Brex SWE II median total comp at $177,127), but the equity story changes the day the Capital One deal closes. Brex ICs know this. They are already taking calls.

This is what makes the Brex Ramp engineer poaching dynamic different from a normal competitive cycle. Ramp doesn't have to recruit hard. It just has to be visible. The counter-move for Mercury, Rippling, Stripe Issuing, and the EU challengers is not to defend Brex talent. It's to fish the same pond, faster, while Ramp is still building its offer pipeline.

The four pools that open first

1. AI-applied product engineers, not ML researchers

Ramp's stated investment areas are Ramp Stack (an AI operating system for accounting firms), AI token spend management, Ramp Budgets, and procurement agents that automate purchasing workflows. None of that needs an ML PhD. It needs senior product engineers who have shipped LLM-in-the-loop workflows in a regulated environment, which is a tiny intersection.

If you keyword-search "ML Engineer" on LinkedIn this week, you will miss the pool. The actual profile lives at Stripe (Issuing, Billing, Tax), Mercury, Plaid, Anthropic and OpenAI applied teams, and the half-dozen YC fintech-AI companies that shipped agentic features in 2025. Most of them don't have "AI" in their title. They have shipped retrieval systems against ledger data, prompt eval harnesses for financial workflows, or human-in-the-loop review queues for invoice extraction.

This is exactly the search that breaks Boolean. "Senior product engineer, regulated fintech, has shipped an LLM workflow that touches money movement" is not a string. It's a description. Which is why we built Refolk: you describe the person in plain English, and you get a ranked shortlist that draws from GitHub commits, LinkedIn history, and the open web rather than the title field alone.

2. The Inspect platform team

The single most under-discussed line in Ramp's press release is that Inspect, its internal software factory, writes more than two-thirds of Ramp's code. If that number is real, the highest-leverage hire in fintech right now is not the 10x IC. It's the platform engineer who builds the code-generation harness.

Ramp will spend the next 30 days locking up its Inspect team with refresher grants priced off the $44B mark. Brex, Mercury, and the EU challengers should be making counter-offers this week. The Inspect team is not large. LinkedIn will not surface them cleanly because most of them have generic titles like "Staff Software Engineer" with a paragraph in the about section that mentions internal tooling.

The most valuable hire in fintech this month is not the 10x IC. It is the engineer who built the harness that replaces them.

3. Agentic payments specialists

Ramp deepened its multi-year partnership with Visa to enable AI agents to execute autonomous corporate payments with real-time controls. Agentic payments as a sub-discipline has maybe a few hundred qualified engineers globally. The pool is concentrated at Visa Developer Center contributors, the Stripe Agents team, Marqeta's program management engineers, and a small group at Plaid working on transaction enrichment.

This is the most defensible thing Ramp is building and the hardest to staff. If you are at a competitor and you are not running outreach against the Visa AI agent partnership working group this week, you are giving Ramp a 60-day head start on a category.

4. EU payments and compliance

Billhop gives Ramp UK/EU payments rails. Juno gives them guest travel infrastructure. The summer launch into UK and Europe means London, Dublin, and Berlin hiring lands in Q3. Wise, Revolut, GoCardless, and Pleo engineers are about to receive a wave of outreach they are not braced for.

US-based recruiters historically under-index on this pool. The mistake is treating it as a secondary market. For payments and compliance roles, the EU pool is deeper than the US one, particularly for engineers who have shipped against PSD2, SCA, and the upcoming Instant Payments Regulation. The fintech engineer sourcing 2026 playbook needs a Europe column, and it needs it this month, not in September.

What Navan is and isn't

Navan raised $200M at a $9.2B valuation. It is a T&E company, not a financial-operations platform. Navan engineers are a real recruit for Brex and Mercury (the workflows overlap), but they are not a natural feed for Ramp, because Ramp specifically needs accounting, procurement, and agentic-payments depth that Navan doesn't build.

The implication for the spend management talent market: do not treat Navan as a Ramp feeder when you plan your defense. Treat it as your own opportunistic pool. Ramp's Q3 hiring will not heavily target Navan, which means Navan's senior ICs are available without a bidding war for the next quarter.

The customer-side signal accounts

Ramp's named enterprise customers include Visa, Uber, Shopify, Anduril, Figma, Notion, Cursor, Stanford Athletics, and The Boys and Girls Club. Two things to do with that list.

First, the internal teams at those companies who own the Ramp integration are pre-qualified for any spend-management role. They have lived inside the product, hit its edges, and know what is missing. The accounts payable engineer at Notion who built the Ramp sync is a better hire for Mercury's bill-pay team than three cold sourced candidates.

Second, the Cursor and Anduril names are signal for a specific kind of engineering culture. Those companies hire opinionated, fast-shipping ICs. The internal champions for Ramp at those accounts skew the same way. If you are sourcing for a high-agency culture, the Ramp customer roster is a shortlist hiding in plain sight.

The 30-day plan, concretely

Week 1 (now through June 12). Pull the Inspect team. Identify the Brex ICs whose vesting cliffs land before the Capital One close. Stand up your EU sourcing pipeline against Pleo, Spendesk, and GoCardless. Map the Visa Developer Center contributor list against your ATS.

Week 2 (June 12 to 19). First-touch outreach. The Ramp $44 billion valuation hiring story is already in the news cycle. Lead with the counter-narrative: dilution math at 44x revenue, product clarity at a smaller stage, and a real equity refresh you can actually price.

Week 3 (June 19 to 26). Onsite cycles. Anything not in onsite by week three loses to Ramp's offer timeline. This is where most counter-recruit campaigns fail. The pipeline exists, the conversations happen, and then the loop drags into July while Ramp signs the candidate in June.

Week 4 (June 26 to July 3). Close. Refreshers, sign-on, start-date flexibility. The Ramp offers will land in the first two weeks of July. You want signed paper before the comparison set exists.

234
Open Brex roles still posted during the Capital One acquisition
Aggressive hiring continues, but the equity story changes the day the deal closes.

The sourcing layer most teams are missing

The hard part of this 30-day window is not strategy. It is volume against a description that doesn't fit a title search. "Engineers who built code-generation tooling at a fintech, are not currently advertising it, and would consider a Series C challenger" is not a LinkedIn filter.

This is the friction Refolk is built for. Ask in plain English, get the right people across GitHub, LinkedIn, and the open web. A sourcer running the Inspect counter-recruit can describe the harness in a sentence, get a ranked list, and have outreach moving by end of day rather than end of week. Against a 30-day window, that compression is the entire game.

FAQ

How aggressively will Ramp actually recruit from Brex in the next 30 days?

Probably less aggressively than people expect, because they don't have to. The Capital One acquisition has already destabilized Brex's equity narrative, and senior Brex ICs are taking inbound calls without being pushed. Ramp's larger spend will go toward EU hiring and agentic-payments specialists, where the pool is shallower and the competition is broader. That makes Brex a defensive priority for every other fintech, not just for Brex itself.

Is the Inspect team really the highest-leverage trade?

For platform-engineer hiring, yes. If two-thirds of Ramp's code is machine-written, the engineers who built that harness have done something most fintechs are still trying to figure out. They are also the smallest, most concentrated, and most likely to be locked up by refreshers in the next two weeks. If you want to make a credible run, this week is the week.

Should US recruiters really prioritize EU sourcing right now?

If your company competes with Ramp on spend management or financial operations, yes. The Billhop and Juno acquisitions plus the announced UK and EU launch this summer mean Ramp will be hiring London, Dublin, and Berlin heavily in Q3. The Wise, Revolut, GoCardless, and Pleo engineering pools are deeper than most US sourcers realize, and the candidates have not been hit with this volume of outreach before. First-movers will get the best ones.

What's the comp anchor for counter-offers this month?

Brex SWE II median total comp is around $177K per Glassdoor, which sets a credible floor. Ramp's $44B mark gives them headroom on equity, but the dilution math at 44x revenue means refresher grants come with a real story about ceiling. Mercury, Rippling, and the EU challengers can compete on stage-appropriate equity and product clarity rather than trying to match Ramp's nominal grant values.

Read next