Haldiram's Frontend Engineer Interview: Rounds, Questions and Preparation

What the job involves

A Frontend Engineer in e-commerce, retail and D2C builds and maintains the customer-facing web storefront - product listing pages, search and filters, cart and checkout, offers and coupon flows - and the internal dashboards that catalogue, pricing and ops teams use. The work is heavily performance and conversion focused, because page speed, mobile usability and checkout reliability directly affect orders. Freshers typically own smaller components and bug fixes first, then take on full page or feature ownership.

Role and sector knowledge

1. 1

   What is different about building a frontend for an e-commerce or D2C store compared to a content website?

   Cover conversion impact, high traffic spikes during sales, mobile-first users, dynamic pricing and inventory, and the need for fast, reliable checkout.

2. 2

   How would you make a product listing page load fast on a mid-range Android phone on a slow 4G connection?

   Mention optimised and responsive images, lazy loading below the fold, code splitting, reducing third-party scripts, and measuring with Core Web Vitals.

3. 3

   Why does accessibility matter for a large retail brand's website?

   Talk about a wider customer base, legal and brand reputation risk, keyboard and screen-reader support, and how semantic HTML and contrast also help SEO.

4. 4

   What frontend metrics would you track after launching a new checkout page?

   Suggest conversion rate, cart abandonment, page load time, error rates, and interaction metrics like time to first meaningful paint on the checkout flow.

Technical fundamentals

1. 5

   Explain how you would build a product card component that shows an image, name, price, discount badge and an add-to-cart button.

   Describe component structure, props, reusable styling, handling missing images, and emitting an event or calling a callback on add-to-cart.

2. 6

   How does state management work in a cart that has multiple pages, and where would you keep the cart state?

   Discuss lifting state up or using a store like Redux or Context, persistence to localStorage, and keeping the cart in sync with the backend.

3. 7

   What happens between typing a product name in the search box and seeing results appear?

   Cover debouncing input, an API call, loading and error states, rendering results, and handling race conditions if responses arrive out of order.

4. 8

   How would you handle a form like address entry at checkout with validation?

   Mention controlled inputs, client-side validation with clear error messages, pincode and phone number patterns for India, and not blocking the user unnecessarily.

Practical scenarios

1. 9

   A discount coupon is applying the wrong amount on the cart page. How do you debug and fix it?

   Show a structured approach: reproduce, inspect network responses and state, check rounding and tax order, add a test, then fix and verify across cart and checkout.

2. 10

   During a big festive sale the site slows down badly. What frontend steps would you take?

   Talk about finding the bottleneck with DevTools and real user monitoring, deferring non-critical scripts, caching, CDN use, and graceful loading states.

3. 11

   You need to add a product filter for size, colour and price on a listing page that already has 500 items. How do you approach it?

   Discuss whether filtering happens client side or via API, URL-synced filter state so links are shareable, and keeping the UI responsive while results update.

4. 12

   A designer hands you a mobile mockup for a new offers page and you have two days. How do you plan the work?

   Show prioritisation, breaking the page into components, reusing existing UI pieces, clarifying unclear states, and testing on real devices before shipping.

Behavioural and HR

1. 13

   Tell me about a project where you had to learn a new frontend tool quickly to finish it.

   Use a clear situation-action-result structure, name the tool, and show how you learned it and what you delivered.

2. 14

   Describe a time you disagreed with a teammate about how to build a UI. What did you do?

   Focus on listening, weighing trade-offs with evidence, and committing to the chosen approach without ego.

3. 15

   Why do you want to work on frontend for a retail or D2C brand rather than a general software company?

   Connect personal interest in customer experience, visible impact on sales, and the fast pace of e-commerce to your own goals.

4. 16

   How do you keep your frontend skills current, and what have you built outside coursework?

   Mention specific resources, side projects, GitHub work, or contributions, and be ready to explain one project in technical detail.