Manager, Engineering - Frontend

This role is suitable for a Senior-level engineering manager with 4+ years of management experience and a strong frontend individual-contributor background. Required skills include deep expertise in StimulusJS, Hotwire, modern frontend tooling, shared component libraries or design systems, scalable data and reporting systems, Agile/Scrum, and cross-functional collaboration. The candidate should be familiar with leading frontend platform teams, designing shared UI infrastructure, improving performance and developer experience, conducting technical reviews, delivering roadmaps, and coaching and hiring engineers.

How would you design and govern a shared frontend component system for a large Rails application using StimulusJS and Hotwire?

I would establish clear component APIs, accessibility requirements, visual guidelines, ownership, and versioning practices. Components should be reusable without hiding important behavior, and adoption should be supported with documentation, examples, automated tests, and a contribution process.

What are the key considerations when building interactive features with StimulusJS and Hotwire?

I would keep behavior localized in small Stimulus controllers, use semantic HTML and progressive enhancement, and avoid unnecessary client-side state. Turbo Frames and Streams should handle partial updates efficiently while preserving predictable navigation, accessibility, and server-side rendering benefits.

How would you improve frontend performance in a Ruby on Rails and Hotwire application?

I would measure first using browser performance tooling, real-user metrics, and server profiling. Typical improvements include reducing JavaScript and CSS payloads, optimizing Turbo updates, eliminating N+1 queries, improving database indexes, caching expensive responses, and minimizing unnecessary DOM updates.

How would you design a scalable data grid or reporting framework?

I would define consistent contracts for columns, filtering, sorting, pagination, permissions, formatting, and empty or error states. Large datasets should use server-side querying and pagination, with careful attention to query performance, accessibility, export behavior, and consistent integration with PostgreSQL or Snowflake.

How would you decide whether reporting data should come from PostgreSQL or Snowflake?

PostgreSQL is generally appropriate for transactional, low-latency operational views, while Snowflake is better suited to analytical queries across large historical datasets. I would consider freshness requirements, query complexity, data volume, concurrency, cost, and whether pre-aggregated or transformed data is needed.

What practices would you use to maintain quality in a shared frontend platform?

I would combine unit and integration tests, accessibility checks, visual regression testing, linting, type or contract validation where applicable, and performance budgets. Clear release ownership, backward-compatibility expectations, documentation, and observability would help prevent platform changes from causing widespread regressions.

How would you organize technical design reviews for frontend platform initiatives?

I would begin with the problem, goals, constraints, alternatives, and measurable success criteria, then involve representatives from product, design, and affected engineering teams. Reviews should produce a documented decision, identify risks and migration steps, and remain lightweight enough to support timely delivery.

How can Redis support a Rails application that provides frontend reporting or dashboard experiences?

Redis can provide caching for frequently requested aggregates, short-lived query results, feature flags, and background-job coordination. Cache keys, expiration, invalidation, serialization, and failure behavior must be designed carefully so stale or unavailable cache data does not compromise correctness.

What would you consider when deploying frontend platform changes on Kubernetes?

I would ensure reliable health checks, resource requests and limits, safe rollout strategies, centralized logging, metrics, and straightforward rollback procedures. Changes should be validated through automated tests and staged environments, with monitoring for error rates, latency, asset delivery failures, and resource pressure.

How would you balance platform roadmap work with requests from product teams?

I would evaluate requests based on user impact, engineering leverage, reliability, performance, developer productivity, and strategic alignment. A transparent roadmap, documented trade-offs, and regular feedback from consuming teams help ensure platform work supports product delivery without becoming an unprioritized service queue.

Wrapbook is an AI-powered production finance platform trusted by leading film, television, and commercial teams. As Manager, Engineering – Frontend, you’ll lead the Frontend Platform team, guide shared component systems and reporting infrastructure, shape technical strategy, and mentor engineers. The stack includes Ruby on Rails, StimulusJS, Hotwire, Redis, PostgreSQL, Snowflake, and Kubernetes, with the role fully remote across the US and Canada. Compensation ranges from US$183K–$283.5K or CA$183K–$251.5K by location, plus benefits, equity or bonus eligibility, unlimited PTO, and professional growth opportunities—making it an excellent chance to drive meaningful impact in a fast-growing, well-funded company.