How a New Hire Explained an Insurance Payment Flow to IT in English
She knew how the new payment flow should work. The IT team would be asking her the questions - in English.
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.
Learning paths
Practise in the course
Start with your introPractise 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.
Join 500+ preparing for global roles
Other engineers practising interview English

Mockly’s approach is genuinely personalized - they use a variety of methods tailored to your specific needs. With their help, I improved my spoken English and prepared thoroughly for behavioral interview questions across different companies. This not only helped me refine my stories grammatically but also ensured I was using the right examples to answer specific questions effectively.

Mockly has helped me enormously in working toward my goals in Tech. Highly recommended.
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Similar case studies
Product Designer in Kazakhstan: Meeting English Before a Job Search
A product designer in Kazakhstan on a cross-border payments product wanted calmer English meetings, then quit to prepare job applications before a move.
Preparing for a Chat System Design Interview in English
System-design lessons in English covered TLS handshake vocabulary, a chat system design mock, clarification questions and deep-dive homework.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.