Senior Software Engineer - Merchant Experience

About seQura

At seQura, we’re building more than features. We’re building a product platform that works across verticals, regions, and brands.

We focus on solving real problems for shoppers, merchants, and partners, and we take full responsibility for what we build — from the first idea to running it in production. We work as one team, sharing context, ownership, and outcomes.

Born in Barcelona, seQura is a privately-owned fintech, currently expanding throughout southern Europe and Latin America, growing above 50% CAGR.
Over 6000 businesses, almost 3 million shoppers, and almost 400 employees continue to rate us as one of the most loved and trusted fintechs out there, with an NPS of 87%, a Trustpilot rating of 4.7/5, and a Glassdoor rating of 4.1/5.

About the role 🤓

We’re looking for a Senior Backend Engineer to join our Merchant Experience team, where engineers operate as true product engineers, owning problems end-to-end and shaping the future of seQura’s B2B platform.

This role goes beyond traditional backend or fullstack engineering. You’ll work on the Merchant Portal platform, the central B2B application where merchants manage orders, track performance, and grow their sales. While your main focus will be on backend systems and platform evolution, you’ll also feel comfortable touching frontend code when needed to deliver end-to-end solutions.

You’ll be part of a highly autonomous team where engineers define problems, validate hypotheses with data, make product decisions, and iterate quickly based on real merchant feedback. We use AI coding assistants (Claude, Cursor) as force multipliers, where the focus is increasingly on why and what to build, while leveraging AI to support the how.

About the Merchant Experience team 🧩

Team missionTo build and scale the Merchant Portal platform — the central B2B application that gives thousands of merchants autonomy, insights, and tools to run and grow their business with seQura.

What we own

• Foundational modules of the Merchant Portal (order management, performance analytics, merchant self-service tools such as campaigns)

• Platform capabilities that allow other teams to build vertical solutions on top of Merchant Portal

• Growth-oriented initiatives, including new value propositions that help merchants sell more and unlock new revenue streams

• Data-driven features that demonstrate how seQura directly impacts merchants’ sales performance

How we work

• Team of 4 Senior Product Engineers with diverse technical strengths

• Strong ownership mindset: engineers own problems end-to-end

• The team validates hypotheses, analyzes metrics, and makes product decisions collaboratively

• Fast iteration, high autonomy, and close collaboration with other engineering teams and customer-facing roles

Requirements

What challenges you'll be solving 🚀

• Own product problems end-to-end: from understanding customer needs and defining hypotheses to validating solutions and shipping impact

• Design and evolve core Merchant Portal platform modules with scalability and extensibility in mind

• Make data-informed product decisions by analyzing metrics, gathering evidence, and incorporating merchant feedback

• Collaborate closely with other engineering teams, vertical product teams, and customer-facing roles to ensure platform impact

• Contribute to architectural decisions that enable the Merchant Portal to become a true B2B platform

• Work in an AI-augmented development environment, leveraging AI tools to accelerate delivery while focusing on problem-solving and product thinking

What to expect in the next 90 days 🏁

Month 1: You’ll get familiar with the Merchant Portal, our revenue model, and how merchants actually use the product. You’ll ship small improvements early to understand workflows, constraints, and decision-making patterns.

Month 2: You’ll identify a friction point in the merchant experience, validate it with data and feedback, and lead a solution end-to-end (from definition to production). At this stage you’re expected to create work, not wait for it.

Month 3: You’ll identify a limitation in the current merchant experience and evolve the underlying capabilities (domain model, APIs, or workflows) so ne