Skip to content
Intro to Tech, Analytics, and Product (TAP).

How TAP is organised

TAP – Technology, Analytics, and Product – builds and runs iwoca’s technology platforms. TAP people sit inside every part of the business, working on the products and infrastructure that make iwoca function.

What iwoca builds

iwoca provides credit and financial products to small and medium-sized businesses. The products span several markets:
UK Lending. Flexi-Loans for UK SMEs, from £1k to £1m. The largest part of iwoca by headcount and revenue.
DE Lending. The same core product adapted for the German market, run from Berlin and Frankfurt.
iwocaPay. B2B Buy Now Pay Later. Sellers offer business customers flexible payment terms; iwoca pays the seller upfront and takes the credit risk.
New Ventures. A business credit card, Credit Compass (credit-score monitoring for SMEs), manda (acquisition finance for SME buyouts), and insurance. Each runs as a small, standalone team.

How teams are organised

Teams are grouped by mission – what they own and deliver – with engineers, analysts, product managers, and designers embedded in each.
Funnel teams own the customer journey for UK Lending – whether a customer arrives direct, through a broker, or via a partner integration.
New Customers – sign-up through first loan
Repeats – retention and re-lending
Platform – shared services the other funnel teams rely on
Broker Flow – the broker application journey
Partner Flow – integrations with fintech product platforms (business banking, accounting, etc.)
Direct acquisition owns how customers find iwoca directly – SEO, paid, brand.
Analytics covers credit risk, pricing, portfolio modelling, and data science across iwoca’s products. The structure is hub-and-spoke: a large central team, smaller groups embedded in product teams, and individual data scientists within build teams.
Credit risk modelling (League of Lending) – building the probabilistic ML models shaping who gets funded, at what price, and for how much
Customer Lifetime Value (CLtV) – portfolio performance and profitability modelling
Embedded data scientists – smaller groups or individuals sitting inside the funnel teams, acquisition, and our German product offering, working on team-specific analytics, RCTs and modelling
Core Systems maintains the shared technical foundations.
Infrastructure – cloud, CI/CD, monitoring
Platform – Django, Celery, the core backend
Reporting Systems – data pipelines and dashboards
Knowledge Management – internal documentation and tooling
Architecture sets technical direction across TAP – system design, standards, and cross-team coordination.

Where your role fits

Job listings are categorised by discipline – Software Engineering, Data Science, Design, Strategy and Product, Risk and Lending Strategy. Day to day, you work inside one of the mission teams above.
Guilds connect people across teams who share a discipline. There are guilds for back-end engineering, front-end, analytics, product, design, and security. They maintain shared standards, run knowledge-sharing, and coordinate work that spans team boundaries.
Your discipline is how you’re hired, your team is what you work on, and your guild is your professional community.

What this means for your interview

The job description should state which team the role sits in. If you want to understand more about what that team owns or how the day-to-day work runs – ask in your interviews. Your interviewers can give you the most current picture.
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.