Column's 10 Engineers Move Trillions. Most Came From HN Comments.
Column's July 2026 HN post shows a national bank running on 10 engineers, most hired through Hacker News. Here's how to source that talent pool.
On July 1, 2026, Column posted three jobs into Ask HN: Who is hiring? The post is 90 words long. Buried inside it is the most important fintech sourcing signal of the year: a nationally chartered bank that processes trillions annually runs on 10 engineers, all reporting to the CEO, "many of whom we hired through HN."
If you are sourcing fintech infra in 2026 and your first move is still LinkedIn Recruiter, you are fishing in the wrong pond.
What the July 2026 post actually says
The Column HN post is unambiguous. Started by William Hockey, co-founder and former CTO of Plaid. Ten engineers. All report to the CEO. Many were hired through prior HN threads. Hiring one infrastructure engineer, one backend engineer, one product engineer.
For context on what those 10 people are actually doing: Column owns Column National Association, an FDIC-insured national bank that Hockey bought by personally paying about $50 million in 2021 for Northern California National Bank, a 15-year-old community bank in Chico with roughly $300 million in deposits. He rebranded it. He connected it directly to Fedwire. Then he pointed the API at Brex, Ramp, Mercury, Wise, and Bilt.
Forbes reports Column became the largest originator of real-time payments in the U.S. in 2025, processing trillions in payment volume, with net revenue doubling to $200 million from $100 million the year prior. Upstarts puts gross margins around 85 percent, with only 5 percent of revenue coming from traditional bank lending.
Ten engineers.
At launch in April 2022, Hockey said Column had "only six engineers." Four years later, the count is 10. The company added four engineers while doubling revenue and becoming the top real-time payments originator in the country. That is not a hiring plan. That is a hiring philosophy.
Why HN is the channel, not a channel
The instinct when you read "we hired most engineers through HN" is to treat it as a quirky detail. It isn't. It's the recursive part of Column's hiring model, and it explains why sourcing fintech engineers of this caliber through traditional funnels has quietly stopped working.
Three things compound on Hacker News that do not compound on LinkedIn:
Identity plus taste in one surface. An HN commenter has a username with a decade of comment history, submission history, and a profile that often links to a GitHub. You can read what they think about Postgres locks, ACH nacha files, or Fedwire ISO 20022 migration before you reach out. LinkedIn gives you tenure and a headline. HN gives you epistemic evidence.
Self-selection through the post itself. The Column post reads like a filter. "10 engineers, all report to the CEO" is a pitch to exactly one archetype: the senior IC who is tired of skip-levels, staff-plus review committees, and quarterly OKR theater. That archetype does not open InMails.
Referral density. When an engineer at Column reads HN, the engineers they know socially also read HN. The people they refer read HN. The pattern reinforces itself. LinkedIn's network graph is polluted with recruiters, coaches, and content posters. HN's is polluted with engineers.
Compare Column's post to the other lean-team pitches in the same July 2026 thread. Albert: "profitable for 4+ years, average employee tenure is 3.6 years." Ashby: "80%+ of our engineering team is Senior - Staff+ level." Rho: cross-stack owners. Every one of them is fishing for the same fish with the same lure, and they are all fishing in the same pond because that fish does not swim anywhere else.
The org-chart line is the offer
"All report to the CEO" is not an org chart detail. It is compensation.
For a Staff or Principal infra engineer at Stripe, Adyen, or Modern Treasury in 2026, the marginal dollar of TC matters less than the marginal hour spent on coordination overhead. Column is selling zero management layer at a nationally chartered bank that clears trillions. There is no equivalent job. There is not even a close second.
This is the part sourcers routinely underprice. When you write outreach to a Staff engineer, the subject line "backend engineer role at fintech" is dead on arrival. The subject line that works is the specific structural fact that the target engineer cannot get at their current job. For Column, that fact is: you will ship code to the Fedwire integration and your only stakeholder is the CEO who owns the company.
The 0.1% of infra engineers do not read job descriptions. They read structural facts and infer the job.
This is where sourcing tools break. Boolean strings on LinkedIn cannot find "engineer who would take a pay cut for a flatter org." Neither can a keyword scrape of the July 2026 HN thread, because the signal is not in the post text, it is in who commented on adjacent threads about Fed rails, ACH edge cases, or Plaid's origin story five years ago. That is why we built Refolk: you describe the person in plain English, the system searches GitHub, LinkedIn, and the open web (including HN threads, comment history, and profile links), and you get a ranked shortlist that respects the structural criteria, not just the keyword match.
The comp story the incumbents cannot match
Hockey has said publicly, "99.9% of my wealth is in plaid and column. That's it." Column is entirely owned by founders and employees. There are no VCs demanding a growth curve. There is no board pushing a 40-engineer hiring plan to justify the last round.
Contrast with Cross River Bank, Column's most direct competitor, which last raised $620 million at a $3 billion-plus valuation. Cross River hires on LinkedIn. Lead Bank hires on LinkedIn. Both of them are fine banks. Neither of them can credibly post "10 engineers, no VC, no forced growth" into an HN thread.
This matters for sourcers because the message is doing more work than the channel. If your client is a VC-backed Series C fintech and you're trying to copy Column's HN playbook, you will get worse results than Column does, because you cannot make Column's offer. What you can do is find the specific structural fact your client offers that the target engineer cannot get elsewhere, and lead with that.
The Goliaths being disintermediated
Here is the framing that should make every fintech recruiter uncomfortable. Fiserv has a $33 billion market cap. FIS has a $25 billion market cap. Both are two decades old. Both are being routed around by a 10-person engineering team in Chico, California, that made $200 million in net revenue last year at ~85 percent gross margin.
The people building at Fiserv and FIS are on LinkedIn. So are the people at Cross River. So are most of the people at Stripe, Adyen, and the mid-market payment gateways. The 10 engineers at Column are largely not, or at least not in a way that a recruiter's InMail can reach. They read the July 2026 Ask HN: Who is hiring thread. They read Hockey's Upstarts profile. They probably lurk in the Plaid alumni network. And they respond to structural pitches, not TC bands.
When Capital One's acquisition of Brex closes in mid-2026 for $5.15 billion in cash and stock, some non-trivial fraction of Brex's engineering org will be back on the market. Column will not need to source them. They will show up in the HN comments under the next Column post.
What to actually do this week
Three concrete moves for anyone sourcing fintech infra in H2 2026:
Build a persistent HN watch, not a one-time scrape. The July 2026 Ask HN thread is not a job board. It is a directory of every fintech that has decided its next hire lives in this specific audience. Column, Rho, Albert, and Ashby all posted. So did roughly 800 other companies. Aging tools like HireIndex now let you search that thread and every prior monthly thread going back nine years. That's a decade of self-selected senior IC signal.
Cross-reference HN commenters against GitHub contribution graphs. A username on HN is worth 5x if you can tie it to public commits in a payments-adjacent repo. Refolk pulls both surfaces (plus LinkedIn and the open web) into one query so you can ask, in plain English, for the person you actually want and get back people, not keyword hits.
Rewrite your outreach to lead with structural facts. Not TC. Not "exciting stage." A specific fact about the org, the codebase, or the reporting line that the target cannot get where they are. Column's post is a masterclass. Ten engineers. All report to the CEO. That's the whole pitch, and it works.
The one-person team engineering trend is not a Coinbase memo anymore. It's a nationally chartered bank moving trillions with a team you could fit around one long table. If your 2026 sourcing plan doesn't account for that, the best fintech infra hires in the market are already talking to someone else, in a thread you're not reading.
FAQ
Is Column really hiring most engineers through Hacker News?
Column's July 1, 2026 HN post says "many of whom we hired through HN," not all. Preserve that hedge. What's fair to say is that HN is Column's primary public sourcing channel, and given that the entire engineering org is 10 people, "many" likely means the majority. It's the clearest disclosed example of HN-native fintech infra hiring at bank scale in 2026.
Can a Series B fintech copy Column's HN playbook?
Partially. You can post in the monthly Ask HN thread and you will get responses. What you cannot copy is Column's offer: no VC, no forced growth, no management layer, direct Fedwire integration, and a CEO who was CTO of Plaid. If you try to run Column's pitch without Column's structural facts, you'll get worse yield than a normal LinkedIn campaign. Lead with your own specific structural facts.
Why does "reports to the CEO" matter so much for senior ICs?
For a Staff or Principal engineer with 12-plus years of experience, coordination cost is the single largest hidden tax on their day. A flat org where a Staff IC ships directly to production with the CEO as the only stakeholder is worth a meaningful pay cut for a specific slice of the market. That slice does not read job descriptions. They read org shape.
How do I find engineers who read HN but don't post there?
Cross-reference. Most senior engineers who read HN also maintain a personal site, a GitHub, or a technical blog. Look for engineers who link HN threads in their writing, cite HN comments in blog posts, or have submitted to Show HN in the past. Refolk searches across GitHub, LinkedIn, and the open web for exactly this kind of composite signal, so you can find the lurkers, not just the commenters.