Fintech Developers in New York
A verified directory of 214 fintech developers in New York — where they work, what they ship, regulatory exposure, and which contact path actually reaches them. Preview free, unlock the full list with a free Articuler account.
Last verified
- 214
- Fintech developers
- 96
- Employers
- 43%
- Open to moving
- 61%
- Reachable off corporate email
Verified in the last 30 days
Banks, scale-ups and infra vendors
Signalled in the last 90 days
Personal path on file
Free preview
6 of 214 profiles
Names, roles, companies and live signals are public. Verified emails and LinkedIn URLs stay masked until you sign in.
- 01
Oluwaseun Adebayo-Frost
Staff Engineer, Payments Core · Thornfield Clearing
Financial District, New York
Led a real-time payments migration off a mainframe ledger; shipped in March after two years.
- Payments infra
- PCI-DSS
- Staff+
- Shipped migration
- o•••••@thornfieldclearing.com Locked
- 02
Ilse Brandtvold
Senior Backend Engineer · Kettleworth Bank
Midtown, New York
Eight years at the same bank-chartered institution; first public conference talk last month.
- Bulge-bracket bank
- Bank-chartered
- Senior
- Newly visible
- i•••••@kettleworthbank.com Locked
- linkedin.com/in/•••••• Locked
- 03
Mattias Grzelak
Principal Engineer, Risk · Ravenswood Neobank
Flatiron, New York
Built the underwriting engine from scratch; team grew from 3 to 14 under him this year.
- Neobank
- SOC 2
- Principal
- Team lead
- m•••••@ravenswoodneobank.com Locked
- linkedin.com/in/•••••• Locked
- 04
Chidinma Okwuosa-Lang
Senior Engineer, Ledger · Barrowgate Digital
Brooklyn, New York
Core contributor to an open-source double-entry ledger library used by four other fintechs.
- Crypto / digital assets
- Open source
- Senior
- Ledger
- c•••••@barrowgatedigital.com Locked
- linkedin.com/in/•••••• Locked
- 05
Rasmus Peduzzi
Engineering Manager, Fraud · Halloway Pay
Hudson Yards, New York
Left a bulge-bracket bank for a Series B fourteen months ago; now hiring three engineers.
- Fintech scale-up
- PCI-DSS
- Manager
- Hiring
- r•••••@hallowaypay.com Locked
- linkedin.com/in/•••••• Locked
- 06
Anjali Venkataraman-Pryce
Staff Engineer, Settlement · Wickersley Rails
Financial District, New York
Owns settlement reconciliation for a card network integration; on call for a regulated surface.
- Payments infra
- PCI-DSS
- Staff+
- Settlement
- a•••••@wickersleyrails.com Locked
- linkedin.com/in/•••••• Locked
Unlock the full Fintech Developers in NYC list
The other 208 profiles are in Articuler. A free account runs 3 directory matches a day — every match returns full profiles with verified emails and LinkedIn URLs. Upgrade for unlimited matches, filtering and export.
Sign in to unlock the full listFree account · No credit card · Takes about 30 seconds
Opens Articuler search for “Fintech developers in New York”
Frequently asked questions
- Why does "reachable off corporate email" matter more here than in other directories?
- Because 105 of these 214 work somewhere with monitored, archived and often externally-filtered mail — bulge-bracket banks and bank-chartered fintechs are required to retain correspondence, and recruiter mail to a @bank address frequently never arrives. The 61% figure counts people with a personal path on file. For this population it is the single field that decides whether outreach lands at all.
- What makes a fintech developer different from a general backend engineer in New York?
- Regulated surface area. Someone who has shipped inside PCI-DSS scope or under an OCC charter has worked with change-control, audit trails and release windows that most product engineers never touch. That experience is why they get hired into fintech and why they are hard to substitute — and it is why 74 of these are tagged PCI-DSS in scope rather than lumped in as "backend".
- Are bank developers actually open to leaving?
- More than the headcount suggests: banks are the largest single employer bucket here at 61, and they are over-represented in the 43% signalling openness. The usual reasons are a compensation ceiling below what a Series B pays in equity, and a stack they cannot talk about publicly. That combination is why bank engineers respond to specific technical pitches and ignore generic ones.
- How does the office cluster affect who will take a meeting?
- New York fintech is not one scene. The Financial District cohort (62) skews bank and infrastructure and is largely back in office; the Brooklyn cluster (41) skews crypto and early-stage with far looser attendance. Trying to run a single in-person event for both is the most common mistake — the subway ride is 35 minutes and functions as a filter.
- Does this include crypto and digital assets engineers?
- Yes, 31 of them, tagged separately. Whether they belong in "fintech" is genuinely contested and depends on what you are hiring or selling for. Filter them out if your product assumes a regulated banking counterparty, and filter them in if you are staffing a ledger or custody problem.
- Why is the count smaller than the other directories?
- Because the intersection is narrow on purpose. There are far more developers in New York and far more fintech people in New York than there are people who are both, with verified employment inside a regulated fintech surface. A list of 3,000 "NYC engineers" would be easier to build and worth much less.