Front End Engineer Position At Millipixels Interactive

• delivery hero
• remote
• react
• next.js
• redux
• node.js

Role: Senior Frontend Engineer at Delivery Hero. Responsibilities include architecture and development of consumer-facing features, state management, performance optimization, API integration, full-stack collaboration, and ensuring code quality. Requirements encompass 3–5 years of front-end experience, proficiency in React, Next.js, Redux, JavaScript, HTML5, CSS3, Node.js, MySQL, and experience with REST APIs, testing frameworks, and modern development practices. The role involves building scalable, user-focused applications with a product mindset, mentorship, and problem-solving skills, with exposure to mobile payments and e-commerce systems as plus. The position is based in a hybrid work environment.

• the product highway
• remote
• react
• typescript
• full-time
• frontend

Frontend Engineer - The Product Highway Responsibilities: Own frontend architecture end-to-end — rendering strategy, state management, component design, performance budgets. You set the architecture, not inherit it. Define and evolve frontend standards at TPH — component patterns, TypeScript conventions, testing strategy, AI workflow practices. What you establish becomes the team's baseline. Mentor SDE-1 and SDE-2 engineers through code reviews, pair programming, and architectural walkthroughs. You make the people around you meaningfully better. Lead client-facing technical conversations — discovery sessions, translating UI requirements into architecture plans, representing TPH's engineering standards to stakeholders. Build and own complex interfaces — data-heavy dashboards, real-time UIs, AI-native UX patterns, multi-step flows. You take on the problems others aren't sure how to approach. Translate design into production UI with precision — and push back when something won't survive production contact. You propose better alternatives, not just flag problems. Step across the stack when needed — write API endpoints, fix backend issues. You don't let a backend change block a frontend delivery when you can solve it yourself. Write code the team can build on — clean component APIs, proper TypeScript, meaningful tests, documented decisions. Must-haves 5+ years building production frontend applications — complex interactive products with real users, not landing pages or internal tools. Deep expertise in React and Next.js — server components, app router, SSR/SSG/ISR, middleware. You understand the rendering model well enough to make and defend architectural decisions. Strong TypeScript — generics, discriminated unions, type inference. This is how you design component APIs and catch bugs before they ship. Has owned frontend architecture independently — state management strategy, rendering approach, data fetching. You've made these calls on production systems and lived with the consequences. Has built or significantly evolved a design system or component library — not just consumed one, but established the primitives and patterns others depended on. Has mentored engineers demonstrably — code reviews, architecture feedback, direct coaching. You've made other engineers better, not just been good yourself. Performance engineering depth — bundle analysis, re-render profiling, Core Web Vitals. You've diagnosed and fixed real performance problems in production. Comfortable across the stack — trace a bug to a backend endpoint, write a fix, unblock the team. Full-stack willingness is non-negotiable. Strong pluses Has led frontend teams or acted as technical lead in a consulting or services environment. Has integrated AI features at depth — streaming LLM responses, chat interfaces, generative UI, AI-powered search. Experience with animation and motion — Framer Motion, GSAP. You implement interactions that feel polished, not bolted on. Experience with both React and React Native or Flutter — working across web and mobile makes you far more deployable. AI-native expectations At SDE-3, you're not just using AI tools — you're defining how TPH's frontend engineers use them. Uses Cursor or Claude Code as primary development environment daily — components, refactoring, production features. Sets AI workflow standards for the team — CLAUDE.md templates, .cursorrules patterns. What you systematize, others inherit. Uses AI for rapid prototyping (v0, Claude, Cursor) and for code review, test generation, and documentation — but never ships AI output without reading it. Coaches SDE-1 and SDE-2 engineers on AI-assisted development — prompting habits, review quality, holding the bar on AI-generated code. Not the right fit if You think senior engineering is about writing better code, not raising the team's ceiling. You've never mentored or led technically — we need someone who's made other engineers better, not just someone who's very good individually. You refuse to touch backend code, or need fully specced designs for everything. You don't use AI tools daily in your current work. How to apply Send your resume and a short note on why this role excites you to anju@theproducthighway.com. No templates — just tell us what you'd bring to TPH, what technical problems you've led, and why building across multiple products at the frontier of AI-native development sounds like the right kind of challenge. … more Requirements: Role: Senior Frontend Engineer (SDE-3) WFO Bangalore | 5+ years | AI-native IT Services About TPH The Product Highway is an AI-native product strategy and engineering firm. We partner with businesses from the earliest spark of an idea through to enterprise scale — growing from zero to multi-million ARR in our first year, working with clients across India, APAC, Europe, and North America. AI got very good at the how — shipping code faster than ever. But almost nothing has changed in the what: deciding what to build, why, and in what order. That's where we live. From in-house AI project managers to near-universal adoption of Cursor and Claude, we've rethought every conventional process from first principles. The result: legacy systems rebuilt in under 6 months, enterprise platforms in under 3, mobile apps shipped in under 1. We only take on problems we find genuinely interesting, and we refuse to ship anything we wouldn't stand behind. Every hire gets us closer to that standard. Who we're looking for Regardless of role, every person at TPH shares these traits: End-to-end owners. You own outcomes, not tasks. If something falls through a crack, that's on you — not because someone assigned it, but because you wouldn't have it any other way. Uncompromising on quality. You have a quality bar that's yours, not your manager's. You won't ship something you wouldn't stand behind, even under deadline pressure. AI-obsessed. You see AI as how work gets done, not a nice-to-have. If you're still doing something manually that AI could handle, you feel that as friction, not normalcy. Structured thinkers. When faced with an ambiguous problem, you break it down, reason through the trade-offs, and arrive at a position — not wait for someone to tell you the answer. Experienced enough to use AI systematically. You have enough depth in your craft that AI makes you dangerous, not dependent. You direct it, evaluate its output, and know when it's wrong. Why we're hiring TPH builds products for clients across fintech, ecommerce, SaaS, enterprise data, and consumer apps. Every one of these lives or dies on the frontend. At SDE-3, we're not looking for someone who can build excellent frontends — we're looking for someone who raises the entire team's ceiling. You define frontend architecture patterns that SDE-1 and SDE-2 engineers build within. You make the hard calls on technology choices, component system design, and performance strategy. You're the technical anchor clients trust with their hardest UI challenges — and the person who defines how TPH's frontend engineers use AI tools. Full job description: Role: Senior Frontend Engineer (SDE-3) WFO Bangalore | 5+ years | AI-native IT Services About TPH The Product Highway is an AI-native product strategy and engineering firm. We partner with businesses from the earliest spark of an idea through to enterprise scale — growing from zero to multi-million ARR in our first year, working with clients across India, APAC, Europe, and North America. AI got very good at the how — shipping code faster than ever. But almost nothing has changed in the what: deciding what to build, why, and in what order. That's where we live. From in-house AI project managers to near-universal adoption of Cursor and Claude, we've rethought every conventional process from first principles. The result: legacy systems rebuilt in under 6 months, enterprise platforms in under 3, mobile apps shipped in under 1. We only take on problems we find genuinely interesting, and we refuse to ship anything we wouldn't stand behind. Every hire gets us closer to that standard. Who we're looking for Regardless of role, every person at TPH shares these traits: End-to-end owners. You own outcomes, not tasks. If something falls through a crack, that's on you — not because someone assigned it, but because you wouldn't have it any other way. Uncompromising on quality. You have a quality bar that's yours, not your manager's. You won't ship something you wouldn't stand behind, even under deadline pressure. AI-obsessed. You see AI as how work gets done, not a nice-to-have. If you're still doing something manually that AI could handle, you feel that as friction, not normalcy. Structured thinkers. When faced with an ambiguous problem, you break it down, reason through the trade-offs, and arrive at a position — not wait for someone to tell you the answer. Experienced enough to use AI systematically. You have enough depth in your craft that AI makes you dangerous, not dependent. You direct it, evaluate its output, and know when it's wrong. Why we're hiring TPH builds products for clients across fintech, ecommerce, SaaS, enterprise data, and consumer apps. Every one of these lives or dies on the frontend. At SDE-3, we're not looking for someone who can build excellent frontends — we're looking for someone who raises the entire team's ceiling. You define frontend architecture patterns that SDE-1 and SDE-2 engineers build within. You make the hard calls on technology choices, component system design, and performance strategy. You're the technical anchor clients trust with their hardest UI challenges — and the person who defines how TPH's frontend engineers use AI tools. What you'll do Own frontend architecture end-to-end — rendering strategy, state management, component design, performance budgets. You set the architecture, not inherit it. Define and evolve frontend standards at TPH — component patterns, TypeScript conventions, testing strategy, AI workflow practices. What you establish becomes the team's baseline. Mentor SDE-1 and SDE-2 engineers through code reviews, pair programming, and architectural walkthroughs. You make the people around you meaningfully better. Lead client-facing technical conversations — discovery sessions, translating UI requirements into architecture plans, representing TPH's engineering standards to stakeholders. Build and own complex interfaces — data-heavy dashboards, real-time UIs, AI-native UX patterns, multi-step flows. You take on the problems others aren't sure how to approach. Translate design into production UI with precision — and push back when something won't survive production contact. You propose better alternatives, not just flag problems. Step across the stack when needed — write API endpoints, fix backend issues. You don't let a backend change block a frontend delivery when you can solve it yourself. Write code the team can build on — clean component APIs, proper TypeScript, meaningful tests, documented decisions. Must-haves 5+ years building production frontend applications — complex interactive products with real users, not landing pages or internal tools. Deep expertise in React and Next.js — server components, app router, SSR/SSG/ISR, middleware. You understand the rendering model well enough to make and defend architectural decisions. Strong TypeScript — generics, discriminated unions, type inference. This is how you design component APIs and catch bugs before they ship. Has owned frontend architecture independently — state management strategy, rendering approach, data fetching. You've made these calls on production systems and lived with the consequences. Has built or significantly evolved a design system or component library — not just consumed one, but established the primitives and patterns others depended on. Has mentored engineers demonstrably — code reviews, architecture feedback, direct coaching. You've made other engineers better, not just been good yourself. Performance engineering depth — bundle analysis, re-render profiling, Core Web Vitals. You've diagnosed and fixed real performance problems in production. Comfortable across the stack — trace a bug to a backend endpoint, write a fix, unblock the team. Full-stack willingness is non-negotiable. Strong pluses Has led frontend teams or acted as technical lead in a consulting or services environment. Has integrated AI features at depth — streaming LLM responses, chat interfaces, generative UI, AI-powered search. Experience with animation and motion — Framer Motion, GSAP. You implement interactions that feel polished, not bolted on. Experience with both React and React Native or Flutter — working across web and mobile makes you far more deployable. AI-native expectations At SDE-3, you're not just using AI tools — you're defining how TPH's frontend engineers use them. Uses Cursor or Claude Code as primary development environment daily — components, refactoring, production features. Sets AI workflow standards for the team — CLAUDE.md templates, .cursorrules patterns. What you systematize, others inherit. Uses AI for rapid prototyping (v0, Claude, Cursor) and for code review, test generation, and documentation — but never ships AI output without reading it. Coaches SDE-1 and SDE-2 engineers on AI-assisted development — prompting habits, review quality, holding the bar on AI-generated code. Not the right fit if You think senior engineering is about writing better code, not raising the team's ceiling. You've never mentored or led technically — we need someone who's made other engineers better, not just someone who's very good individually. You refuse to touch backend code, or need fully specced designs for everything. You don't use AI tools daily in your current work. How to apply Send your resume and a short note on why this role excites you to anju@theproducthighway.com. No templates — just tell us what you'd bring to TPH, what technical problems you've led, and why building across multiple products at the frontier of AI-native development sounds like the right kind of challenge. … more