Principal Software Engineer (Payments)

Principal Software Engineer II

Are you a senior engineer who wants to stay hands-on while shaping the technical direction of a growing team? Do you enjoy designing and delivering complex systems that have real impact? If so, read on.

We’re building the next generation of tools to support a fast-moving, merchant-first ecosystem. We value empowered teams, practical thinking, and outcome-driven engineering—and we’re looking for someone who shares these values.

What We Prioritise:

• Small teams, real outcomes – Clear goals, the right tools, minimal bureaucracy.
• Growth mindset – Encouraging innovation, skill development, and cross-team learning.
• Solving real problems – Focused on delivering value through practical, scalable solutions.

The Role:

As Principal Software Engineer II, you’ll lead technical direction across a range of platform capabilities (e.g., APIs, billing, settlement). You’ll be responsible for architectural decisions, mentoring teams, and contributing to key delivery efforts—staying 50% hands-on with the code.

Key Responsibilities:

• Define and evolve engineering practices and architecture across teams.
• Own and contribute to technical strategy, standards, and documentation.
• Identify improvement opportunities and lead cross-team initiatives.
• Provide technical leadership and mentorship to developers.
• Guide technology decisions, including build vs. buy assessments.
• Stay hands-on with critical coding tasks tied to strategic goals.

Requirements:

• 10+ years’ experience in software engineering and architecture.
• Strong skills in .NET, Java, or similar languages; SaaS/API experience preferred.
• Hands-on knowledge of SQL, middleware, caching, system integration.
• Track record of addressing performance/scalability issues.
• Experience in mentoring and leading technical teams.
• Excellent communication skills and stakeholder engagement.
• Comfortable working in a fast-moving, evolving environment.

Payments experience is a bonus, but not essential.

Please reach out to Brendan McCrory with any further questions.