Design, build, and deliver customer-facing web/mobile experiences that are performant, reliable, and intuitive
Lead the implementation and evolution of frontend systems, including component design, state management, and UI architecture
Write clean, well-structured code and actively participate in code reviews and technical design discussions
Own code quality end-to-end, including testing, edge-case handling, and production readiness
Collaborate closely with Product, Design, and UX partners to translate customer needs into elegant technical solutions
Make thoughtful trade-offs between speed, quality, and long-term maintainability—and clearly communicate those decisions
Continuously simplify and improve systems, demonstrating strong judgment, creativity, and attention to detail
Mentor other engineers through example, feedback, and technical discussion, contributing to a strong engineering culture
Requirements
Bachelor’s degree in Computer Science or equivalent practical experience
4+ years of professional software engineering experience, with a strong emphasis on frontend or customer-facing web development
Strong proficiency in modern frontend languages, ideally TypeScript/JavaScript, with solid fundamentals in data structures, algorithms, and problem decomposition
Experience building and maintaining production UI systems, including performance optimization, accessibility, and cross-browser compatibility
2+ years contributing to frontend architecture and design, including patterns for maintainability, reliability, and scalability
2+ years working across the full software development lifecycle, including coding standards, code reviews, source control, build tooling, testing, and operational support
Familiarity working in cloud-backed environments (e.g., integrating with APIs, CI/CD pipelines, AWS and/or Azure), with an understanding of how frontend systems behave in production
Strong communication skills: you ask clarifying questions, state assumptions, identify constraints, and explain your thinking clearly—especially when requirements are ambiguous.