Constant Contact India Frontend Engineer Interview: Rounds, Questions and Preparation

What the job involves

Frontend Engineers at global tech and fast-growing product companies build and maintain user interfaces for web applications used by customers worldwide. Day to day they write JavaScript or TypeScript, work with frameworks like React, consume APIs, fix UI bugs, improve accessibility, and collaborate with designers, backend engineers, and product managers. Freshers usually start with component-level tasks, code reviews, and gradually take ownership of small features.

Role and Technical Knowledge

1. 1

   What happens when you type a URL in the browser and press Enter, from a frontend perspective?

   Cover DNS lookup, TCP and TLS, HTTP request, server response, HTML parsing, CSS and JS loading, and render tree construction. Mention blocking resources and how the critical rendering path affects first paint.

2. 2

   Explain the difference between var, let, and const in JavaScript with examples.

   Talk about function scope vs block scope, hoisting behaviour, temporal dead zone, and reassignment rules. Give a small code example showing a bug that var causes inside a loop.

3. 3

   How does React decide when to re-render a component, and how can you prevent unnecessary re-renders?

   Explain state and prop changes triggering re-renders, the role of keys in lists, and tools like React.memo, useMemo, and useCallback. Mention that premature optimisation is not always needed.

4. 4

   What is the difference between Flexbox and CSS Grid, and when would you use each?

   Say Flexbox is one-dimensional for rows or columns, Grid is two-dimensional for layout areas. Give a practical example like a navbar with Flexbox and a dashboard layout with Grid.

Practical Scenarios and Problem Solving

1. 5

   A page you built loads slowly on a mid-range Android phone. How would you investigate and improve it?

   Mention Chrome DevTools performance and network tabs, Lighthouse, image compression, code splitting, lazy loading, and reducing main-thread JavaScript. Also consider testing on a real device or throttled network.

2. 6

   You need to build a search box that calls an API as the user types. How would you avoid firing too many requests?

   Describe debouncing or throttling, cancelling stale requests with AbortController, showing loading and empty states, and handling race conditions so old responses do not overwrite new ones.

3. 7

   A form on your page submits but the user sees no feedback. How would you debug and fix it?

   Check console errors, network tab for failed or pending requests, and whether the submit handler calls preventDefault. Then add loading, success, and error states, and validate inputs before sending.

4. 8

   How would you make a complex dashboard accessible to keyboard and screen reader users?

   Cover semantic HTML, focus management, ARIA roles only when needed, colour contrast, and testing with keyboard tab order and a screen reader. Mention that accessibility is part of the definition of done, not an afterthought.

Behavioural and Teamwork

1. 9

   Tell me about a project where you had to learn a new frontend tool or library quickly.

   Use a STAR structure: situation, task, action, result. Focus on how you learned, what you built, and one concrete outcome like a deployed link or a bug you fixed.

2. 10

   Describe a time you disagreed with a teammate about a technical approach.

   Show that you listened, compared trade-offs with evidence, and either convinced or accepted the decision gracefully. Avoid sounding rigid or dismissive.

3. 11

   You are given a bug in production code you did not write, and the deadline is tomorrow. What do you do?

   Talk about reproducing the bug, reading logs and recent commits, asking for help early, and communicating status. Mention writing a small test to prevent regression if time allows.

4. 12

   Why do you want to work as a frontend engineer at a product company rather than a services company?

   Connect your interest to building user-facing features, owning quality, and iterating with real user feedback. Show awareness of the company's product or domain without claiming inside knowledge of their interview process.

HR and Fresher-Specific Questions

1. 13

   Walk me through your resume and highlight the frontend work you are most proud of.

   Keep it to two minutes, focus on projects with live links or GitHub repos, and state your specific contribution. Avoid listing every technology you have ever touched.

2. 14

   Are you comfortable relocating to a different city or working in a hybrid model?

   Be honest and clear about your flexibility. If you have constraints, state them politely and show willingness to adapt where possible.

3. 15

   What are your salary expectations as a fresher?

   Research typical fresher ranges for the role and city, then give a broad range or say you are open to the company's standard band. Focus on learning and growth rather than a single number.

4. 16

   Where do you see yourself in two years as a frontend engineer?

   Show a realistic path such as deeper expertise in React and performance, mentoring interns, or owning a feature area. Avoid saying you want to move into management immediately.