Interview questions for remote hires, by role

Questions

• Walk me through how you'd organize a manager's inbox on your first day. Names a system (labels or folders, rules for what to answer and what to forward) and asks what's off-limits before touching anything.
• Tell me about a time two people wanted the same calendar slot. Explains who they checked with, how priority was decided and how they told the person who got moved.
• Which admin tasks have you fully taken over from someone? Names specific tasks and describes how they learned them, wrote them down and confirmed they had them right.
• How do you keep track of 20 small tasks across a week? Describes a real list or tool they use every day, not "I just remember."
• Write me a two-line email declining a meeting request on my behalf. Short, polite, offers a next step, and matches your tone instead of sounding stiff.
• A vendor's invoice is higher than the quote. What do you do? Doesn't pay or argue; compares the documents, asks the vendor in writing about the difference and sends you both files.
• What's an admin process you made better? Gives a before and after in concrete terms, like fewer steps or less back-and-forth.
• How do you handle access to someone's accounts and passwords? Uses only what they were given, never saves passwords in a browser or notes app, and asks before opening anything sensitive.

Paid test task

• What to send: a messy list of 15 meeting requests and 10 emails (made-up data), plus a one-page note on your calendar rules and priorities.
• Ask for: a proposed calendar for the week, draft replies to 3 of the emails, and a short note listing what they'd ask you before acting.
• Time: 60 to 90 minutes.
• What to look for: your rules followed without reminders, conflicts caught, replies that sound like you, and sensible questions in the note.

What this role pays: Virtual / administrative assistant salary by country

Questions

• Tell me about the hardest customer conversation you've handled. Covers what the customer wanted, how it ended and what they learned, without blaming the customer.
• A customer asks for something our policy doesn't allow. How do you say no? Acknowledges the problem, explains the policy in plain words and offers what they can do instead.
• How do you make sure your answers are right when you're new? Checks the help docs and past tickets first, and asks a teammate before sending anything they're unsure about.
• What does a great support reply look like to you? Answers the actual question in the first line, uses the customer's details and ends with a clear next step.
• How do you handle several chats at once on a busy day? Prioritizes by urgency and wait time, reads each chat's history before replying, and uses saved replies without sounding canned.
• When would you escalate a ticket instead of solving it? Gives concrete triggers like a refund above their limit, a security concern, a threat to post publicly or a bug, and explains how they hand it over.
• How do you write up a bug for the product team? Steps to reproduce, what was expected and what happened, screenshots, and how many customers reported it.
• What do you do in the last 15 minutes of a shift? Closes or hands over open tickets with notes, so the next person doesn't have to ask.

Paid test task

• What to send: 6 realistic tickets (an angry customer, a refund request, a how-to question, a bug report, a vague one-liner and a sales question) plus your help doc or a one-page policy sheet.
• Ask for: a written reply to each, the tag they'd use, and whether they'd escalate it.
• Time: about 60 minutes.
• What to look for: the policy applied correctly, a tone that fits each customer, short replies that still answer everything, and good calls on what to escalate.

What this role pays: Customer support / call center agent salary by country

Questions

• How do you approach a monthly bank reconciliation? Matches transactions, investigates each difference and never forces the balance with a plug entry.
• What do you do when a receipt is missing? Asks the owner once with the date, amount and vendor, and tracks open requests until they're closed.
• How do you categorize a transaction you've never seen before? Checks past entries and the chart of accounts, parks it in a holding account if unsure, and asks before month-end.
• Tell me about a mistake you found in someone else's books. Explains how they spotted it, how they fixed it and how they told the owner without drama.
• What would be in the month-end package you send me? Reconciled accounts, profit and loss, balance sheet, receivables aging and a short note on anything unusual.
• Which accounting tools have you used, and for what kinds of businesses? Names tools, business types and the tasks they did in each, not just "I know it."
• How would you catch up books that are three months behind? Starts from bank statements, works oldest month first and gives you a realistic timeline before starting.
• What do you need from me each week to do this well? Asks for specific things: receipts by a set day, answers to open questions, approval for bills.

Paid test task

• What to send: a made-up bank statement for one month, a matching transaction export with a few planted errors (a duplicate, a wrong category, a missing deposit) and your chart of accounts.
• Ask for: a reconciliation in a spreadsheet and a short note listing every difference and how they'd fix it.
• Time: 60 to 90 minutes.
• What to look for: every planted error found, a note a business owner can follow, and questions instead of guesses wherever the data is ambiguous.

What this role pays: Bookkeeper / accounting clerk salary by country

Questions

• Tell me about a campaign that didn't work. Names what they tried, how they knew it failed, what they changed and what happened next.
• How do you decide where the next dollar of ad budget goes? Talks about cost per lead or per sale by channel, not just clicks or reach.
• How do you set up tracking for a new landing page? Describes conversion events, tagged links and a test conversion before launch.
• What's one test you'd run on our homepage? Picks one specific change, explains why and says how they'd judge the result.
• How do you report results to an owner who isn't a marketer? Leads with spend, leads and cost per lead in plain words, then what they'd do next.
• Which numbers do you check daily, and which only weekly? Daily for spend and anything broken, weekly for trends; shows they won't overreact to one bad day.
• How do you write ad copy for a product you don't know yet? Reads reviews, support tickets or sales call notes to learn how customers talk before writing a word.

Paid test task

• What to send: your homepage URL, a short description of your best customer and a made-up monthly report with spend, clicks and leads by channel.
• Ask for: 3 takeaways from the report, one budget change with the reason, and 2 ad headlines with a one-line rationale each.
• Time: about 90 minutes.
• What to look for: conclusions that match the numbers, a budget move they can defend, and copy written for your customer, not for other marketers.

What this role pays: Digital marketing specialist salary by country

Questions

• Walk me through how you plan a month of content. Starts from business goals and launches, then themes, then the calendar; trends come last.
• Show me an account you grew and what you did. Shares real examples and can explain which posts worked and why.
• A post gets an angry public comment. What do you do? Replies calmly or moves it to a private message, flags it to you if it's serious, and doesn't delete criticism by reflex.
• How do you write in a brand voice that isn't yours? Reads past posts and the website, keeps a short list of words to use and avoid, and asks for feedback on the first batch.
• Which numbers tell you a post worked? Picks metrics tied to the goal, like saves, shares, clicks or inquiries, not only likes.
• How would you turn one blog post into social content? Gives several formats from one source: a quote card, a short video script, a carousel, a question post.
• What would you never post on a business account? Shows judgment: other people's content without credit, jokes about sensitive events, claims nobody has checked.

Paid test task

• What to send: your brand guide or 5 example posts you like, plus one blog post or product page as source material.
• Ask for: a one-week plan for [platforms] with captions and a short description or rough mockup of each visual.
• Time: 60 to 90 minutes.
• What to look for: posts that sound like you, a mix of formats, captions that work without the image, and a clear reason behind each post.

What this role pays: Social media manager salary by country

Questions

• Pick one portfolio piece and walk me through the brief. Explains the goal, the constraints and why they made the main choices, not just which tool they used.
• How do you handle feedback you disagree with? Asks what problem the feedback is solving, offers an alternative and still delivers the requested version.
• What do you need in a brief before you start? Goal, audience, sizes, final copy, deadline, and examples of what you like and don't like.
• How do you keep many small designs on-brand? Uses templates, a style guide and saved colors and fonts, and checks against the guide before sending.
• How do you name and organize your files? Describes a naming and version system you could find things in without asking.
• Tell me about a design that did its job well. Connects the design to a result, like more clicks or approval in the first round.
• How do you keep revision rounds down? Confirms the brief in writing and shares a rough draft early instead of a polished wrong answer.

Paid test task

• What to send: your logo and brand colors, a short brief for one ad in 3 sizes (square, vertical story, wide banner) and the copy to use.
• Ask for: the 3 files ready to upload, plus the editable source file.
• Time: about 2 hours.
• What to look for: the brief followed, text readable at small sizes, a consistent layout across sizes, and a tidy source file with named layers.

What this role pays: Graphic designer salary by country

Questions

• How do you update a live site without breaking it? Works on a staging copy, takes a backup, tests key pages and forms, then deploys at a quiet time.
• Our site is slow on phones. Where do you start? Measures first, then looks at images, scripts and hosting before rewriting anything.
• Tell me about a bug you couldn't reproduce at first. Describes how they narrowed it down: browsers, devices, logs and asking the reporter for details.
• How do you estimate a small change? Breaks it into steps, adds time for testing and says what could make it take longer.
• What do you check before adding a new plugin or library? Maintenance history, overlap with what's already installed, and whether it's needed at all; prefers fewer moving parts.
• How do you hand over your work so someone else can maintain it? Readable code, a short readme and notes on anything unusual.
• How do you make sure a contact form actually delivers leads? Sends test entries, checks the inbox and the CRM, and sets up an alert if submissions stop.

Paid test task

• What to send: a design (an image or mockup) of one page section and access to a test environment or a code sandbox.
• Ask for: the section built and responsive, plus a short note on how they tested it on phone and desktop.
• Time: 2 to 3 hours.
• What to look for: a close match to the design, clean and readable code, a layout that holds up on a small phone, and a note that tells you what they checked.

What this role pays: Web developer salary by country

Questions

• Tell me about a feature you built from start to finish. Covers the problem, their design choices, the trade-offs, how they tested it and what happened after release.
• How do you approach a bug report with little detail? Asks for specifics, reproduces it, writes a failing test, then fixes it.
• What makes a pull request easy to review? Small scope, a clear description of what and why, tests, and screenshots for interface changes.
• Describe a technical decision you'd make differently today. Owns the call and explains what they learned without blaming others.
• How do you keep a remote team informed about your work? Short written updates, early warnings on delays, and decisions written down where others can find them.
• How do you decide code is ready to ship? Weighs tests, review and risk, and can name what they'd never ship without.
• How do you handle a disagreement in code review? Argues the trade-off with examples, and commits to the team's decision once it's made.
• What do you check before deploying a database change? A fresh backup, a migration that can be rolled back, and a test run on a copy with realistic data volume.

Paid test task

• What to send: a small repo in your stack with a short spec for one feature (for example, an API endpoint with input validation) and one known bug.
• Ask for: the feature with tests, the bug fixed, and a pull request description explaining their choices.
• Time: 2 to 4 hours. Keep it there; oversized tasks lose the candidates with the most options.
• What to look for: readable code, sensible tests, a fix for the bug's real cause, and a pull request description you'd be glad to get from a teammate.

What this role pays: Software developer salary by country

Working across time zones

• Our core hours are [hours] in [time zone]. How does that fit your day? Gives a specific answer in their local time and mentions other commitments, not just "no problem."
• How did you stay in sync with a team in another time zone? Written handovers, a fixed overlap window, and planning work so nobody is blocked overnight.
• What would you do if you needed to change your hours for a week? Tells you early, proposes a plan and makes sure nothing urgent falls through.

Communication

• How do you like to get feedback? Answers honestly and gives an example of acting on feedback.
• What goes into a good end-of-day update? Done, in progress, blocked and next, in a few lines.
• Tell me about a misunderstanding over chat or email. Explains how they noticed it, how they cleared it up and what they do differently now.

Home setup and internet backup

• Describe where you work and what equipment you use. A quiet space, a reliable computer and a headset; brings up noise and privacy without being asked.
• What happens if your internet or power goes out? Has a backup, like a mobile hotspot, a second connection or a nearby place to work, and a plan to tell you right away.
• How do you keep work separate from personal use on your computer? A separate user account or browser profile, and no work files on shared devices.

When they get stuck

• Tell me about the last time you were stuck on a task. Tried a few specific things, then asked a clear question that included what they'd already tried.
• How long do you try on your own before asking for help? Has a sensible rule, like 20 to 30 minutes on a normal task and right away on anything urgent or risky.
• What do you do if you make a mistake nobody has noticed yet? Tells you right away, explains the impact and suggests the fix.