Software Development Engineer III
Job description
About the role
The role contributes to the payer proposition team to build and experiment with new engagement features for payers. The work focuses on developing features that improve how payers interact with GoCardless and testing concepts in this greenfield area. Collaboration across functions is required to reduce ambiguity and deliver reliable solutions.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Exploration of payer networks uncovers opportunities to improve payer engagement with GoCardless. Designed experiments validate ideas and generate insight into payer behavior. Cross-functional collaboration resolves ambiguity and tests new concepts. Current technologies build reliable systems, which are adapted based on findings. The payer experience is shaped to strengthen payer relationships and support merchants.
Requirements
The posting states a pay range of $49600 to $74000.
A bachelor's degree or equivalent practical experience is required. Experience with banking, payments, or financial infrastructure is beneficial. Adaptation to new technologies and processes is necessary. Collaboration in team environments is expected, with an emphasis on reliable, well-tested systems. Problem solving and initiative are required to find better solutions.
Practical notes
This role is based in Lisbon, Portugal, and may involve travel. Work away schemes and adaptive working policies may apply. Team composition and processes are designed to support experimentation and learning. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Growth mindsets drive learning and concrete business outcomes. Collaboration shapes the best products. Reliability and testing are emphasized. Problem solving and ownership help teams find better solutions.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Based in London, this fintech company focuses on bank payments. Core offerings include recurring transactions, Direct Debit handling, and Open Banking services. Business operations center on these payment solutions. The company serves clients through specialized bank payment processing. Head office remains in London. Expertise lies in streamlining payment flows for partners. Consistent focus stays on bank-based payment methods.