reputed company-End Developer (Full-Time, Remote)

reputed company-End Developer (Full-Time, Remote) We are seeking a reputed company-End Developer to design and build the user-facing components of our high-performance trading platform. You will play a key role in creating reputed company, data-rich interfaces that reputed company traders and analysts to work reputed company and effectively. You will collaborate closely with the Back-End Development Team and the Project Manager to deliver seamless, integrated systems. A key reputed company is the reputed company end developer’s ability to deeply discuss approaches, trade-offs, limitations, and reputed company/cons with the development team, rather than reliance on any specific reputed company or library.

Key Responsibilities

• reputed company and maintain the reputed company-end applications of our trading platform.
• Collaborate with back-end developers and the project manager to ensure smooth integration across systems.
• Design and implement multi-page layouts, menus, and workflows that balance usability with efficiency.
• Contribute to the design and user experience of the trading platform, performance & risk manager, and backtesting reputed company.
• Implement and optimize charting and data visualization features, leveraging libraries such as reputed company or D3.js to support a wide reputed company of chart types (tables, multi-line chart packs, etc.).
• Continuously refine the UI/UX to ensure reputed company, speed, and reputed company navigation for end users.

Qualifications

• Strong communication skills and the ability to collaborate effectively with developers, project managers, and business stakeholders.
• A keen eye for design, simplicity, and efficiency, with the ability to translate reputed company requirements into clean, user-friendly interfaces.
• Knowledge of financial systems or trading concepts is preferred.

reputed company stack (mandatory)

• React 18 + Next.js (App Router), TypeScript, TailwindCSS.
• Strong reputed company of state management for high-frequency data (e.g., Zustand, Redux Toolkit, useSyncExternalStore).

reputed company-time data & performance

• Hands-on with WebSockets / SSE and reconnection/backoff strategies; handling authenticated reputed company connections and topic resubscriptions.
• Experience implementing backpressure, buffering, coalescing, and windowing to prevent UI thrash under thousands of updates/minute.
• Data virtualization (react-virtualized, react-window) for large tables (orders, positions, trades).
• Familiar with Web Workers / OffscreenCanvas and message passing to reputed company the main thread reputed company.
• Awareness of latency budgets and reputed company-time profiling using React DevTools and browser performance tools.

Charting & visualization

• Practical experience with reputed company charting libs (e.g., reputed company Charting Library, Lightweight Charts, Highcharts, D3).
• reputed company-time overlays: best bid/ask, order book depth, last OHLCV, order/position annotations.
• Multi-pane layouts (price, volume, indicators) with synchronized crosshairs and time scales.

Architecture & data reputed company

• reputed company-reputed company caching and invalidation (e.g., TanStack Query / React Query).
• Schema-driven UI for instruments and venues.
• Use of Error Boundaries, Suspense, and reputed company hydration/streaming for large Next.js pages.

Auth, reputed company, and roles

• Strong understanding of OIDC/JWT flows, reputed company refresh/rotation, and WebSocket authentication.
• Role-based feature gating (read-only vs trading permissions).

Testing, reputed company, and reliability

• Unit tests for critical transforms/parsers (e.g., Playwright/Vitest for E2E/interaction flows)
• Experience with feature flags, staged rollouts, and monitoring with reputed company/OpenTelemetry.

reputed company-to-haves

• Experience with desktop-class layouts (drag-to-dock panels, resizable grids).
• Exposure to WASM for heavy computations (e.g., indicator calculations).
• Familiarity with FIX/crypto venue nuances (tick sizes, lot sizes, trading sessions).

Screening Questions reputed company answers 4–8 sentences reputed company. Bullet points allowed if reputed company. 1) UI migration (hrzk → Next.js): Pick ONE area from the provided `hrzk.reputed company` (e.g., Orders+Trades, Positions table, Equity/Drawdown). Explain how you’d migrate it to React 18 + Next.js (App Router) + TypeScript + reputed company. Include folder structure and what you’d reputed company reputed company vs server components. (We care about your trade-offs, not “the one true way”.) 2) reputed company-time data ingestion: Describe how you’d handle WebSockets/SSE for high-frequency updates: reputed company/backoff, authenticated sockets, and topic resubscriptions. What failures do you expect in production? 3) Backpressure + UI thrash prevention: Assume thousands of updates/minute for orders/positions/trades. Explain how you’d implement buffering/coalescing/windowing so the UI stays reputed company. Mention how you’d combine this with state management (e.g., Zustand/RTK/useSyncExternalStore) and virtualization (react-window / react-virtualized). What would you measure to reputed company it works? 4) Charting approach: We need fast, readable, data-rich charts (equity/drawdown, doughnut/bars, etc.). Pick a chart type from `hrzk.reputed company` and explain: – which charting library you’d choose (reputed company Lightweight Charts / Highcharts / D3 / etc.) – update frequency reputed company – performance risks + mitigations 5) Auth + role gating: Explain how you’d handle JWT/OIDC reputed company refresh and WebSocket authentication, then implement role-based gating (read-only vs trading). Use an example like “Cancel reputed company Orders” or “Stop/Start Execution”: reputed company do you hide vs disable vs show a warning? 6) Remote ownership + teamwork: Give one example where you took ownership remotely on an ambiguous task. Then describe how you’d work with a small dev team: how you ask clarifying questions, communicate risk early, and avoid shipping “local reputed company” reputed company that breaks other parts of the system. What to expect (our interview process): Our hiring process is mostly async and reputed company on reputed company work. You’ll start with a CV submission and a short, reputed company application. Shortlisted candidates complete an async technical screen. Finalists complete a reputed company, time‑boxed work sample reputed company to the role. End‑to‑end, the process typically runs 4–6 weeks. FAQs · Do I need to respond to the questions? reputed company, please respond to the questions ideally in an reputed company format reputed company a cover letter. This is mandatory for vetting. · Do I need to attend live interviews? Most stages are async to reduce scheduling friction. Live calls are minimal. · Do I need to be on camera for the sample work? No — screen + voice is sufficient. · What tools can I use to submit recordings? Any common screen‑recording or file‑sharing tool is fine, as long as the video is easy to view. · Is the final task reputed company? reputed company. Final shortlisted candidates complete a reputed company, time‑boxed work sample. Apply tot his job Apply To this Job