How a Polish Business Analyst Explained FinTech Products in English

The payment flow was clear in Polish. Explaining it to the IT team in English was not.

At a glance

Role	Business analyst (insurance / payments)
Region	Poland · multinational
Starting Point	Strong domain knowledge; English slipped on process detail
Project	Online loan repayment via PayPro (replacing cash)
Outcome	Requirements and edge cases explained clearly to engineering

Timeline

Finance + IT vocabulary

Focus

Pay-by-link insurance launch

Outcome

Requirements in live English

7-Day Free Trial

Land your dream tech job. In English.

Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches

Start freeNo card needed

500+ tech pros preparing for global roles

Courses · Coaching · Mock Interviews

“The IT team will ask me questions about the project — I need to practice talking about technical details clearly, with the right finance and insurance words.”
— Business analyst · FinTech / insurance

Profile

A business analyst in Poland, starting a new role at a multinational insurance company. The first major project: launch online loan repayment through PayPro — a bank-wide payment platform — while advisors still meet customers in person today and collect cash weekly. She co-works with the IT team when they ask how the product should behave. Classes focused on explaining flows, edge cases, and screen behaviour in English, not on a coding interview loop.

Pain Points

Explaining token payments and timeouts while mixing tenses
Pronunciation collisions: signing vs singing, cough, cyber
Countable/uncountable errors: “number of insurance” vs policies
Process steps described vaguely (“at the first of the process”)
Passive or awkward advisor/customer roles (“invites a meeting” vs schedules)
Writing what the system should do without crisp screen-by-screen language

Goals

Explain the cash-to-digital payment change to IT in English
Walk through SMS link → customer confirmation → token deactivation
Cover edge cases: unpaid after docs, link expiry, multiple clicks
Describe advisor workflow changes (checkbox, main system updates)
Build finance + IT vocabulary: agreement, encourage, from scratch, age limits
Anticipate questions the IT team will ask — and ask her own
Clear pronunciation in multinational meetings

Lesson Notes

These are the classes we actually ran — not a generic curriculum. Each one started from a real interview question.

Class 1

Payment flow

Project intake — PayPro repayment

Legacy flow: advisor visits customer, prepares documents, disburses loan in cash; customer repays advisor weekly in cash
New flow: SMS with payment link → customer checks data → confirms; token payment with new ID per click; link inactive after 30 minutes
IT must update advisor main system: checkbox when payment method verified; handle customer with prepared docs but incomplete payment
Homework: list questions IT might ask; coach will add more

Class 2

Requirements detail

Edge cases and screens

Wait during 4 hours → wait for 4 hours (customer has docs but payment still active)
Link active 30 minutes; confirmation page 15 minutes; customer can click link many times
Screen flow: confirmation popup with customer data → confirm → next screen must load
Responsibility in class: write what the system should do at each step — in English

Class 3

Insurance product rules

Finance vocabulary and grammar

From scratch = built without prior help — useful for greenfield features
Age rules: “Customer must have maximum 67 years old” → “The customer must be a maximum of 67 years old”
The selling of the insurance → the sale of the insurance; limit age → age limit
Insurance is uncountable; count policies: “five policies in total”, “quantity of insurance policies”
Product catalogue: four variants sellers can offer, each with limits

Feedback

Coach notes from those sessions, kept as they were given in class.

Screen-by-screen beats abstract process

When IT asks “what happens next?”, name the screen, the data shown, and the action — not only the business rule.

Advisor vs customer voice

The advisor schedules a meeting; the customer receives the link. Role clarity prevents implementation bugs in English.

Time boxes need exact prepositions

Link active for 30 minutes; wait for four hours — small grammar fixes change whether engineering trusts the spec.

Countable nouns in insurance

Insurance (uncountable) vs policies (countable). Wrong forms sound unprofessional in a multinational review.

Common Mistakes

Corrections from live answers — the same patterns that showed up in class.

Heard in class	Use instead
“The advisor invites a meeting”	“The advisor schedules a meeting” Invite = guest; schedule = set time.
“At the first of the process”	“At the beginning / start of the process” Sequence language for IT walkthroughs.
“Wait during 4 hours”	“Wait for 4 hours” Duration waits use for.
“Customer must have maximum 67 years old”	“The customer must be a maximum of 67 years old” Age limit phrasing for compliance copy.
“Number of insurance”	“Number of insurance policies” Insurance is uncountable; policies are countable.
“Signing (when meaning signature)”	“Signing — watch pronunciation vs singing” Homophone risk in customer-facing flows.

Before and After

Before coaching

Process explanations jumped steps
Finance grammar errors on age and sale wording
Pronunciation risk on signing / cyber
Passive advisor/customer wording

After coaching

Screen-level requirements in order
Timed token and link rules stated clearly
Policy vs insurance count fixed
Homework: IT question bank in English

Session snapshot

Classes in this set	3+ (Sept 2026 focus)
Domain	Insurance · loan repayment · PayPro
Audience	IT engineering + product
Format	Requirements walkthroughs, not coding

The Turning Point

The shift was narrating the confirmation screen: popup with customer data, confirm click, next screen loads. Before, rules floated in abstract (“payment must complete”). After, each UI state had an English sentence IT could ticket. That is when the IT team stopped asking “can you say that again?”

The Result

Notes end during launch prep — no promotion or offer is claimed. Outcome: she could explain PayPro repayment, advisor workflow changes, and edge cases in English well enough for engineering questions. Vocabulary and pronunciation fixes were tied to her actual screens, not a generic word list.

Advice for Analysts Working With IT in English

Write requirements screen-by-screen before the meeting
Separate advisor actions from customer actions in every sentence
Fix countable nouns in your domain (policies, accounts, transactions)
State timings with for / within consistently — engineers will implement literally
Build a shared question list with IT before each review

Why This Matters for FinTech and Insurance Analysts in English

Multinational launches fail in handoffs: business knows the rule, engineering needs the behaviour. Non-native English makes that gap wider — not because of accent, but because process language gets vague. These classes treated every correction as a spec fix, not a grammar exercise.

Preparing for a similar path? Read How a Product Designer From Kazakhstan Built Interview English.

Practise the vocabulary you will actually say in the interview

No card required. Start with a 7-day free trial — a lesson, a mock interview, or both.

Create your Mockly account →

Frequently Asked Questions

How do business analysts practice English for IT meetings?

Use your real project: narrate one flow end-to-end, then edge cases, then write the questions IT will ask. Fix wording on the same material — not random topics.

Is this the same as interview coaching?

Same method — speak, then feedback — but the goal here was shipping a payment feature with engineering, not a behavioural loop at a named tech company.

What vocabulary matters most in insurance and payments English?

Roles (advisor vs customer), countable nouns (policies), time boxes (link expiry, wait periods), and compliance phrases (age limits, sale of insurance).

Do I need perfect pronunciation for multinational teams?

You need clear distinction on high-risk words (signing vs singing, cyber) and calm pacing on flows. Accent is not the bar; ambiguity is.