Farseer - Senior Frontend Engineer
Requirements
• You don't need to know our stack by heart. You need to think like a senior engineer — which means clear judgment, real ownership, and the ability to make sound calls when the right answer isn't obvious. • You are a good fit if you: • Have shipped production frontend at real complexity — data-dense interfaces, heavy state, heavy interactivity. Framework doesn't matter as much as judgment • Can build interfaces that hold up under real data volume — large grids, deep hierarchies, fast recalculation • Think in components, design systems, and patterns that scale across a product • Have opinions about state management, rendering performance, and where complexity should live, and can defend them • Are comfortable working in an interconnected product where shipping a new screen often means simplifying three older ones • Use AI tools to move faster — code generation, debugging, prototyping • Experience with spreadsheet-like interfaces, modeling tools, BI tools, or anything where users build structured logic in a UI • Background in financial, analytical, or planning products • Strong design sensibility — you should be able to tell when something is off and push back on it
Responsibilities
• Core Product builds the product itself — everything users see, touch, and rely on every day. • That includes sheets, variables, dimensions, scenarios, modeling logic, planning workflows, collaboration, dashboards, and the backend systems that make all of it feel fast, reliable, and coherent. • The technical surface area is broad, and the constraints are real: models with millions of cells, real-time recalculation across deep dependency graphs, multi-user editing on the same surface, enterprise-grade permissions and audit logs — all fast enough that finance teams choose to work in Farseer instead of going back to Excel. • As a Senior Frontend Engineer on Core Product, you own those surfaces. You'd be joining a small team of senior engineers across backend and frontend. • As a Senior Frontend Engineer on Core Product, you own those surfaces. • You'll: • You'll: • Build the modeling UI — sheets, formulas, dimensions, scenarios • Build planning workflow UI — assignments, approvals, locks, scheduled processes • Build collaboration UI — audit log, comments, permissions, multi-user editing • Build visualizations, reporting, and dashboards • Make core user actions feel instant. Performance of the UI is part of the product • Work with the design system across these surfaces, and shape it where it doesn't yet exist • And one more thing — Core Product Engineers who develop broad product judgment here tend to go on to lead new specialized teams as the company grows.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT