Software engineer interview questions for remote jobs
Remote software engineering interviews test three things: can you code under some pressure, can you reason about design trade-offs, and can you work without someone standing over you. Expect a take-home task or online test, one or two live technical calls and a behavioural round.
These are the questions we see most often in interviews for roles open to Nigerian candidates, with what the interviewer is looking for.
Updated October 2026 by the WorkRemote careers team
On this page
About the role and your experience
Openers that check you understand the job and have done the work.
Walk me through a project you built that you are proud of.
Why they ask
It is the opener in most first calls. They want to see whether you understand your own work at the level of decisions, not just features.
How to answer
Pick one project with real users or real complexity. Cover the problem, your part (not the team's), one hard technical decision and what you would change now. Keep it to two minutes and let them ask follow-ups.
Show a sample answerHide the sample answer
At a Lagos logistics startup I built the dispatch service that assigns riders to orders. The hard part was double assignment when two dispatchers clicked at the same time, so I moved the assignment into a single PostgreSQL transaction with a row lock. Double bookings went from a few a day to none. If I rebuilt it now I would add a proper job queue instead of polling.
Why do you want to work for us remotely rather than for a local company?
Why they ask
They want to know you have thought about the role, not just the dollar pay.
How to answer
Be honest that pay matters, but give a specific reason about their product, stack or team. Show you have read their site, used the product or read their engineering blog.
How do you use AI coding tools in your work?
Why they ask
Almost every team uses them. They want to know you use them responsibly.
How to answer
Give concrete uses (boilerplate, tests, reading unfamiliar code) and your rules: you review every suggestion, never paste secrets or client code into tools the company has not approved, and you can explain everything you commit.
Technical questions
What you know and how you'd do the work, often with a live task or test.
What is the difference between a process and a thread?
Why they ask
A basic computer science check that tells them whether you understand concurrency at all.
How to answer
A process has its own memory space; threads within a process share memory. Threads are cheaper to create and communicate faster, but shared memory means race conditions and the need for locks. Mention how your language handles it, for example Node.js runs your JavaScript on one thread with an event loop, and Python's GIL limits CPU-bound threads in CPython.
Given an array of integers and a target, return the indices of two numbers that add up to the target.
Why they ask
Two Sum is a common warm-up. They watch how you communicate, not only whether you know the trick.
How to answer
State the brute force first (two loops, O(n²)), then improve: walk the array once, store each number's index in a hash map, and for each element check whether target minus that element is already in the map. That is O(n) time and O(n) space. Say the edge cases out loud: duplicates, no answer, negative numbers.
How would you design a URL shortener?
Why they ask
A standard system design question for mid-level roles that tests whether you can reason about scale, storage and trade-offs.
How to answer
Clarify requirements first (reads versus writes, custom aliases, expiry, analytics). Then cover generating short codes (base62 of an auto-increment ID or a random key with collision checks), storage (a key-value lookup by code), caching hot links in Redis, redirect status codes (301 versus 302 and the analytics effect) and how you would scale reads. Finish with what you would monitor.
What happens when you type a URL into a browser and press Enter?
Why they ask
It shows how much of the web stack you understand end to end.
How to answer
Go in order: DNS lookup, TCP connection, TLS handshake for HTTPS, the HTTP request, the server and any load balancer, the response, then the browser parsing HTML, fetching CSS and JavaScript and rendering. Go deeper on whichever part matches the role.
How do you find out why an API endpoint has become slow?
Why they ask
Debugging production issues is a big part of the job and is hard to fake.
How to answer
Describe a method: check monitoring to see when it started and whether it correlates with a deploy or traffic; look at traces to find the slow span; if it is the database, run EXPLAIN ANALYZE and look for sequential scans or N+1 queries; then fix, measure again and add an alert.
Show a sample answerHide the sample answer
Last year our orders endpoint went from 200ms to 3 seconds. The Datadog trace showed 80 separate SELECT queries per request, an N+1 from the ORM loading each order's customer. I switched to a join with eager loading and it dropped back to about 150ms. I also added a test that fails if the query count goes above a limit.
Explain the difference between SQL and NoSQL databases. When would you pick each?
Why they ask
They want to know you make choices for reasons, not habit.
How to answer
Relational databases like PostgreSQL give you schemas, joins and transactions, which suit most business data. Document stores like MongoDB or key-value stores like DynamoDB suit flexible or very high-volume access patterns where you know your queries in advance. Say that PostgreSQL is a sensible default and give a real case where you would choose otherwise.
How do you make sure your code works before you merge it?
Why they ask
Remote teams depend on engineers who test their own work.
How to answer
Talk about unit tests for logic, integration tests for database and API boundaries, running the change locally against realistic data, CI checks and a small, readable pull request. Mention a bug your tests caught.
Behavioural questions
Past situations. Answer with a real example: what happened, what you did, what changed.
Tell me about a time you disagreed with a technical decision.
Why they ask
They are checking whether you can disagree respectfully and then commit, which matters more when people only meet on calls.
How to answer
Use a real example. Say what you proposed, the evidence you brought, how the decision went and what you did afterwards. It is fine if you lost the argument; show you supported the final choice.
Show a sample answerHide the sample answer
My lead wanted to add a second database for search. I thought PostgreSQL full-text search would be enough for our data size, so I wrote a short benchmark with our real product table and shared it in the thread. We went with Postgres and agreed to revisit at a million rows. If he had chosen Elasticsearch, I would have built it properly anyway.
Tell me about a bug you shipped to production.
Why they ask
Everyone ships bugs. They want honesty and a sense of how you respond.
How to answer
Pick a real one. Explain the impact, how it was found, how you fixed it and what you changed so it would not happen again. Do not blame others.
Where do you want to be in three years?
Why they ask
They want to know whether you will stay and grow, or leave after six months.
How to answer
Tie your answer to the role: deeper ownership of a system, moving towards senior or tech lead, learning a part of their stack. Avoid saying you plan to start your own company next year.
Situational questions
Hypotheticals about problems you'd meet in the job.
You are given a vague ticket: "Make checkout faster." What do you do?
Why they ask
Real tickets are often vague. They want to see you clarify scope before writing code.
How to answer
Ask what faster means and for whom, find the current numbers (page load, API latency, drop-off), agree on a target, then propose the smallest change that moves it. Write the plan back to the ticket so everyone agrees.
Your pull request has been waiting for review for two days and you are blocked. What do you do?
Why they ask
Tests initiative and tact.
How to answer
Ping the reviewer politely with what you need and why it is blocking, offer a short call, and if the team has a rule, ask someone else. Meanwhile, start the next task on a separate branch.
Remote work questions
How you'll work from Nigeria with a team elsewhere: hours, power, internet, communication.
How do you stay productive when your team is six hours behind you?
Why they ask
They worry about lost days waiting for answers.
How to answer
Explain how you plan around it: write questions with full context before their day starts, keep a second task ready in case you are blocked, and put decisions in writing so nobody needs a call.
Show a sample answerHide the sample answer
With my last US client I front-loaded questions. By 1pm Lagos time I would post anything I needed answered with screenshots and the options I saw, so it was the first thing they read at 8am Eastern. I always kept a smaller ticket ready so I was never just waiting.
What is your setup for power and internet?
Why they ask
Interviewers know about Nigerian power and network problems, even if they are too polite to say so.
How to answer
Be specific and calm. Name your backup and how long it lasts, and your two internet sources on different networks. Mention that you have worked a full day on backup before.
How do you communicate progress when nobody is checking on you?
Why they ask
Silence is the most common reason remote contractors are let go.
How to answer
Describe a habit: a short end-of-day update in Slack or the ticket, flagging blockers as soon as they appear, and small pull requests so progress is visible.
Remote interview tips
Test your camera, microphone and internet an hour before the call, and have your hotspot ready on a different network in case your main line drops. If the power goes during an interview, message the interviewer on the chat or email straight away, rejoin and carry on; it happens and most interviewers are understanding if you handle it calmly.
For live coding, think out loud. Silence for three minutes reads as being stuck, even when you are not.
Confirm the time zone in writing. "Tuesday 3pm" from a US recruiter could be 3pm Pacific, which is 11pm in Lagos in summer and midnight in winter. Put both times in your reply.
Questions people ask
How many interview rounds do remote software engineering jobs have?
Usually three to five. A typical sequence is a recruiter screen, a take-home or online test, one or two technical calls, and a hiring manager or culture call. Vetting platforms like Toptal add their own stages before you meet clients.
Are take-home tests paid?
Usually not. Expect two to six hours of unpaid work. If a task looks like several days of real product work, it is fair to ask whether it is paid or can be shortened.
What language should I use in a live coding interview?
The one you know best, unless the job says otherwise. Python and JavaScript are popular because they are short to write. Interviewers care about reasoning and clear code more than the language.
Will employers ask about my internet and power in Nigeria?
Often, yes, or they will wonder silently. Mention your backup power and second internet connection briefly, ideally before they ask.
Updated October 2026 by the WorkRemote careers team
Interview questions for roles close to software engineer
- Backend Developer
A backend developer builds the servers, APIs, databases and background jobs that apps run on, typically in Node.js, Python, Go, Java or C#. Nigerian backend developers are hired remotely by foreign companies, especially those with fintech or payments experience, though most remote roles want two or more years of production work.
- Frontend Developer
A frontend developer builds the part of a website or web app people see and click, mostly with HTML, CSS, JavaScript or TypeScript and React. It is one of the most common remote tech jobs open to Nigerians, but it is also the most crowded, so you need polished, fast, accessible work to get noticed.
- Full Stack Developer
A full stack developer builds both the user interface and the server side of a product, often React or Next.js on the front and Node.js, Python, Laravel or Rails behind it with a SQL database. Startups hiring remotely like full stack developers because one person can ship a whole feature, and many Nigerians land remote work this way after a few years at an agency or startup.
- DevOps Engineer
A DevOps engineer builds and runs the machinery that takes code from a developer's laptop to production: CI/CD pipelines, Docker images, Kubernetes clusters and Terraform-managed infrastructure. It is very doable remotely from Nigeria, but it is rarely a first tech job, because employers are handing you access to production.