https:\/\/www.horizonassetinvestments.com\/<\/a>\n<\/p>\nFront-End Developer (Full-Time, Remote)<\/span><\/strong><\/p>\n <\/span><\/p>\nWe are seeking a Front-End Developer to design and build the user-facing components of our high-performance trading platform. You will play a key role in creating intuitive, data-rich interfaces that enable traders and analysts to work efficiently and effectively.<\/span><\/p>\n <\/span><\/p>\nYou will collaborate closely with the Back-End Development Team and the Project Manager to deliver seamless, integrated systems. A key factor is the front end developer\u2019s ability to deeply discuss approaches, trade-offs, limitations, and pros\/cons with the development team, rather than reliance on any specific pattern or library.<\/span><\/p>\n<\/span><\/p>\n <\/span><\/strong><\/p>\n\u0627\u0644\u0645\u0647\u0627\u0645 \u0627\u0644\u0623\u0633\u0627\u0633\u064a\u0629<\/span><\/strong><\/p>\n\n- Develop and maintain the front-end applications of our trading platform.<\/span><\/li>\n
- Collaborate with back-end developers and the project manager to ensure smooth integration across systems.<\/span><\/li>\n
- Design and implement multi-page layouts, menus, and workflows that balance usability with efficiency.<\/span><\/li>\n
- Contribute to the design and user experience of the trading platform, performance & risk manager, and backtesting engine.<\/span><\/li>\n
- Implement and optimize charting and data visualization features, leveraging libraries such as TradingView or D3.js to support a wide variety of chart types (tables, multi-line chart packs, etc.).<\/span><\/li>\n
- Continuously refine the UI\/UX to ensure clarity, speed, and intuitive navigation for end users.<\/span><\/li>\n<\/ul>\n
<\/span><\/p>\n <\/span><\/strong><\/p>\nQualifications<\/span><\/strong><\/p>\n\n- Strong communication skills and the ability to collaborate effectively with developers, project managers, and business stakeholders.<\/span><\/li>\n
- A keen eye for design, simplicity, and efficiency, with the ability to translate complex requirements into clean, user-friendly interfaces.<\/span><\/li>\n
- Knowledge of financial systems or trading concepts is preferred.<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nCore stack (mandatory)<\/span><\/strong><\/p>\n\n- React 18 + Next.js (App Router), TypeScript, TailwindCSS.<\/span><\/li>\n
- Strong command of state management for high-frequency data (e.g., Zustand, Redux Toolkit, useSyncExternalStore).<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nReal-time data & performance<\/span><\/strong><\/p>\n\n- Hands-on with WebSockets \/ SSE and reconnection\/backoff strategies; handling authenticated socket connections and topic resubscriptions.<\/span><\/li>\n
- Experience implementing backpressure, buffering, coalescing, and windowing to prevent UI thrash under thousands of updates\/minute.<\/span><\/li>\n
- Data virtualization (react-virtualized, react-window) for large tables (orders, positions, trades).<\/span><\/li>\n
- Familiar with Web Workers \/ OffscreenCanvas and message passing to keep the main thread responsive.<\/span><\/li>\n
- Awareness of latency budgets and frame-time profiling using React DevTools and browser performance tools.<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nCharting & visualization<\/span><\/strong><\/p>\n\n- Practical experience with professional charting libs (e.g., TradingView Charting Library, Lightweight Charts, Highcharts, D3).<\/span><\/li>\n
- Real-time overlays: best bid\/ask, order book depth, last OHLCV, order\/position annotations.<\/span><\/li>\n
- Multi-pane layouts (price, volume, indicators) with synchronized crosshairs and time scales.<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nArchitecture & data access<\/span><\/strong><\/p>\n\n- Client-side caching and invalidation (e.g., TanStack Query \/ React Query).<\/span><\/li>\n
- Schema-driven UI for instruments and venues.<\/span><\/li>\n
- Use of Error Boundaries, Suspense, and progressive hydration\/streaming for large Next.js pages.<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nAuth, security, and roles<\/span><\/strong><\/p>\n\n- Strong understanding of OIDC\/JWT flows, token refresh\/rotation, and WebSocket authentication.<\/span><\/li>\n
- Role-based feature gating (read-only vs trading permissions).<\/span><\/li>\n<\/ul>\n
Testing, quality, and reliability<\/span><\/strong><\/p>\n\n- Unit tests for critical transforms\/parsers (e.g., Playwright\/Vitest for E2E\/interaction flows)<\/span><\/li>\n
- Experience with feature flags, staged rollouts, and monitoring with Sentry\/OpenTelemetry.<\/span><\/li>\n<\/ul>\n
<\/span><\/strong><\/p>\nNice-to-haves<\/span><\/strong><\/p>\n\n- Experience with desktop-class layouts (drag-to-dock panels, resizable grids).<\/span><\/li>\n
- Exposure to WASM for heavy computations (e.g., indicator calculations).<\/span><\/li>\n
- Familiarity with FIX\/crypto venue nuances (tick sizes, lot sizes, trading sessions).<\/span><\/li>\n<\/ul>\n
<\/span><\/p>\nScreening Questions
Keep answers **4\u20138 sentences** each. Bullet points allowed if clear.<\/span><\/p>\n <\/span><\/p>\n1) **UI migration (hrzk \u2192 Next.js):** <\/span><\/span><\/p>\nPick ONE area from the provided `hrzk.html` (e.g., Orders+Trades, Positions table, Equity\/Drawdown). <\/span><\/span><\/p>\nExplain how you\u2019d migrate it to **React 18 + Next.js (App Router) + TypeScript + Tailwind**. <\/span><\/span><\/p>\nInclude folder structure and what you\u2019d make **client vs server components**. <\/span><\/span><\/p>\n(We care about your trade-offs, not \u201cthe one true way\u201d.)<\/span><\/p>\n <\/span><\/p>\n2) **Real-time data ingestion:** <\/span><\/span><\/p>\nDescribe how you\u2019d handle **WebSockets\/SSE** for high-frequency updates: <\/span><\/span><\/p>\nreconnect\/backoff, authenticated sockets, and topic resubscriptions. <\/span><\/span><\/p>\nWhat failures do you expect in production?<\/span><\/p>\n <\/span><\/p>\n3) **Backpressure + UI thrash prevention:** <\/span><\/span><\/p>\nAssume **thousands of updates\/minute** for orders\/positions\/trades. <\/span><\/span><\/p>\nExplain how you\u2019d implement buffering\/coalescing\/windowing so the UI stays responsive. <\/span><\/span><\/p>\nMention how you\u2019d combine this with **state management** (e.g., Zustand\/RTK\/useSyncExternalStore) and **virtualization** (react-window \/ react-virtualized). <\/span><\/span><\/p>\nWhat would you measure to prove it works?<\/span><\/p>\n <\/span><\/p>\n4) **Charting approach:** <\/span><\/span><\/p>\nWe need fast, readable, data-rich charts (equity\/drawdown, doughnut\/bars, etc.). <\/span><\/span><\/p>\nPick a chart type from `hrzk.html` and explain: <\/span><\/span><\/p>\n– which charting library you\u2019d choose (TradingView Lightweight Charts \/ Highcharts \/ D3 \/ etc.) <\/span><\/span><\/p>\n– update frequency strategy <\/span><\/span><\/p>\n– performance risks + mitigations<\/span><\/p>\n <\/span><\/p>\n5) **Auth + role gating:** <\/span><\/span><\/p>\nExplain how you\u2019d handle JWT\/OIDC token refresh and **WebSocket authentication**, then implement role-based gating (read-only vs trading). <\/span><\/span><\/p>\nUse an example like \u201cCancel All Orders\u201d or \u201cStop\/Start Execution\u201d: when do you hide vs disable vs show a warning?<\/span><\/p>\n <\/span><\/p>\n6) **Remote ownership + teamwork:** <\/span><\/span><\/p>\nGive one example where you took ownership remotely on an ambiguous task. <\/span><\/span><\/p>\nThen describe how you\u2019d work with a small dev team: how you ask clarifying questions, communicate risk early, and avoid shipping \u201clocal optimum\u201d code that breaks other parts of the system.<\/span><\/p>\n <\/span><\/p>\nWhat to expect (our interview process):<\/span><\/p>\n <\/span><\/strong><\/p>\nOur hiring process is mostly async and focused on real work.
You\u2019ll start with a CV submission and a short, structured application.
Shortlisted candidates complete an async technical screen.
Finalists complete a paid, time\u2011boxed work sample aligned to the role.
End\u2011to\u2011end, the process typically runs 4\u20136 weeks.<\/span><\/p>\n <\/span><\/p>\n\u0627\u0644\u0623\u0633\u0626\u0644\u0629 \u0627\u0644\u0634\u0627\u0626\u0639\u0629<\/span><\/p>\n\u00b7 <\/span><\/span><\/span>Do I need to respond to the questions?<\/span><\/p>\nYes, please respond to the questions ideally in an open format via a cover letter. This is mandatory for vetting.<\/span><\/p>\n\u00b7 <\/span><\/span><\/span>Do I need to attend live interviews?
Most stages are async to reduce scheduling friction. Live calls are minimal.<\/span><\/p>\n\u00b7 <\/span><\/span><\/span>
![](\"https:\/\/we-work-remotely.imgix.net\/logos\/0171\/4987\/logo.gif?ixlib=rails-4.0.0&w=50&h=50&dpr=2&fit=fill&auto=compress\"){kind=logo}
<\/p>\n