> Markdown version of [/jobs/ext/4704210-principal-software-engineer-fintech](https://www.wearedevelopers.com/jobs/ext/4704210-principal-software-engineer-fintech). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Principal Software Engineer, Fintech

- **Company:** Plug Technologies Inc.
- **Location:** Los Angeles, CA, United States (Remote available)
- **Experience:** Expert
- **Salary:** $222,256 - $259,324
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Distributed Systems, Payment Systems, Fault Tolerance, Web Servers, Software Engineering, Flexi (Photoshop Plugin), Technical Debt, Juniper
- **Published:** November 13, 2026
- **Apply:** https://www.careerbuilder.com/job-details/principal-software-engineer-fintech-los-angeles-ca--3a11624a-b3fd-4d18-82e8-4d6ecee37900

## About the Role

Software Engineering, Sales, Web Client Plug-ins, Juniper Networks M-Series, Artificial Intelligence (AI), Liens, Banking Services, Architectural Design, Technical/Engineering Design, Customer Relations, * 10+ years in software engineering, with 5+ years working on B2B and B2C payments solutions.

 * Direct experience designing and building payments, ledger, lending, or money movement infrastructure, not just consumer-facing payment systems.
 * A genuine taste for elegance: the ability to design within real regulatory and stakeholder constraints in a way that stays efficient and clean, rather than accumulating one-off exceptions and technical debt to satisfy each new requirement.
 * Proven experience designing systems within regulatory and banking-partner constraints. You understand what it takes to build infrastructure that a bank, processor, or regulator will actually sign off on.
 * Deep expertise in distributed systems: transaction integrity, financial data consistency, idempotency, auditability, and fault tolerance at scale.
 * A track record of owning architecture decisions end to end, from design through implementation and long-term maintainability.
 * Comfort operating with high agency in an ambiguous, fast-moving startup environment. You'll be the first and primary technical owner of this domain.
 * Strong cross-functional collaboration skills. You can translate complex technical tradeoffs for Product, Risk, Finance, and Compliance stakeholders.
 * International or cross-border money movement experience is a plus, but not required.
 * Experience with title, lien, lending, or marketplace escrow-like flows is a plus.
 * You work agent-first. You are comfortable orchestrating multiple coding agents, defining clear acceptance criteria, and reviewing AI-generated output to a high bar, and you have a point of view on where that is and is not appropriate in code that moves money.

## Description

* Own the architecture for Plug's money-facing systems: ledger, payment disbursement, settlement, reconciliation, and lien and title payoff processing.
 * Design a ledger that is deterministic, auditable, and gives a single, queryable source of truth for every dollar that moves through the platform.
 * Architect systems that integrate directly with banking partners, payment processors, and lien and title servicers, working within the regulatory and compliance constraints those partnerships require, and doing so elegantly rather than with brittle workarounds.
 * Make and document the core technical tradeoffs for financial systems: consistency vs. availability, idempotency, fault tolerance, and failure recovery for transaction-critical infrastructure.
 * Partner with Product, Risk, Finance, and Compliance to translate business and regulatory requirements into system design.
 * Set technical standards and review architecture for any system that touches money, acting as the final technical guardrail before it ships.
 * Mentor and raise the technical bar for engineers working in and around the money systems domain, without owning formal people management.
 * Evaluate and help decide when to build vs. integrate with external payments and banking infrastructure providers.