Software Engineer: Boarding

The Boarding domain builds and maintains the platform that onboards merchants onto PPRO's network of the products and services that get our customers live, fast, compliant, and reliable. As a Software Engineer, you own live, public-facing APIs built to handle real scale, take on well-defined but moderately complex problems, work largely independently within the team, and own your piece of the boarding pipeline end-to-end.

What you'll do

• Build, test, and operate services within the Boarding platform, following the "you build it, you run it" mindset
• Work largely independently on team-scoped tasks, seeking guidance from senior teammates and your manager on ambiguous or cross-team topics
• Adapt quickly when priorities shift, re-plan your own work, communicate impact, and keep delivery moving without needing to be told twice
• Take ownership of your commitments: proactively surface risks/blockers, follow through to completion, and hold yourself accountable for outcomes, not just output
• Write testable, decoupled, readable code; write tests across the pyramid (unit → integration); use our observability stack to understand and improve the services you own
• Participate in incident response for your team's services, using runbooks and systematic debugging; contribute to blameless postmortems
• Collaborate closely with peers, other Boarding squads, and stakeholder teams (Compliance, Product, Risk); share knowledge and give/receive feedback openly

What you'll need

• 3–5 years of hands-on software engineering experience, ideally with some payments/fintech exposure
• Java, Spring Boot, REST APIs
• Event-driven microservice architecture (SQS/SNS/Kinesis or similar)
• AWS cloud fundamentals (EKS, DynamoDB, or equivalent managed services)
• Testing across the pyramid; comfortable with TDD
• Observability tooling (Datadog or equivalent) - can read dashboards/alerts and act on them

Nice to have

• Terraform/IaC exposure, payments or KYC/compliance domain background, hands-on use of AI tools in the SDLC