Forward Developed Engineer

Forward Deployed Engineer — Banking Platform

Ship it, then go sit with the people using it.

• Charlotte, NC Location Charlotte, NC — on-site at our headquarters, with travel to partner and client sites
  
  Experience Required5+ years building and shipping production software, including meaningful time in financial services and hands-on experience building with Claude
  
  Employment Type
  
  Full-time, exempt
  
  Reports To Technical Program Manager Direct Reports None. You work across engineering, product, operations, and directly with external partners.
  
  Core Stack React, Flutter, AWS, Git Hub Actions, Claude (Claude Code and the Claude API)
  Portfolio Expected — see "Show Us Your Work" below The Trade We're Offering We're a smaller institution headquartered in a city full of very large ones, and we're not going to pretend we can match what the largest of them offer on every dimension. What we're offering instead is scope that those jobs structurally cannot give you. At a large bank, this work is split across four teams — a mobile team, a web team, a platform team, and a client-facing integration group — and you'd own a lane in one of them.
  
  Here, the whole path from commit to customer is yours. You'll write the Flutter code, write the React code, own the pipeline that ships both, and then sit across the table from the people using what you built and watch where it breaks. Engineers who want that loop rarely get it  that's the job you've been trying to find, this is it

We're hiring a Forward Deployed Engineer to build our banking platform and then take it into the field. This is a hybrid of product engineering and client-facing solutions work: roughly two-thirds building, one-third embedded with the partners, vendors, and internal teams who depend on what you ship.

The forward-deployed part is the point. Most engineering organizations put layers between the person who writes the code and the person who has to live with it, and quality suffers in both directions. You'll close that gap. When an integration fails at a partner, you're the one who diagnoses it — not a support tier that escalates to a queue that eventually reaches engineering three days later.

We also expect this person to be genuinely fluent with Claude — not as a novelty, but as core tooling. A small team competing against institutions a hundred times our size only works if each engineer's output is multiplied. You should already be building this way and be able to show us how.

You'll work closely with the Senior Product Manager who owns the banking portfolio, and you'll have real influence over technical direction. We have opinions but not much legacy, which means your architectural decisions will still be standing in five years.

Mobile Development — Flutter

• Build and ship our customer-facing mobile banking application in Flutter across iOS and Android
• Own the release process end to end — store submissions, staged rollouts, versioning, and the deprecation strategy for older clients
• Handle the parts of mobile banking that are genuinely hard: biometric authentication, secure local storage, session handling, offline states, and deep links from notifications
• Keep performance and app size honest on the low-end devices real customers actually carry

Web Development — React

• Build customer-facing web banking experiences and the internal tooling our operations teams use daily
• Share logic and design language across web and mobile so the two products don't quietly diverge
• Build to accessibility standards — WCAG conformance is a regulatory expectation in consumer banking, not a nice-to-have

Cloud Infrastructure — AWS

• Design, deploy, and operate services on AWS — compute, storage, networking, secrets, and identity
• Own infrastructure as code so…