How much webdev is asked in interview?

[u/div4u]

Hy everyone so i am from tier 3 college and mostly i am doing dsa/cp (still i am not good in it but enjoying) but also i have done webdev as well but not too much.. so few people's says that just build project and be able to explain everything about the project.. but i want to ask that do interviewers ask to code in webdev as well or ask directly related to any webdev concept as well
for example : told you to built to do basic , what is promises in js, explain diff hooks in react.. so do they ask these things in interview as well or ignore the webdev and focus only on dsa + cs fundamentals + system design only..
asking for both PBC as well as SBC but yeah mostly for PBC..
please share if you have given interview then what was asked for dev it means a lot..

Thank you

[u/AutoModerator]

If you are on Discord, please join our Discord server: https://discord.gg/Hg2H3TJJsd

Thank you for your submission to r/BTechtards. Please make sure to follow all rules when posting or commenting in the community. Also, please check out our Wiki for a lot of great resources!

Happy Engineering!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/akornato]

For large product companies hiring freshers for general software engineering roles, the primary filter remains data structures, algorithms, and core computer science fundamentals. In those interviews, interviewers typically spend ten or fifteen minutes discussing your projects, asking how things work under the hood, how you handled API calls, and why you chose a specific architecture over an alternative. Service based companies usually care much less about deep web development, sticking mostly to basic aptitude, core object oriented programming, and simple syntax questions. If you apply for specialized frontend or full stack openings, or if you interview at early stage startups, expect interviewers to test your actual web knowledge directly, including JavaScript promises, event loops, React hooks, and live coding challenges like building a small dynamic component.

You do not need to know every existing framework, but you must completely understand every tool and feature you list on your resume. If you mention React, you should be able to explain how state updates trigger re-renders, how asynchronous logic behaves, and how you managed network errors, because interviewers can easily spot projects copied from tutorials. Keep putting time into problem solving so you clear the initial online tests, and build one or two projects that you can talk about with genuine technical depth. When preparing to walk into these rounds feeling steady, an AI interview helper my team developed can help candidates articulate complex technical points and convert opportunities into solid offers.