Front-End Engineering Manager

Job Description

Front-End Engineering Manager

\n

\n

Remote, United States | $170,000 to $190,000 base salary plus benefits

\n

\n

Role at a glance

\n

\n
• Reporting to: Chief Technology Officer
\n
• Team: Three senior front-end engineers
\n
• Working model: Hands-on player-coach across four-week sprints
\n
• Core stack: React, Redux, JavaScript ES6+, HTML/CSS and Node
\n

\n

\n

Element Six is retained by an established enterprise SaaS company whose building analytics platform helps operators improve equipment performance, energy efficiency and day-to-day building operations.

\n

\n

The platform takes large volumes of live data from equipment across complex property portfolios and turns it into prioritized actions for the people operating those buildings. Behind a relatively simple interface sits a demanding front-end problem: complex data, charts, tables, and workflows that must remain fast, clear, and useful at scale. The company is now hiring a Front-End Engineering Manager to lead the three senior engineers responsible for that experience.

\n

\n

Why this role is worth your attention

\n

\n
• This is not a role where you inherit a large organization and manage from a distance. You will join a small, experienced team where your decisions will directly affect what gets built, how quickly it ships, and how the product evolves.
\n
• They want a front-end leader who can own the technical direction while working closely with Product on operational problems rather than finished specifications. Someone who can explore ideas, prototype possible solutions, make informed architectural decisions, and help shape complex workflows before they enter the backlog.
\n
• The product is also moving beyond passive analytics towards greater control and intervention. That creates a new set of questions around usability, trust, and how users act confidently on what the platform tells them.
\n

\n

\n

What you will own

\n

\n
• Lead and mentor three engineers while continuing to contribute directly to the platform.
\n
• Own front-end architecture, code quality, performance, scalability, security and UX standards.
\n
• Review pull requests, resolve technical blockers, and make informed architectural decisions.
\n
• Partner with Product from the beginning of an idea, helping turn operational problems into prototypes, workflows and shipped functionality.
\n
• Improve how complex operational data is filtered, visualized, and presented without overwhelming the user.
\n
• Run the team’s day-to-day engineering practices, including planning, backlog refinement, code review and delivery across four-week sprints.
\n
• Introduce practical AI-assisted development workflows while maintaining appropriate technical oversight and code-review standards.
\n
• Work across front-end, back-end, and QA to improve testing, CI/CD, and release quality.
\n

\n

\n

What we are looking for

\n

You may already be an engineering manager who misses being close to the code, or a Principal or Lead Front-End Engineer ready to take formal ownership of a team. Either way, you will need:

\n

\n
• Deep, recent hands-on front-end engineering experience with React and modern JavaScript.
\n
• The technical credibility to review code, guide senior engineers, and own critical functionality.
\n
• Experience making front-end architecture decisions within a production enterprise SaaS environment.
\n
• Breadth beyond the component layer, including API integration, automated testing, CI/CD, security, performance and scalability.
\n
• Experience leading, mentoring, or technically directing engineers.
\n
• Evidence of working closely with Product and contributing to UI, UX and workflow decisions.
\n
• Experience building interfaces around large, real-time, operational or otherwise complex datasets.
\n
• Practical experience using AI coding tools, including an informed view of how generated code should be structured, tested and reviewed.
\n

\n

\n

Experience with Highcharts, Kendo React UI, Azure, time-series data, or building systems would be useful, but direct building-technology experience is not required.

\n

\n

This probably is not for you if

\n

\n
• You have moved away from hands-on engineering and do not want to return to regular code and pull-request review.
\n
• You prefer to receive completed requirements rather than help shape the solution.
\n
• You are primarily looking for a large team-management remit rather than a hands-on player-coach role.
\n
• Your experience is primarily visual implementation without wider ownership of architecture, testing, security and delivery.
\n
• You use AI tools personally but haven't considered how to introduce them responsibly across a team.
\n

\n

\n

If you are looking for a role where you can lead experienced engineers, stay technically hands-on, and genuinely influence both the product and how it is built, apply for a confidential conversation.