Mid/Senior Frontend Engineer

We are looking for an experienced Frontend Engineer to build the interfaces our customers and internal teams use every day. Our work spans consumer-facing web platforms and dense, workflow-driven internal admin tools. Because our product priorities evolve, you can expect to move between different projects and interfaces over time rather than owning a single screen indefinitely. The common thread across all our work is a strict adherence to industry standards and best practices. We care deeply about clean code, maintainability, component architecture, and building user interfaces that are responsive, accessible, and performant long after launch. Your Initial Focus: Your first major project will be building the web interfaces for a complex consumer-facing travel and booking platform. You will build both the public-facing, performance-sensitive checkout flow (optimized for mobile web, dynamic search, and live price streams) and the high-density internal management panels used to handle complex multi-supplier orders, cancellations, and customer support workflows. Key Responsibilities • Software Design & UI Development: Design, write, and maintain high-quality, reusable, and scalable frontend code using TypeScript, Next.js, and React. • Standards & Best Practices: Strictly adhere to industry best practices, modern architectural patterns, and internal style guides to ensure long-term codebase maintainability, high performance, and accessibility (WCAG). • Code Review & Quality Assurance: Actively participate in the code review process, providing thoughtful, constructive feedback to peers to maintain high code quality and consistency across libraries. • Technical Strategy & Collaboration: Participate in technical discussions, system architecture planning, and API contract design alongside backend engineers. Proactively identify technical debt and drive continuous frontend improvements. • Asynchronous Data & State Management: Properly handle complex user-interface states—including optimistic updates, race conditions, caching strategies, stale data, graceful degradation, and robust error handling. • Cross-Functional Collaboration: Work closely with product management, designers, backend engineers, and QA to translate Figma designs into robust code, pushing back when designs may not withstand real-world API latencies or edge-case data. • Testing & Performance Maintenance: Write and maintain reliable UI and end-to-end tests. Monitor and optimize Core Web Vitals, bundle sizes, and rendering cost on mid-range devices. What We Are Looking For • Experience: 4+ years building production frontends with React, including solid, hands-on experience with Next.js (App Router, Server/Client components, data fetching strategies). • Strong TypeScript: Deep experience with strong typing—not standard JavaScript with light type annotations. • Engineering Excellence: Proven track record of writing maintainable code, building shared component libraries, and adhering to strict modern web standards. • Complex Async UI: Comfort handling the gap between dynamic server states and user actions (loading boundaries, fallback UI, complex form validation, stream rendering). • Responsive & Accessible: True mobile-first development habits, cross-browser compatibility skills, and semantic HTML standards. • Language: Professional working English. Nice to Have • Component Library Ownership: Experience building or maintaining shared design systems or component libraries across multiple applications. • Dual UI Experience: Experience building both consumer-facing UIs (high polish, conversion-focused) and internal admin tools (data-dense, fast-keyboard navigation). • Internationalization: Handling multi-currency interfaces and multi-language support (i18n). • Backend Familiarity: Enough understanding of REST/GraphQL APIs and server architecture to meaningfully contribute to contract design. What This Role Is Not This is not a role where you just turn static mocks into layout components. You will be expected to think critically about asynchronous state, network failures, edge cases in real data, and API design. If you prefer working in isolation on static designs without questioning the underlying data flow, this role will not be a good fit.