Full stack developer interview questions for remote jobs
Full stack interviews test whether you can carry a feature across the whole stack and make sensible trade-offs on your own. Expect questions on React, APIs, SQL, authentication and deployment, plus a practical task and questions about how you prioritise.
These are questions remote startups commonly ask full stack candidates, including those hiring from Nigeria.
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.
Tell me about a feature you built end to end.
Why they ask
They want proof you have really worked across the stack.
How to answer
Pick one feature, describe the data model, the API, the UI and how you tested and shipped it, and one problem you hit. Numbers help: usage, time saved, revenue.
Show a sample answerHide the sample answer
At a Lagos edtech startup I built the results checker for schools. I designed the tables for terms, subjects and scores, built a CSV upload with validation in Laravel, and the parent-facing page in Vue. The hard part was schools uploading files with inconsistent subject names, so I added a mapping step. Around 40 schools used it in the first term.
Why do you want to work at an early-stage startup?
Why they ask
They want to know you understand the trade-offs: less structure, more ownership.
How to answer
Be specific about the problem they are solving and why you like owning features end to end. Show you know it can be messy and that you are fine with that.
Technical questions
What you know and how you'd do the work, often with a live task or test.
Walk me through how you would build a "forgot password" feature end to end.
Why they ask
It touches the database, email, security and UI, so it shows full stack thinking in one question.
How to answer
Generate a random, single-use token, store only its hash with an expiry (say 30 minutes), email a link containing the token, and on submission verify the hash and expiry, update the password hash and invalidate the token and existing sessions. Return the same message whether or not the email exists so attackers cannot find accounts. On the UI, handle expired links clearly.
What is CORS and why does my fetch work in Postman but fail in the browser?
Why they ask
A daily full stack annoyance that many developers solve by guessing.
How to answer
Browsers enforce the same-origin policy; Postman does not. CORS lets a server say which other origins may read its responses, using headers such as Access-Control-Allow-Origin. Requests with credentials or custom headers trigger a preflight OPTIONS request. Fix it on the server by allowing the specific frontend origin, not by using a wildcard with credentials.
Where should validation happen: frontend or backend?
Why they ask
Checks you understand security as well as user experience.
How to answer
Both, for different reasons. Frontend validation gives fast feedback; backend validation is the real protection because anyone can call your API directly. Sharing a schema with Zod (TypeScript) or similar keeps the two in line.
How would you let users upload profile photos?
Why they ask
A practical design question with storage, security and performance angles.
How to answer
Have the backend issue a short-lived presigned URL for S3 or similar so the browser uploads directly, then save the file key in the database. Validate type and size, resize images in a background job, serve through a CDN, and never trust the file name or content type from the client.
How do you keep the UI fast when the API is slow?
Why they ask
Tests whether you think about perceived performance across both layers.
How to answer
Fix the API first if you can (indexes, caching, fewer queries). On the UI, show skeletons, cache and reuse data with TanStack Query or SWR, use optimistic updates for actions likely to succeed, paginate long lists and avoid request waterfalls by fetching in parallel or on the server.
When would you choose WebSockets over polling?
Why they ask
Real-time features such as chat or live dashboards are common in startup products.
How to answer
Polling is simple and fine when updates are infrequent or a few seconds of delay is acceptable. WebSockets or server-sent events suit chat, live tracking or collaborative editing where low latency matters. Mention the extra work: connection handling, scaling across servers with Redis pub/sub, and reconnection on flaky mobile networks.
Design the database tables for a simple project management app with teams, projects and tasks.
Why they ask
Full stack developers at small companies usually own the schema.
How to answer
Tables for users, teams, team_memberships (with a role), projects (team_id), and tasks (project_id, assignee_id, status, due date). Add foreign keys, indexes on the columns you filter by, and timestamps. Discuss soft deletes and how you would enforce that users only see their team's data in every query.
What happens when a Next.js page is server-rendered?
Why they ask
Most full stack roles now use Next.js and they want to know you understand it beyond copy-paste.
How to answer
The server runs the components, fetches data and sends HTML, so the user sees content before JavaScript loads. The client then hydrates, attaching event handlers. With the App Router, server components never ship their code to the browser, and client components marked with "use client" do. Mention caching and when you would use static rendering instead.
How do you deploy safely?
Why they ask
Startups need developers who will not take production down on a Friday.
How to answer
Tests and type checks in CI, preview deployments for review, database migrations that are backwards-compatible, feature flags for risky changes, monitoring after release and a known way to roll back.
Behavioural questions
Past situations. Answer with a real example: what happened, what you did, what changed.
What is the weakest part of your stack, and what are you doing about it?
Why they ask
Full stack candidates often oversell. Honesty here builds trust.
How to answer
Name a real gap (for example, CSS layout, or database performance), and what you are doing to close it, with a recent example.
Describe a time you had to learn a new technology quickly for a project.
Why they ask
Generalists constantly meet unfamiliar tools.
How to answer
Explain how you learned (docs, small prototype, asking someone), how long it took, and what you shipped.
Situational questions
Hypotheticals about problems you'd meet in the job.
You have three requests from the founder, the designer and a customer, all marked urgent. What do you do?
Why they ask
Prioritisation is the hardest part of full stack work at small companies.
How to answer
List them in one place, estimate each roughly, and ask the person who sets priorities (usually the founder or PM) to rank them, with your recommendation. Fix anything that is losing money or data first.
Show a sample answerHide the sample answer
I would post in our product channel: "Three urgent items today: checkout error for some Android users (losing sales), the new pricing page, and the logo update. I suggest checkout first, it's about two hours, then pricing. Okay?" Most founders just want to see you have thought about it.
A customer reports the app is broken but you cannot reproduce it. What do you do?
Why they ask
Debugging across browser, network and server is core full stack work.
How to answer
Ask for details (device, browser, time, screenshots), check Sentry and server logs for that user and time, look at feature flags and recent deploys, and try their conditions, such as a slow network or an older Android phone.
Remote work questions
How you'll work from Nigeria with a team elsewhere: hours, power, internet, communication.
How do you work with a designer and a product manager who are in a different time zone?
Why they ask
Full stack developers talk to everyone, and delays add up.
How to answer
Preview deployments and short screen recordings for async review, batching questions before their day starts, and an agreed overlap window for live calls.
How do you handle being the only engineer on a team?
Why they ask
Early-stage startups often hire one remote developer first.
How to answer
Talk about documenting decisions, writing tests so you can move fast safely, keeping the stack boring, setting expectations with the founder and finding outside reviewers in the community when you need a second opinion.
Remote interview tips
Startups often run a paid or unpaid trial task. Before starting, confirm the scope and the time they expect in writing, and stop at that limit. Write down what you would do next in the README.
Keep a short video demo of your best project ready to share; it rescues an interview when screen sharing fails on a weak connection.
If you are interviewing with a US founder, confirm the time in both zones. Lagos is 5 hours ahead of New York in summer and 6 in winter.
Questions people ask
What is a typical full stack take-home test?
A small app with authentication, a few CRUD screens, a database and tests, built in four to eight hours. Some startups ask you to extend an existing repo instead.
Do full stack interviews include system design?
Usually a lighter, product-focused version: designing tables, APIs and screens for a feature, rather than global-scale distributed systems.
Should I use the company's stack in my take-home?
If they say so, yes. If they let you choose, use what you know best and explain how it maps to their stack.
Updated October 2026 by the WorkRemote careers team
Interview questions for roles close to full stack developer
- 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.
- 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.
- Software Engineer
A software engineer designs, writes, tests and maintains the code behind products, and it is one of the remote jobs Nigerians most often get with foreign companies. Entry-level remote roles are rare, so most people get their first two years of experience locally or through freelance work before landing a dollar-paid contract.
- Python Developer
A Python developer writes software in Python, most often web backends with Django or FastAPI, but also automation scripts, data pipelines and the tooling around AI models. Remote companies hire Nigerian Python developers for all of these, and Python skills also open dollar-paid AI training and evaluation work.