Principal Software Engineer - FinTech
JobNimbus · Lehi, UT
—
Jul 20, 2026
Lehi, UT
Jul 21, 2026
What this job asks for AI summary
A principal-level engineering role focused on owning the architecture and long-term roadmap of a payments and billing platform built on Stripe. Day-to-day work spans designing distributed financial systems, writing foundational backend code in C# and Node.js, setting company-wide engineering standards, and mentoring senior engineers. Suited to a seasoned engineer with deep payments domain knowledge and experience leading technical strategy across multiple teams.
Principal level · 10+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 2,550 people nationally plausibly meet what this posting asks for (software developers). range 1,500–3,800
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
Location is not stated in the posting; JobNimbus is headquartered in Lehi, UT but the role appears to be remote-eligible based on the absence of any location requirement. CBSA left blank due to genuine ambiguity.
C# and Node.js are listed together with 'and/or' framing in the requirements block — C# is emitted as the primary skill with Node.js as an alternative, reflecting that mastery of at least one is the hard gate.
Couchbase is explicitly called 'a major plus' in the requirements section, placing it as preferred rather than a hard gate despite appearing alongside required skills.
AI-assisted development tools appear in a responsibilities/vision context ('Champion the strategic adoption of…') rather than as a candidate qualification gate, so treated as preferred.
Observability, tracing, and alerting are described with firm gating language ('deep experience with') in the requirements block and are captured as a single 'observability' skill covering that capability cluster.
No compensation range is disclosed in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): AI-assisted development tools.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.