How to Answer: "Why Do You Want to Work at Starling Bank?"

Starling's application form asks a written motivation question, which candidates report as: "What do you know about Starling Bank and why do you want to work here?" That question therefore arrives before any interview. You can draft the answer carefully and then reuse it out loud.

Starling Bank is a UK digital bank that built and owns its own banking platform, and it runs personal, business, joint, and multi-currency accounts. It also sells that platform to other banks as Engine by Starling. A strong answer names one specific part of this work, and then connects that part to something you have built yourself.

What the Interviewer Listens For

1. That you know Starling owns its technology. Most banks buy a core banking platform from a vendor, which is the software that holds accounts, balances, and payments. Starling wrote its own instead, and it states its own connections to the United Kingdom payment schemes: Faster Payments, Bacs, and inbound CHAPS. Naming this difference proves real research, so put it in your first two sentences.

2. Interest in the product, not only in digital banking. Starling runs accounts for people and for businesses, plus features such as Saving Spaces and Kite, a card for children. Through Engine, it also sells the same platform to other banks that want to launch their own accounts. Name the product area you want to work on, and say why that one rather than the others.

3. Evidence that you work without heavy process. Starling's engineering pages state that it does not use estimates, story points, or t-shirt sizing, and that engineers release their own code and support it in production. Give one example of a time you set your own priorities and delivered the result without being told to.

4. Fit with the stated values. Starling describes its vision as fast technology, fair service, and honest values, and its responsible banking page names fairness, inclusion, compassion, and transparency. Connect one of those values to a real decision you made at work, because an adjective about yourself proves nothing to the interviewer.

A Three Part Structure

Part 1: The specific opening (2 to 3 sentences). Name what interested you in Starling and prove that you looked at it, because the public developer API and the published engineering posts are both easy evidence to gather.

Part 2: Your proof (2 to 3 sentences). Describe one system you built and owned from start to finish, and include a number that shows either its size or its result.

Part 3: The direction (1 to 2 sentences). Say what you want to build at Starling, and name the area of the bank it belongs to.

Sample Answer

"I want to work at Starling because it owns the whole banking platform instead of renting one from a vendor. I read the engineering posts about releasing to production several times a day inside a regulated bank, and that combination is rare. In my last role I built the payments service for a marketplace, including idempotent retries and a daily reconciliation job. It moved about 40,000 transfers a month, and I supported it in production myself. That work taught me that correctness in money movement comes from design rather than from careful operators. Starling solves the same problem at a far larger scale, and it then sells the result to other banks through Engine. I want to work on core banking services there, and to keep owning whatever I release."

This answer works because every claim has proof behind it. The interest is tied to published engineering writing, and the ownership claim includes a number. The direction names a real part of the bank rather than a job title.

Where the Question Appears

The written version comes first, inside the application form, so treat it as a draft you will later reuse out loud. Expect the spoken version in the first interview with an engineer. The final interview with the chief technology officer or the deputy is reported to focus on culture fit, so the question returns there in a deeper form.

Candidates also report a blunt companion question on some applications: why would we regret not hiring you? Keep the same core answer in every stage, because interviewers compare notes afterward. Add one new proof point in the later stage, such as a detail from the developer documentation.

Common Mistakes

• Praising the app and stopping there. Liking the user interface is not a reason to join the engineering team, because every applicant has used the app.
• Generic enthusiasm for financial technology. An answer that fits any digital bank fails here, because the difference at Starling is that it built and owns its own platform.
• No contact with the product. The app is open to anyone and the developer API has a sandbox, so arriving without trying either one looks unprepared.
• Asking for one narrow specialty. Small cross-functional teams expect engineers to cover several areas, so wanting one fixed task for years does not match that expectation.
• Ignoring regulation. A bank operates under rules that control how it builds software, so wanting to move fast with no mention of controls worries the interviewer.

How to Prepare

• Learn the stages first. The round order in the Starling Bank interview process shows where this question appears and how often it returns.
• Use the same research twice. The product knowledge you gather here also serves the Starling Bank system design interview, so study the platform once.
• Plan for the wait. The reported reply times in how long it takes to hear back will tell you when to follow up.
• Practice the delivery. Grokking Modern Behavioral Interview teaches answers built on evidence rather than on adjectives, which is what this question rewards.