Industries
Why BFSI employees leave and how to understand why
Sales producers, branch staff and operations teams in financial services leave for different reasons. How to ask what shaped their decision and act on it.
7 min readRead article
Banking, Financial Services and Insurance
HR for Fintech Companies: Product Teams, Operations and Speed
A fintech company builds financial products on technology, with engineers, risk staff and customer teams growing faster than its processes. Engineers and risk staff come from different worlds, so levels, equity explanations and system access need settling before the next hiring wave.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsHow the work is organised
A fintech company may offer payments, lending, investments, insurance distribution or accounting tools through an app or platform. The team usually combines engineers, product and data staff with people from banking, credit, risk and operations, and the two groups have different habits and pay expectations. Headcount often doubles within a year, funding rounds change plans, and customer support and collections teams grow alongside the technology team. Founders are close to the product and often still run HR themselves. See also HR for banking, financial services and insurance.
Who does the work
- Engineers and data staff
- Product and design staff
- Risk, credit and fraud analysts
- Customer support and onboarding teams
- Operations and reconciliation staff
- Sales and partnership teams
- Founders and functional heads
Where HR strains in fintech companies
Two cultures under one roof
Staff from banks expect procedure and grades, while product teams expect freedom, and neither understands the other's reasons.
Hiring outruns structure
People join faster than titles, reporting lines and pay bands are defined, so offers vary and early staff feel overtaken.
Equity promises are loosely understood
Staff were told about stock options at joining, but few can explain the vesting, the cliff or what happens when they leave.
Support and operations burn out
Customer teams absorb every growth spike and every outage, and they are paid and recognised far below the engineers.
Roles shift with every pivot
A change of product or a funding decision rewrites jobs, and people learn about it from rumours.
Data handling needs discipline
Staff have access to customer and financial data, and access rights, onboarding rules and exit steps are often informal.
Layoff risk sits close
A slow quarter or a failed round can mean cuts, and a company without clear process handles them badly.
What a working HR set-up looks like
- 01
Set bands and levels early
A simple ladder of levels and pay bands for each function so offers and promotions follow one logic. See compensation benchmarking.
- 02
Explain equity in plain words
A one-page note and a conversation for each holder covering vesting, exit and what the grant is and is not worth. Confirm the legal and tax treatment with a qualified professional.
- 03
Create a structured hiring loop
Defined interview stages, a skills task and a scorecard per role, using the workforce and recruitment process and the IT and specialised recruitment approach.
- 04
Treat support as a career, not a stop
Clear levels, rotation into risk or operations and recognition for the customer teams. The competency and talent management work helps.
- 05
Tie access to joining and leaving
A checklist linking system and data access to role, handed on at joining and withdrawn at exit. See exit and offboarding.
What to put in place first
- List the current levels and pay of everyone in one function and look for gaps you cannot explain.
- Ask five option holders to explain their grant, and note what they get wrong.
- Check who still has system access after leaving in the last six months.
- Confirm with a qualified professional the financial-sector, data and employment obligations that apply to your fintech business.
Confirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
Where GullyHR helps
- IT and specialised recruitment
Hiring engineers, data and risk staff with a clear process and fair offers.
- Compensation benchmarking
Bands and levels that make offers and promotions consistent as the team grows.
- Organisation design
Reporting lines and team shape that survive a pivot or a hiring spurt.
- HRMS implementation
A system for records, leave and onboarding before spreadsheets stop coping.
Every engagement starts by recording where you stand, and every later report compares against that. We do not promise outcomes. Start with a free conversation, or see the paid HR Diagnostic.
Blogs worth reading first
From the GullyHR blog: one on HR in banking, financial services and insurance, and one on each of the topics this page points to.
HR Management
"We need two more people": the headcount plan nobody wrote
Hiring decisions made one request at a time, in the month the pain is worst. What a workforce plan contains and why a twelve-month view changes what you hire.
7 min readRead article
HR Management
Salary bands for SMEs: building grades when you have never had any
Most salary structures grew one negotiation at a time. How to build grades and bands from what you already pay, without repricing everybody at once.
8 min readRead article
Guides
What to automate first in HR (and what to leave alone)
Automating a broken process makes it faster and harder to fix. How to choose what goes first, and which tasks should stay manual.
7 min readRead articleMore on the GullyHR blog.
Questions owners ask
Usually before about twenty to thirty people, when offers, leave and reporting lines begin to differ from person to person. A light structure early is cheaper than an overhaul later.
Be clear about which rules are fixed for good reason, such as controls and data handling, and which are open to team choice. Shared language for decisions helps more than a shared dress code.
In plain writing and in person, with examples and without promises about future value. Direct people to a qualified professional for tax questions.
Offer levels and a route into other teams, protect shifts and breaks, and recognise their input into the product. A support job with no future is a short stay.
Yes. We start with a conversation about the team and what is not working, and can work on specific processes or on a part-time basis through fractional HR.
More on HR for banking, financial services and insurance
All 10 business types in banking, financial services and insurance · Find another business type
BanksLending businesses and loan officersWealth management firmsCredit services companiesCo-operative banks and credit societiesPrivate equity and venture firmsHR Strategy and Workforce Planning in banking, financial services and insuranceCompensation, Payroll and Benefits in banking, financial services and insuranceHR Technology and Automation in banking, financial services and insurance
See all HR topics for banking, financial services and insurance, or another industry.