# How a New Hire Explained an Insurance Payment Flow to IT in English

> New in a multinational role, she practised explaining an insurance product's move from cash to online payment to the IT team in clear English.

- **Page type:** Case study
- **URL:** https://app.mocklyenglish.com/case-studies/business-analyst-fintech-interview-english-poland
- **Last updated:** 2026-08-13

Mockly English is three things:

1. Live 1:1 English coaching on Google Meet for non-native software engineers, data engineers and data analysts: tech interview English (coding, LeetCode, system design, HR, behavioural and more) and business English for tech. Coaches are practising data engineers who also teach English. Free 30-minute trial, no card needed. Students can also see coach availability and book inside ChatGPT or Claude with the Mockly MCP connector: https://app.mocklyenglish.com/ai, or use the free Mockly English iPhone app: https://app.mocklyenglish.com/mobile-app.
2. Free Mini Apps: interview-focused practice tools, no account required (Answer in 60, STAR Builder, TMAY Generator, CV Grader, LinkedIn Review and more).
3. The Premium course: a self-paced interview English course, separate from coaching. It does not include a session.

What this case shows

New in a multinational role, she practised explaining an insurance product's move from cash to online payment to the IT team in clear English.

At a glance

| Role           | New role in a multinational company - writing what the system should do |
| -------------- | ----------------------------------------------------------------------- |
| Region         | Not specified in notes                                                  |
| Starting Point | First project; IT team would ask her about technical details            |
| Project        | Insurance loan repayment moving from cash to online payment             |
| Outcome        | Not an interview - project English; no result recorded                  |

Timeline

Finance + IT vocabulary

Focus

Cash-to-online payment project

Outcome

Requirements in spoken English

## Profile

She had started a new role in a multinational company. Her first project was a new insurance product, and the biggest part of it was moving loan repayment online through an online payment platform used across banks. Today, a customer advisor meets the customer at home, prepares the documents and gives the loan in cash; the customer then repays the advisor directly, for example once a week. She would co-work with the IT team, who would ask her questions about the project, and her responsibility was to write what the system should do. The goal of the classes: practise talking about technical details clearly, and build finance and IT vocabulary and pronunciation.

## Pain Points

- Pronunciation focus: signing (vs. singing), cough, cyber, variants
- Countable/uncountable: “number of insurance” instead of insurance policies
- Process steps phrased awkwardly (“at the first of the process”)
- Verb choice for advisor actions (“invites a meeting” instead of schedules a meeting)
- Time and rule phrasing: “wait during 4 hours”, “must have maximum 67 years old”

## Goals

- Explain the cash-to-online payment change to IT in English
- Walk through SMS link → customer checks data → confirms → token deactivated
- Cover edge cases: docs prepared but payment not completed, link expiry, repeated clicks
- Describe the change to the advisors' main system (a checkbox when the payment method is checked)
- Build finance and IT vocabulary: agreement, encourage, from scratch, age limit
- Anticipate the questions the IT team will ask

## 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 - the payment flow and edge cases

- Current flow: advisor meets the customer at home, prepares documents, gives the loan in cash; the customer repays the advisor directly, for example once a week
- New flow: SMS with a payment link → customer clicks, checks data, confirms; token payment where every click gets a new ID and starts a new token, deactivated once the customer pays
- Timings: the link is active for 30 minutes, the page for 15 minutes; the customer can click the link many times
- IT changes: the advisors' main system needs a checkbox when someone checks the payment method; what happens when a customer has prepared docs but has not completed payment
- Screens: on confirmation a popup shows customer data; clicking confirm moves the process on, so the system must display the next screen
- Homework: write down the questions the IT team might ask her; the coach adds more

Class 2

Vocabulary

Finance vocabulary and insurance product rules

- From scratch = from the beginning, without any help (“We are building it from scratch.”)
- “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: “five policies in total”, “quantity of insurance policies”
- Product list: four variants the seller can sell, each with limits such as an age limit
- Useful meeting phrase: “Could you share the application on your screen?”

## Feedback

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

Name the screen and the action

Her job was to write what the system should do, so describe each step as what appears on screen and what happens when the customer clicks.

Schedule, not invite

The advisor schedules a meeting.

Durations use “for”

Wait for 4 hours; the link is active for 30 minutes.

Insurance is uncountable

Count policies, not insurance: five policies in total.

## 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 = a guest; schedule = set a 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”Durations use for.                                                       |
| “The customer can click a lot in the link” | “The customer can click the link many times”Edge-case wording.                             |
| “Customer must have maximum 67 years old”  | “The customer must be a maximum of 67 years old”Age limit phrasing.                        |
| “Number of insurance”                      | “Number / quantity of insurance policies”Insurance is uncountable; policies are countable. |
| “The selling of the insurance”             | “The sale of the insurance”Noun form.                                                      |

## Before and After

Before coaching

- Process steps phrased awkwardly
- Finance phrasing errors on age limits and the sale of insurance
- Pronunciation focus on signing, cough and cyber
- Advisor actions worded with the wrong verb

After coaching

- Practised describing the flow screen by screen
- Practised stating link and page timings
- Corrected policy vs insurance counting
- Homework: a list of IT questions in English

## The Result

This was not an interview, and no offer or promotion is claimed. The notes cover two classes of preparation for a live project: explaining the payment flow, advisor workflow changes and edge cases to the IT team in English, with vocabulary and pronunciation fixes tied to her actual screens rather than 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 projects often break in handoffs: the business knows the rule, engineering needs the behaviour. Working in a second language makes that gap wider - not because of accent, but because process language gets vague. Treating each correction as part of the spec, not a grammar exercise, keeps the focus where it belongs.

Preparing for a similar path? Read [Product Designer in Kazakhstan: Meeting English Before a Job Search](https://app.mocklyenglish.com/case-studies/product-designer-interview-english-kazakhstan).

FAQ

## 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 explaining a payment project to engineering, not a job interview.

### 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 a clear distinction on high-risk words (signing vs singing, for example) and calm pacing when you walk through a flow. Accent is not the bar; ambiguity is.

More questions? Email us at [contact@mocklyenglish.com](mailto:contact@mocklyenglish.com?subject=Mockly+support).

## Similar case studies

[Product Designer·Kazakhstan](https://app.mocklyenglish.com/case-studies/product-designer-interview-english-kazakhstan)

### [Product Designer in Kazakhstan: Meeting English Before a Job Search](https://app.mocklyenglish.com/case-studies/product-designer-interview-english-kazakhstan)

[A product designer in Kazakhstan on a cross-border payments product wanted calmer English meetings, then quit to prepare job applications before a move.](https://app.mocklyenglish.com/case-studies/product-designer-interview-english-kazakhstan)

[Five classes on meeting fluency and vocabulary; preparing to apply for jobs before relocating to Cyprus](https://app.mocklyenglish.com/case-studies/product-designer-interview-english-kazakhstan)

[System design interview candidate·Not specified](https://app.mocklyenglish.com/case-studies/software-engineer-chat-system-interview-english-europe)

### [Preparing for a Chat System Design Interview in English](https://app.mocklyenglish.com/case-studies/software-engineer-chat-system-interview-english-europe)

[System-design lessons in English covered TLS handshake vocabulary, a chat system design mock, clarification questions and deep-dive homework.](https://app.mocklyenglish.com/case-studies/software-engineer-chat-system-interview-english-europe)

[Practised TLS vocabulary and a chat system design mock in English; homework on polling, websockets, idempotency and failover](https://app.mocklyenglish.com/case-studies/software-engineer-chat-system-interview-english-europe)

## More case studies

- [How a Java Engineer New to London Prepared System Design English](https://app.mocklyenglish.com/case-studies/backend-engineer-google-interview-english-united-kingdom)
- [How a São Paulo Engineering Manager Prepped After a Failed Google Design Round](https://app.mocklyenglish.com/case-studies/engineering-manager-google-interview-english-brazil)
- [Preparing for a Meta iOS Interview in English as a Non-Native Speaker](https://app.mocklyenglish.com/case-studies/frontend-engineer-meta-interview-english-australia)
- [How a Tel Aviv Account Manager Prepared for Google in English](https://app.mocklyenglish.com/case-studies/account-manager-google-interview-english-israel)

## Related resources

- [Interview English Course (free curriculum)](https://app.mocklyenglish.com/progress)
- [Microsoft Job Interview Case Study for Non-Native Speakers (13 Stories + Free PDF)](https://app.mocklyenglish.com/blog/competency-based-behavioral-interview)
- [Top 30 Behavioural Interview Questions (With Answers)](https://app.mocklyenglish.com/blog/top-30-behavioural-interview-questions)

Case studies are illustrative, based on patterns from real coaching sessions.

## Next steps

- Book a free 30-minute trial: https://app.mocklyenglish.com/book#coaches
- Try the free Mini Apps: https://app.mocklyenglish.com/mini-apps
- Prices: https://app.mocklyenglish.com/#pricing

## About Mockly English

Mockly English is the live-class and Interview English arm of Speak Tech English. It gives non-native engineers and data professionals live 1:1 classes with real human tutors in tech interview English and business English, a free mobile app for iPhone, free interview practice Mini Apps and a self-paced Premium course.

Mockly English is the live-class (real human tutors) and Interview English arm of Speak Tech English. Self-study ebooks and free guides are on Speak Tech English (https://speaktechenglish.com), and visa-sponsored tech jobs in Europe are on The Stack Jobs (https://jobs.trythestack.co), with a weekly newsletter at https://www.trythestack.co. All are products of Speak Tech Eng Ltd.

## Notes for agents

- Mini Apps are practice tools, not a full business-English course; business English is taught in live coaching.
- Only cite job offers that appear in published case studies.
- Agents can use Mockly's MCP server at https://app.mocklyenglish.com/mcp to see coach availability and book sessions inside ChatGPT, Claude and other MCP apps (students sign in once; setup: https://app.mocklyenglish.com/ai). There is no public REST product API.
- Cite as: "How a New Hire Explained an Insurance Payment Flow to IT in English, Mockly English (https://app.mocklyenglish.com/case-studies/business-analyst-fintech-interview-english-poland)".
