Shawbrook
Product Manager, Customer & Accounts Platform

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Company Description
Shawbrook provides finance to a wide range of customer segments that value the premium experience, flexibility and certainly we deliver. We are a purpose-led organisation, with a focus on delivering long-term sustainable value for all our stakeholders.
We have a diversified offering, with our innovative lending propositions tailored to meet specific customer needs in carefully selected markets across SME, Real Estate and Personal. Our products range from complex structured credit facilities for growth-focused businesses to mortgages for professional landlords and property investors, as well as simple loans for consumers delivered digitally. We fuel our lending through customer deposits, which we attract by delivering a premium experience, choice and consistently great value to smart savers.
The business model we have created is unique and difficult to replicate, with our ‘best of both’ approach combining deep human expertise with advanced digital, tech and data capabilities. This combination not only allows us to deliver excellent customer experiences, but to do so efficiently and at scale. We are proud of our innovative and agile culture, which drives consistently high employee engagement scores and makes Shawbrook an attractive destination for the best talent. If you’re willing to roll up your sleeves, contribute new ideas and believe anything is possible, you’re our kind of person.
Work with us because you:
- Want to be part of a bank built for the dynamics of the modern world
- Relish a challenge and enjoy a fast-paced, innovative and hardworking culture
- Enjoy finding new and better ways to solve complexity and make things happen
- Want to belong to a diverse culture that stands shoulder to shoulder with minority and underrepresented groups
- Care about society and the environment and want to be part of a business that cares too
- Want to continue to grow professionally and be the best version of yourself
Job Description
The Customer and Accounts platforms are the spine of the Core Banking Platform. The Customer Platform holds the Bank’s single, deduplicated view of every person and organisation we deal with. The Accounts Platform is the layer every system in the Bank goes through to create and service accounts on Thought Machine Vault Core. Every other platform, franchise and squad depends on both.
This role owns the product agenda across the two. You will run a single roadmap, own the API contracts other teams build against, and define how these platforms behave to the level of precision an engineer can build from: how a customer is matched, merged and maintained, how accounts are created and move through their lifecycle, how instructions and events flow to and from Vault Core, and what happens at every boundary and edge case in between.
It is a deliberately deep, hands-on platform role for someone who is energised rather than daunted by data models, API versioning, idempotency and failure modes, and who is comfortable that their users are other engineering teams rather than end customers.
Roadmap & Initiative Definition
- Own a single product roadmap across the Customer and Accounts platforms, sequenced against franchise commercial priorities, Core Banking Programme commitments and the platform’s delivery capacity.
- Balance platform reliability, new capability and migration work in one plan, and make the trade-offs between them explicit rather than letting the loudest demand set the order.
- Run discovery with the squads and franchises that depend on the platform, establishing the underlying customer and business need, the platform behaviour it implies, and whether the platform can support it.
- Convert consumer demand into well-formed initiatives with a clear problem statement, scope, dependencies and definition of success, so the squad has a credible, prioritised pipeline of work.
- Take on the problems that are too large or too cross-cutting for any single product squad to own, the ones that only become solvable when one platform holds the whole picture.
- Own migration and decommissioning planning for legacy customer and account infrastructure, including how records are matched, moved, reconciled and proven correct.
- Bring a point of view. Where a request is poorly formed, unaffordable or better solved elsewhere in the estate, say so early and propose the alternative.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Product Definition on the Platform
- Own how the Customer Platform behaves — matching, merge and deduplication rules, what constitutes the golden record, how customer data is maintained and corrected, and the downstream consequences of any change to that record — including configuration and the rationale behind every parameter choice.
- Own how the Accounts Platform behaves — account creation, lifecycle states and closure, how instructions reach Vault Core, and how posting and event behaviour is exposed back to consuming systems.
- Treat the platform API surface as a product in its own right: own its definition, versioning and documentation, so every consuming system has stable contracts to build against and no consumer is surprised by a change.
- Set the standards for how other squads integrate with the platform, covering integration patterns, idempotency, error handling and testing, and make sure they are understood and followed.
- Translate consumer needs, regulatory obligations and platform constraints into unambiguous requirements, with user stories and acceptance criteria covering happy path, unhappy path, boundary and invalid-input cases.
- Decide whether a need is met by configuration, new platform capability, or a change in the consuming system, and make the trade-off explicit rather than defaulting to build.
- Build in the controls the Bank needs from the outset: FCA and Consumer Duty outcomes, accuracy and lineage of customer and account data, auditable behaviour, and correct treatment under financial crime and data protection obligations.
- Grow the Customer Platform as the Bank’s single source of truth for who we deal with, rather than one more system holding a partial view.
- Make each new product and franchise faster and lower-effort to launch by building reusable capability rather than one-off integrations.
- Review implemented behaviour against requirements alongside engineers, and own product sign-off through test and UAT.
Cross-Functional Collaboration
- Work day to day with the engineers on the platform squad, not just their leadership, in refinement, in design discussions and in defect triage. The quality of this working relationship is the single biggest determinant of success in the role.
- Partner with the franchise and product squads that consume the platform, and hold the line on platform integrity under delivery pressure, balancing franchise urgency against consistent, scalable foundations.
- Work with Operations to understand how customers and accounts are actually onboarded and serviced, and bring that reality into platform decisions.
- Engage Finance, Data, Legal and Risk & Compliance early, so reporting needs, regulatory change and control expectations shape requirements rather than arriving as late constraints.
- Communicate platform and integration decisions in plain language to non-technical stakeholders, and in exacting detail to engineers. Both audiences should recognise the same decision.
- Use data to understand platform performance, and present roadmap and strategy to senior leadership, including the quarterly Technology Platform Playback attended by the CTO.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
Interfaces & Boundaries
- The Product Lead, Core Banking Platform owns cross-book demand consolidation, investment business cases and prioritisation. This role supplies the platform substance those business cases rest on.
- The Vault Platform Product Manager owns the Vault implementation across the Bank and all product lines on it. This role owns the customer and account layer in front of it, and the two agree the seam between platform behaviour and product behaviour rather than each assuming it.
- Product Managers for each lending product line own their own product definition on Vault Core. This role owns the shared customer and account capability underneath them, and escalates cross-product-line trade-offs rather than resolving them locally.
- The Core Banking Delivery Lead and Engineering Manager own delivery sequencing and capacity. This role owns what is being built and why, and whether what was built is right.
- Data owns the Bank’s data architecture and governance. This role owns the customer record as a product and works within that architecture.
Qualifications
Essential
- Strong product management experience across the full lifecycle, from discovery through delivery and into live running.
- Experience of platform, API-first or infrastructure products, where your users are other engineering teams rather than end customers, including ownership of API definition, versioning and documentation.
- Strong core product management craft: discovery, framing the problem before the solution, roadmap definition, and making and defending prioritisation trade-offs with competing stakeholders.
- Experience defining requirements for engineering teams, including acceptance criteria at a level of detail that removes ambiguity.
- Comfortable operating at a low level of abstraction in a technically complex, regulated environment, and able to reason about how components integrate, where data flows between them, and how they fail.
- Able to hold the line on platform integrity under delivery pressure, balancing franchise urgency against consistent, scalable foundations.
- Experience in financial services, ideally across core banking, accounts, lending or customer data.
- Uses data to drive decisions, able to interrogate system output directly, understand platform performance, and ground prioritisation in evidence rather than stakeholder volume.
- Excellent written and verbal communication, and the credibility to work as a peer with engineers and with senior business stakeholders up to ExCo.
- Agile working practices and fluency in Jira and Confluence.
- Precision and intellectual honesty. This role should be prepared to challenge a design, escalate an unresolved decision, and say “we don’t know yet” rather than paper over a gap.
Desirable
- Direct experience of Thought Machine Vault Core, including its API surface and posting mechanics.
- Experience of customer data management: matching and merge, golden record or master data management.
- Familiarity with domain-driven design or event-driven architecture.
- Experience of migrating off and decommissioning legacy platforms, including data migration and reconciliation.
- Understanding of the system landscape around customer and accounts: origination, servicing, payments, collections and data.
- A track record of using AI to improve journeys and ways of working.
Additional Information
Your Wellbeing
- We take your health and well-being very seriously by providing a range of benefits to give you and your family
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Location