Principal Software Engineer - Partner Services

Priority Technology Holdings, Llc; United States; Remote; USD 180,000 - 240,000; Full time

Job summary

Priority Commerce is seeking a Principal Software Engineer - Partner Services to lead a multi‑team area while staying hands‑on in critical systems. You will own architecture roadmaps, ADRs, and cross‑team standards, partnering with product, design, and executive leadership to drive business outcomes.

This role emphasizes AI‑native practices, incident leadership, and enterprise‑level reliability in a remote setting.

Qualifications

• 15–20+ years of engineering experience.
• Payments or Banking domain experience preferred.
• Hands-on coding with leadership responsibilities.
• Own area-level OKRs and KPIs; drive business outcomes.
• Proven architecture leadership and ADR practice.

Responsibilities

• Stay hands-on — design, build, review, and operate critical systems.
• Lead during highest‑pressure moments — incidents and escalations.
• Own the area’s architecture roadmap and ADRs.
• Participate in ARB and write ADRs to enterprise standards.
• Contribute to the Principal Engineering & Architecture Guild.
• Define and enforce observability bar aligned with SRE principles.

Skills

Hands-on leadership

Architectural leadership

Executive communication

Reliability & security focus

AI-native practices

Education

Bachelor's degree in CS/Engineering

Advanced degree preferred

Tools

React.js/Redux

Node.js

Kafka

MySQL

Elasticsearch

Redis

Snowflake

AWS

Kubernetes

GitHub/TeamCity/Octopus

Job description

If you are unable to complete this application due to a disability, contact this employer to ask for an accommodation or an alternative application process.

Principal Software Engineer - Partner Services

Professional Remote, US

Job title: Principal Software Engineer - Partner Services

Reports to: Director, Engineering

Department: Development

Location: Remote (CAN)

About Product & Technology at Priority Commerce:

Our vision in Product & Technology is to engineer the world's most resilient, AI-native financial ecosystem that empowers businesses to transcend table-stakes and lead the agentic future, where every financial transaction is intelligent, every developer is accelerated, and every experience is unified.

At Priority Commerce, we are building the Priority Commerce Engine, a unified platform that enables businesses to collect money, store money, lend money, move money, and build modern commerce experiences at scale.

About the Role:

Principal Software Engineers are the senior technical leaders of a product area at Priority Commerce — a group of teams that together own a meaningful slice of the platform. You're the highest technical authority within the area, and accountable for both its technical outcomes and the continuous improvement of its engineering quality. Together with the area's Director of Engineering, you share accountability for the area's customer and business outcomes — the OKRs and KPIs the business plans on, what the area ships, and how reliably it serves customers.

You're motivated to own mission-critical systems — the ones where correctness, data integrity, security, and availability are obligations, not features, and where a defect in production affects real customers moving real money. The weight of that responsibility is part of what draws you to this role, not something you tolerate.

You're hands-on. Still. At Priority, the Principal title doesn't graduate you out of the code — it puts you in the parts of the system that matter most, and keeps you close to production so your direction stays grounded in reality. You lead by example — your quality, your work ethic, your AI-native practice, and your engineering judgment set what the area looks like at its best.

When the area hits its highest-stakes moments — incidents that draw executive attention, senior cross-functional escalations, the most critical delivery moments — you're in the room and on point. You show up, take the lead, and stay on it until it's resolved — regardless of time of day, day of week, or weekend.

You co‑own the area's relationship to its customer and business outcomes with the Director of Engineering — not just its technical health. You own engineering's line of sight to those outcomes: area‑level OKRs and KPIs — the ones the business plans on — tie back to the engineering work you direct. You know the area's most important customers and senior stakeholders by name, partner with product and design leadership on the area's strategy, and speak the business' language fluently enough that engineering investment can be defended on the same terms as product investment.

You partner with peer Principals across product areas on shared services, integration patterns, and cross‑cutting capabilities, executing within the standards Distinguished Engineers & Architects set. You hold a formal (dotted‑line) relationship with Distinguished Engineers & Architects, who set the architecture standards the area aligns to and can direct or overrule area‑level architectural decisions in service of platform coherence.

You participate in the Architecture Review Board and the Principal Engineering & Architecture Guild. You bring the workstream's architectural decisions that cross workstream boundaries or need enterprise ratification to Priority's Architecture Review Board (ARB), and you take ARB direction back to shape decisions inside your workstream. You write ADRs to the enterprise standard the Distinguished Engineer & Architect owns, and you hold the ADR practice in your workstream so architecture knowledge compounds rather than scatters. You also show up to Priority's Principal Engineering & Architecture Guild — the venue where cross‑workstream learning between Principals happens deliberately. It's where you get sharper alongside your peers, and where your workstream's architectural judgment is informed by everything you see across the rest of the company.

You hold the architecture transparency framework in your workstream. The Distinguished Engineer & Architect defines the framework that makes Priority's architecture transparent and less personality‑dependent; you hold it in your workstream. Every critical system in the workstream has a current runbook, an AI‑native knowledge store, an ownership map, and a backup/shadow ownership map — machine‑readable, kept current, and useful in an incident at 2 AM without paging a specific human. The AI‑native knowledge store is treated as a real operating capability, not a side documentation exercise: it cuts onboarding time, sharpens troubleshooting, and makes your workstream's architecture less dependent on tribal memory. When you go on leave, the workstream doesn't lose its architectural memory — because you made sure it lives in a system, not in your head.

You set the observability bar for the workstream. Observability is engineered in, not bolted on. The Distinguished Engineer & Architect sets the observability bar for Principals; you set it for your workstream. Teams build systems observable from the first line of code — instrumentation, telemetry, SLOs, and error budgets are design‑time properties, not afterthoughts — and Staff+ engineers hold that bar in their domains. The workstream operates in the spirit of SRE, because you can't operate what you can't see, and you can't earn customer trust in systems you can't observe.

You serve as your workstream's conduit to Priority's Innovation Studio team — paving the way to a continuously evolving and improving Agentic PDLC way of working. What the Studio explores at the edges of practice, you translate into your workstream's daily work; what your workstream learns in production, you feed back so the Agentic PDLC gets sharper for everyone. The Studio partnership is a primary source of your AI‑forward leverage.

Developing engineers is a primary part of the job — and it doesn't stop at the Staff+ bench. The Staff and Senior Staff engineers in the area get sharper because of your architectural mentorship. But every engineer on every team gets better because you care about lifting them, at every level — the mid‑level engineer whose design review you spent an hour on, the associate who paired you with a hard bug, the Senior who watched how you handled an incident and took something into the next one. The Principal who only makes the engineers closest to their own level better is leaving the biggest part of the multiplier on the table.

What You’ll Do:

• Stay hands‑on — design, build, review, and operate the parts of the area's systems that matter most; lead by example, not by exhortation.
• Lead during the area's highest‑pressure moments — incidents that reach executive attention, senior cross‑functional escalations, the most critical delivery moments — regardless of time of day, day of week, or weekend.
• Own the area's architecture roadmap and the ADRs that govern it — current, communicated, and built against by teams.
• Participate in Priority's Architecture Review Board (ARB) — bring workstream architectural decisions that cross workstream boundaries or need enterprise ratification, and take ARB direction back to your teams; write ADRs to the enterprise standard and hold the ADR practice in your workstream so architecture knowledge compounds rather than scatters.
• Show up as an active member of the Principal Engineering & Architecture Guild — the venue where Priority's Principals get sharper together.
• Hold the architecture transparency framework in your workstream — every critical system has a current runbook, an AI‑native knowledge store, an ownership map, and a backup/shadow ownership map, machine‑readable and kept current; treat the AI‑native knowledge store as a real operating capability, not a side documentation exercise.
• Set the workstream's observability bar — instrumentation, telemetry, SLOs, and error budgets engineered in from the first line of code; every team in the workstream builds in the spirit of SRE.
• Define and drive how AI agents take part across discovery, design, development, testing, deployment, and operations — and be the most AI‑forward engineer in the area by visible evidence.
• Own the area's OKRs and KPIs end to end — system metrics and the customer and business outcomes the area is on the hook for — and partner with product, design, and customer‑facing leadership on the area's strategy.
• Own the area's technical onboarding and knowledge base — usable by engineers and agents alike, with no single points of failure.
• Raise the area's engineering maturity — quality, predictability, reliability, agentic practice — by setting the example and coaching the engineers around you up.
• Allocate technical investment against strategy and defend it in business terms leadership accepts; own the area's delivery, reliability, security, and quality trends and make the case for investment with data.
• Partner with peer Principals across product areas on shared services, integration patterns, and cross‑cutting capabilities — executing within the standards Distinguished Engineers & Architects set.
• Serve as your workstream's conduit to Priority's Innovation Studio — translate Studio‑explored Agentic PDLC practices into your workstream's operational reality, and feed workstream production learnings back into the evolving practice.
• Develop engineers at every level — Staff and Senior Staff sharpen through your architectural mentorship, and the mid‑level, associate, and Senior engineers around you get better because you care about lifting them.

Success Looks Like:

• The area's architecture roadmap is current, and teams build against it.
• ADRs at workstream level are written to the enterprise standard and cited by engineers in the workstream years later; the ADR practice compounds architectural knowledge rather than scattering it.
• Every critical system in your workstream has a current runbook, an AI‑native knowledge store, and an ownership + backup ownership map — architecture in the workstream is transparent and less personality‑dependent, and onboarding, troubleshooting, and incident response go faster because of it.
• Observability is a design‑time property of what your workstream ships; teams operate in the spirit of SRE.
• The area's customer and business outcomes — its OKRs, its KPIs — move on your watch, not just its technical metrics.
• The area is more predictable on your watch — lead time shrinks year over year, commitments hold, and incident and defect trends improve.
• AI agents are operational across the lifecycle, not aspirational — because you defined and led the practice.
• Engineers at every level in the area grow because of you — not just the Staff+ bench, but the mid‑level, associate, and Senior engineers you took the time to lift.
• The area has no single points of failure you haven't identified and mitigated; what the area ships is reliable, and customers feel it.
• The Distinguished Engineer & Architect considers your area the example.

What We're Looking For:

• Roughly 15–20+ years of relevant engineering experience — a guide, not a gate; we hire on demonstrated impact, not years.
• Experience in the Payments or Banking domain is preferred, but experience in at least one of these areas is required.
• Hands‑on credibility and strong work ethic — you still write the code, debug the incidents, stay close to production at this level, and lead by example, not by exhortation.
• Comfort and credibility leading in the area's highest‑stakes moments — executive‑attention incidents, senior escalations, critical deliveries — regardless of hour.
• A track record owning technical direction for a multi‑team organization with real business outcomes, including reliability and quality leadership at scale.
• Track record of owning area‑scale customer and business outcomes, not just technical ones; product, business, and stakeholder fluency at the level required to partner with executive product leadership.
• Architecture leadership evidenced in writing — roadmaps, ADRs, and standards organizations built against.
• Experience participating in an Architecture Review Board (or equivalent cross‑workstream architecture decision forum) and adopting a standardized ADR practice across a workstream.
• Track record of setting the observability and reliability bar for a multi‑team organization — teams that shipped observable systems by default because you led them there, and operated in the spirit of SRE.
• Demonstrated leadership of AI‑native transformation — agentic workflows adopted by teams, not just personal use.
• A record of growing engineers at every level — not just Staff‑level engineers into architecture ownership, but visible investment in the growth of mid‑level, associate, and Senior engineers around you.
• Security and regulatory fluency for financial platforms.
• Exceptional written and executive communication.
• The primary technology stack for the Partner Solutions team includes: Frontend: React.js/Redux Backend: Node.js, Kafka Data Layer: MySql, Elasticsearch, Redis, Snowflake Infrastructure : cloud‑native microservices AWS, Kubernetes CI/CD: github/Teamcity/octopus

Nice to Have:

• Experience improving engineering processes and team effectiveness at scale.
• Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience.
• Advanced degree in a relevant technical discipline (e.g., Master’s or PhD).
• We believe that performance and experience go hand in hand - an exceptional employee experience is earned through contribution . We are a results‑driven team, grounded in our core values: ownership, authenticity, service, trust, innovation, and camaraderie.
• Our culture is built for those who want to make an impact. We challenge each other to grow, celebrate progress, and support one another through shared goals and real connection. Whether you’re