Frequently asked full stack developer interview questions across JavaScript, React, Node, APIs and databases — with concise answers. Practise them in a free AI mock interview.
Practise these in a free AI mock interviewProps are read-only data passed from a parent to a child. State is data a component owns and can change over time. Updating state re-renders the component; props change only when the parent passes new values.
JavaScript is single-threaded; the event loop lets it handle async work. Synchronous code runs on the call stack; promise callbacks wait in the microtask queue and timer callbacks in the macrotask queue, running when the stack is empty. Microtasks run before the next macrotask.
DNS resolves the domain to an IP, a TCP (and TLS) connection is made, the browser sends an HTTP request, the server responds with HTML, then the browser parses HTML/CSS/JS, builds the DOM and renders — fetching linked assets along the way.
Never concatenate user input into queries. Use parameterised queries / prepared statements (or an ORM), validate and sanitise input, and give the database account least privilege.
REST uses HTTP verbs (GET/POST/PUT/DELETE) on resources identified by URLs, returning representations (usually JSON). A RESTful API is stateless, resource-oriented, and uses correct status codes.
SQL databases are relational with fixed schemas and strong consistency — great for structured, related data and transactions. NoSQL offers flexible schemas and horizontal scale — great for large, evolving or unstructured data. Choose by data shape and scale needs.
Hooks let function components use state and lifecycle features: useState for local state, useEffect for side effects, useContext for shared data, useMemo/useCallback for performance. They must be called at the top level, not conditionally.
Measure first (Lighthouse/DevTools). Then compress/lazy-load assets, code-split JS, cache (CDN + HTTP caching), reduce re-renders, add DB indexes for slow queries, and avoid blocking the main thread.
Cross-Origin Resource Sharing — a browser rule that blocks a page from calling a different origin unless that server returns the right Access-Control-Allow-Origin headers. You fix it on the server, not the browser.
Authentication verifies who you are (login). Authorization decides what you are allowed to do (roles/permissions). You authenticate first, then authorize each action.
Knowing the answers isn’t enough — say them out loud
Practise these Full Stack questions in a free AI mock interview: answer by voice, get instant feedback on your strengths and the gaps to fix.
Admissions open · free to apply
Attended a masterclass or have a friend's referral code? You get ₹15,000 off. Fill this and our team takes it from here — pay by cash or online.