0% found this document useful (0 votes)
15 views2 pages

Technical Mock Interview QA Script

The document is a script for a technical interview mock call focusing on front-end development using React and Angular. It includes questions about project experience, differences between frameworks, state management, API integration, component types, mobile app development, responsiveness, Agile methodologies, and debugging techniques. Each question is followed by a concise answer that highlights key concepts and personal experiences.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views2 pages

Technical Mock Interview QA Script

The document is a script for a technical interview mock call focusing on front-end development using React and Angular. It includes questions about project experience, differences between frameworks, state management, API integration, component types, mobile app development, responsiveness, Agile methodologies, and debugging techniques. Each question is followed by a concise answer that highlights key concepts and personal experiences.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

🧪 Technical Interview Mock Call – Q&A

Script
1. Q1. Can you walk me through a project where you used React or Angular? What
challenges did you face?

A: Sure. At Zuruwaala Private Limited, I built a dashboard using React with Redux for state
management. I also worked on mobile apps using React Native. A key challenge was
managing state across deeply nested components, which I resolved using centralized Redux
store and custom hooks.

2. Q2. What are the differences between React and Angular? When would you use one over
the other?

A: React is a lightweight JavaScript library focused on UI, while Angular is a full-fledged


framework. I choose React for lightweight, component-driven apps and Angular for
enterprise-level apps that require built-in routing, form validation, and DI.

3. Q3. Explain the purpose of Redux or NgRx. How do you manage global state in your
applications?

A: Redux and NgRx are used to manage global state in a predictable way using actions,
reducers, and a centralized store. In React, I use Redux with middleware like thunk or saga.
In Angular, I use NgRx effects and selectors to work with observable streams.

4. Q4. How do you handle API integration in a React/Angular app? How do you handle
errors and loading states?

A: I use fetch/axios in React and HttpClient in Angular. I manage loading and error states
using local component state or Redux/NgRx, and show feedback to users like loaders or
error messages.

5. Q5. What is the difference between functional and class components in React?

A: Functional components are simpler and use hooks for state and lifecycle, while class
components use lifecycle methods and `this`. I prefer functional components due to their
cleaner syntax and better performance with hooks.

6. Q6. Have you worked on mobile apps with React Native? What was your experience
with navigation and styling?

A: Yes. I’ve built e-commerce features with React Native. I used `react-navigation` for stack
and tab navigation, and styled components using `[Link]`. I also used
`Dimensions` for responsive layout.
7. Q7. What are controlled vs uncontrolled components in React?

A: Controlled components use React state for input values; uncontrolled components rely
on refs and DOM. Controlled components are preferred for form validation and dynamic
control.

8. Q8. How do you make your front-end application responsive?

A: I use CSS3 with media queries, Flexbox/Grid layout, and mobile-first design. In React
Native, I use `Dimensions`, `%`, and responsive libraries like `react-native-responsive-
screen`.

9. Q9. Can you describe a time you worked in an Agile/Scrum environment?

A: Yes. I’ve worked in 2-week sprints, attended daily standups, sprint planning, and
retrospectives. I coordinated closely with product managers, QA, and backend teams to
deliver features on time.

10. Q10. What is your approach to debugging a front-end issue that only occurs in
production?

A: I use browser dev tools, check logs or use error tracking tools like Sentry. I also replicate
the issue in staging, check environment differences, and add console logs or network traces
to pinpoint the bug.

You might also like