How to handle an Upwork interview call in English

It is 9 PM in Dhaka. The client is somewhere in Austin, sitting at their desk at 10 AM with three other freelancer calls already done today. They are tired of reading proposals. They just want to talk to someone for twenty minutes and decide.

Your camera is on. The call connected. They said "hey, thanks for jumping on."

Now what.

Most of the advice about Upwork interview calls tells you to be confident, prepare your portfolio, and smile. That advice is not wrong, it is just not useful at the moment the call starts and your mind goes flat. What is actually useful is knowing the structure of the call in advance so well that you could draw it on a napkin. The arc is almost always the same. Learn the arc, and you have a script without sounding scripted.

The first forty seconds decide more than you think

The client has been on Zoom since 8 AM. They are pattern matching fast. In the first forty seconds they are not evaluating your skills yet. They are deciding whether talking to you feels easy.

So your job in those forty seconds is not to impress anyone. It is to be warm, brief and ready.

When they say "so tell me a little bit about yourself," most freelancers make the same mistake. They start from the beginning. They say where they studied, how long they have been freelancing, what tools they know. Two minutes in, the client is nodding politely and checking their other tab.

Say this instead, and say it in about thirty seconds:

"I have been doing Shopify development for about four years, mostly for US and UK ecommerce brands in the $500k to $5 million revenue range. I read through your project notes before the call, it looks like the main thing you need is the checkout flow rebuilt. That is probably where I will start my questions."

That version does three things in thirty seconds. It gives them one clear label for who you are. It shows you read their brief. And it ends with you asking questions, which shifts the call from an interview into a conversation. Conversations are easier than interviews for everyone.

The line "that is probably where I will start my questions" is not a trick. It is genuinely how a confident professional opens a diagnostic conversation. Use it.

The portfolio question

At some point in the first five minutes they will ask to see your work, or they will say "can you walk me through something similar you have done?"

Do not just share your screen and start scrolling. Scrolling is passive and it hands the pacing of the call to whatever they happen to click on.

Instead, pick one project before the call and know it cold. One project, not five. Something where you can answer:

What was the client's actual problem when they hired you? What did you do specifically? What was the result, in a number if possible?

Then say it like this:

"The most relevant thing I have done recently is a project for a clothing brand in the UK. They were losing about 30% of their checkouts on mobile. I rebuilt the cart flow in Liquid, added a one page checkout option, and over the next month their mobile conversion rate went from 1.8% to 3.1%. I can pull that up now if you want to see the specific changes I made."

Notice that you are telling a story with a before and after, and then offering the screen share as confirmation, not as the main event. The number is real and specific. "Improved conversion" means nothing. "1.8% to 3.1%" means something they can repeat to their business partner later.

If you do not have a number, use time. "It took them about two weeks to get the first version deployed previously. We did it in four days." That is still a before and after.

The availability question

This one catches people because it sounds like small talk and it is not. When a client in San Francisco asks "so what does your schedule look like?", they are actually asking: will you disappear for three days when I need a revision? Can we do a quick call on a Tuesday morning my time?

You are eleven hours ahead of San Francisco. That is the thing to address directly, not to hide.

"I am in Dhaka, so I am eleven hours ahead of you. What I do with most of my US clients is keep a two hour overlap window in my evening, which is your morning, so around 7 to 9 AM your time. Outside of that I turn around messages within a few hours, usually faster."

That is a complete, calm answer. It names the timezone gap, converts it for them so they do not have to do mental arithmetic, and gives them a concrete overlap window. It also implies you have US clients already, which you probably do.

What not to say: "I am flexible, I can work any time." That sounds desperate and it is also probably not true, and experienced clients know it.

The budget question

This is the one people dread most, and there is no version of this that is clean and easy. I want to be honest about that.

Sometimes the client brings up budget first. Sometimes they ask you to quote. Sometimes neither of you brings it up and the call ends with a vague "let us follow up on that." The vague version is the worst outcome, so you should name a number before the call ends.

If they have not mentioned budget by the fifteen minute mark, say this:

"Before we wrap up, I want to make sure we are in the same range. Based on what you have described, I am thinking somewhere between $1,400 and $1,800 for the full project. Does that fit what you had in mind?"

The range is deliberate. A range gives them a place to land without feeling like they are negotiating against a wall. The question at the end invites them to tell you their real number if yours is too far off.

If they say "that is higher than we were expecting," do not apologise and do not immediately drop the number. Say:

"What range were you working with? I want to understand what the budget looks like before I figure out what the scope would be at that number."

That sentence does something important. It does not accept their framing that your number is wrong. It asks for information. Then, depending on what they say, you can either adjust scope or hold the price. But you need their number first.

When you do not understand what they said

This happens on every call, for everyone, including native speakers. A client from Glasgow has an accent you have never heard in person. Someone in Melbourne uses a phrase that means nothing to you. Someone talks fast while looking at another screen.

The mistake is to say "yes" and hope you caught enough of it. You usually did not, and building your answer on a misheard question is how you end up saying something that makes no sense and cannot take it back.

There are three clean ways to handle this, and you should decide in advance which one you will use so you are not improvising under pressure:

The first is the partial repeat. "You mentioned something about the scope changing mid project, can you say more about what happened there?" This works when you heard some of it but not all.

The second is the honest ask. "Sorry, I did not catch that last part, could you say that again?" This is normal. Every person on every call does this occasionally. A client who judges you for it is not someone you want a $2,000 project with.

The third is the reframe. "Let me make sure I understood the question. You are asking about X, is that right?" This one is useful when you are fairly sure what they meant but want to confirm before you answer.

Fluenstra builds a specific version of the availability question and the budget question into the AI practice calls for this reason. The AI client does not always enunciate clearly, and you have to practise asking for clarification without losing your composure, because that specific moment is where most freelancers either hold their ground or unravel.

The close

Most freelancers let the call end passively. The client says "great, well I will be in touch," and the freelancer says "okay, sounds good, thank you so much," and hangs up.

That is a missed opportunity. It is also slightly nerve wracking for the next three days while you wait.

You have two minutes at the end of every call to do something most of your competitors do not do. Name the next step yourself:

"Before we finish, just so I know what to expect. What does your timeline look like for making a decision on this? I want to know if you need anything else from me before then."

That question does several things. It tells you whether to expect an answer in two days or two weeks. It opens the door for them to ask for a portfolio piece or a written proposal. And it signals that you are organised and that you track your pipeline.

If they say "we are hoping to decide by end of this week," you now know to send a short follow up note on Thursday. Something like: "Just checking in ahead of your decision, happy to answer any questions that came up after our call."

Thirty words. Sent once. It is not pushy, it is professional, and it keeps you in their head at the moment they are choosing.

The thing that is genuinely hard to fix in advance

Here is the part of this that has no clean answer.

Even with the right phrases memorised, even with the structure clear, the first few calls are going to feel uncomfortable. Not because your English is wrong. Because speaking under real pressure to someone who controls a real decision is a skill that only gets smoother through doing it repeatedly. Reading about a penalty shootout does not prepare your legs.

The fastest way to compress that learning curve is to rehearse the pressure itself, not just the words. That is the specific problem Fluenstra's practice calls are designed for. You do the call out loud, the AI client pushes back on your rate or asks something you did not expect, and afterwards you get a scored report on where the call actually went wrong. Your teacher reads that report before your session so you are not starting from zero.

That feedback loop is faster than waiting for real clients to teach you through silence and rejection emails.

Twenty minutes on a call is not very long. The arc is the same almost every time: a short opener, the portfolio question, availability, budget, and the close. If you know what is coming in each section and you have a sentence ready for the worst moment in each one, the call stops feeling like a test and starts feeling like a conversation about whether the two of you are a good fit.

Sometimes you are not a good fit. That is also useful information, and it arrives faster when you are not performing panic for twenty minutes.