Global Desi Frontend Engineer Interview: Rounds, Questions and Preparation

What the job involves

A Frontend Engineer at an e-commerce, retail, or D2C company like Global Desi builds and maintains the customer-facing website and web app that shoppers use to browse collections, check product availability, add items to cart, and complete checkout. Day to day you work with designers, backend engineers, and catalog or marketing teams to ship responsive pages, integrate product and pricing APIs, improve page speed, and fix UI bugs that affect conversion. In fast-growing retail teams you may also own A/B test variants, festive sale banners, and store-locator or size-guide features.

Role and e-commerce frontend knowledge

1. 1

   How would you build a product listing page for a fashion brand where filters like size, colour, and price update without a full page reload?

   A strong answer covers fetching or filtering data via API, updating the URL query params, re-rendering only the product grid, and showing loading or empty states. Mention keeping filter state in the URL so shoppers can share or refresh the page.

2. 2

   What frontend factors affect conversion on a product detail page, and how would you improve them?

   Talk about fast image loading, clear price and discount display, size and stock visibility, prominent add-to-cart, and mobile layout. Suggest lazy loading images, compressing assets, and reducing layout shift.

3. 3

   How would you handle a festive sale banner or homepage campaign that changes every few days?

   Explain building reusable banner components or using a CMS-driven config so marketing can swap content without code changes. Mention cache busting, image optimisation, and testing on low-end mobile devices.

4. 4

   What is the difference between server-side rendering and client-side rendering for an e-commerce storefront?

   Cover SEO benefits of SSR for product pages, faster first paint, and trade-offs in server cost and complexity. Mention that cart and account pages may still be client-rendered.

Core frontend technical questions

1. 5

   Explain how the event loop works in JavaScript and why it matters when you fetch product data.

   Describe call stack, task queue, and microtasks, and how async or await fits in. Link it to keeping the UI responsive while product or cart APIs load.

2. 6

   How do you manage state in a React app with a shopping cart and user login?

   Discuss local component state for UI, context or a store for cart and auth, and syncing cart with the backend. Mention avoiding prop drilling and persisting cart in local storage or cookies.

3. 7

   What is the difference between localStorage, sessionStorage, and cookies, and where would you store a cart or auth token?

   Explain size limits, expiry, and server access. A strong answer says cart can go in localStorage, while sensitive auth tokens should ideally be in httpOnly cookies, and notes XSS risks.

4. 8

   How would you make a product card accessible to screen reader users?

   Cover semantic HTML, alt text for product images, button labels like Add to cart, keyboard focus order, and sufficient colour contrast. Mention testing with keyboard only.

Practical scenarios and debugging

1. 9

   A shopper reports that the add-to-cart button does nothing on mobile but works on desktop. How do you debug it?

   Walk through reproducing on a real device or emulator, checking console errors, inspecting touch versus click events, and testing CSS overlay or z-index issues. Mention checking network calls and recent deploys.

2. 10

   The homepage takes 6 seconds to load on 4G. What steps would you take to bring it under 3 seconds?

   Suggest measuring with Lighthouse, compressing and lazy loading images, code splitting, removing unused libraries, and caching. Prioritise by impact and mention Core Web Vitals like LCP and CLS.

3. 11

   You need to show real-time stock availability on a product page. How would you design the frontend behaviour?

   Explain polling or websockets, showing last updated time, disabling add-to-cart when out of stock, and graceful fallback if the stock API fails. Mention not blocking the whole page on this call.

4. 12

   A designer hands you a Figma file for a new checkout flow. What do you check before writing code?

   Cover responsive breakpoints, error and empty states, form validation rules, accessibility, and how it connects to existing APIs. Mention clarifying edge cases like coupon codes and address autofill.

Behavioural and HR questions

1. 13

   Tell me about a time you built something for a college project or internship and had to fix a bug under time pressure.

   Use the STAR method, focus on your specific action, and mention what you learned about testing or communication. Keep it honest and relevant to frontend work.

2. 14

   Why do you want to work as a frontend engineer in e-commerce or D2C retail?

   Connect personal interest in shopping experiences, fast-paced product cycles, and visible impact on conversion. Show you understand that retail frontend work is both creative and metric-driven.

3. 15

   How do you keep learning new frontend tools, and what have you learned in the last six months?

   Name specific resources like documentation, YouTube, or open-source projects, and describe a small project or feature you built. Avoid vague answers like I watch tutorials.

4. 16

   Describe a time you disagreed with a teammate or received critical feedback on your code.

   Show you listen, ask questions, and separate ego from the work. End with how you improved the code or relationship and what you would do differently.