Senior Frontend Platform Engineer

About the role

You will design and build the visualization platform that powers TRM's investigative interfaces, including graph exploration and large-scale data visualization for global investigative workflows. You will develop high-performance rendering systems using technologies such as Canvas, WebGL, and GPU-accelerated rendering to visualize complex datasets with precision and speed. You will build reusable visualization libraries, SDKs, and platform primitives that enable teams across TRM to construct powerful data exploration experiences without starting from scratch. You will participate in technical design discussions and code reviews to continuously improve architecture, performance, and maintainability of frontend systems. You will develop a deep understanding of crypto and blockchain investigation workflows to directly inform product design and platform capabilities for investigators. You will help define the next generation of data exploration tools used by investigators and financial institutions worldwide to disrupt illicit activity. As an early member of the Frontend Engineering team, you will own foundational platform decisions that shape how visualization and rendering evolve across the product. You will work alongside product, design, and data platform teams to deliver impactful features that meet strict investigative and compliance needs.

Key facts

What you'll do

• Architect the core visualization platform that supports TRM's investigative interfaces and graph exploration capabilities at scale.
• Engineer high-performance rendering systems leveraging Canvas, WebGL, and GPU-accelerated rendering for complex and data-dense scenarios.
• Construct reusable visualization libraries, SDKs, and platform primitives that empower teams across TRM to build robust data exploration experiences.
• Engage in technical design discussions and code reviews to elevate architecture, performance, and long-term maintainability.
• Absorb crypto and blockchain investigation workflows deeply to translate operational needs into platform capabilities.
• Define and deliver the next generation of data exploration tools used by investigators and financial institutions worldwide.
• Lead the implementation of graph visualization and large relational dataset rendering as foundational platform primitives.
• Optimize performance in data-dense UIs using virtualization, viewport culling, Web Workers, and large-dataset rendering optimization strategies.
• Design and ship reusable frontend systems, SDKs, component libraries, and developer platforms that reduce friction for internal teams.
• Apply strong computer science fundamentals including data structures and algorithmic thinking to solve complex visualization problems.
• Build rich interfaces with React and modern frontend frameworks while maintaining strict performance and reliability standards.
• Collaborate closely with product, design, and data platform teams to align on roadmap priorities and delivery outcomes.
• Drive performance profiling and debugging for rendering pipelines to ensure smooth interactions with massive graph datasets.
• Contribute to open-source adjacent internal tools that standardize how visualization and exploration are done across TRM.

Requirements

• Bring strong JavaScript and TypeScript fundamentals with proven experience building large-scale frontend systems that handle complexity.
• Demonstrate experience building data-dense web applications such as analytics platforms, visualization tools, or mapping systems that serve critical workflows.
• Show hands-on experience with Canvas, WebGL, or GPU-accelerated rendering to construct high-throughput visualization layers.
• Have experience working with data visualization libraries such as D3, PixiJS, Three.js, or similar tools to translate data into interactive visuals.
• Exhibit experience building or working with graph and network visualization systems using tools like D3-force, Cytoscape.js, vis.js, Sigma.js, or similar technologies.
• Understand graph layouts such as force-directed, hierarchical, or radial layouts and know their tradeoffs in real-world scenarios.
• Apply experience optimizing performance in complex UIs using techniques such as virtualization, viewport culling, Web Workers, and large-dataset rendering optimization.
• Have experience designing reusable frontend systems, SDKs, component libraries, or developer platforms that enable cross-team productivity.
• Possess strong computer science fundamentals including data structures and algorithmic thinking to reason about scalability and performance.
• Have experience with React and modern frontend frameworks to build responsive and maintainable interfaces.
• Demonstrate ability to work effectively in a fast-paced environment where ruthless prioritization and rapid adaptation are essential.
• Show capacity to operate under execution pressure by challenging timelines and proposing reasoned tradeoffs to accelerate delivery.
• Exhibit ownership of time-boxed spiking efforts, proposing clear 1-week spikes with success criteria to de-risk implementation decisions quickly.
• Align with a team schedule that operates on a weekly sprint cadence and values technical ownership in project leadership.
• Communicate clearly within a distributed, timezone-mixed environment with at least 6 hours of overlap in North America hours.
• Engage with on-call responsibilities on a rotating basis approximately once every 16 weeks to triage frontend issues reported through support channels.

Nice to have

None specified.

Practical notes

The team operates on a weekly sprint schedule. Individuals on the team are tasked to lead projects as technical anchors, and are given a chance to grow and take ownership according to their level and goals. We work closely with product, design, and with our engineering partners in data platform teams to deliver impactful features to customers and the company. The team's timezone is a mix of EST and PST, with at least 6 hours of overlap with PST (8 am to 2 pm PST). On Call rotation is approximately one week every 16 weeks. Frontend usually does not get pager duty alerts but receives frontend issues from customer support channels and the on-call is responsible for triaging if it is a frontend bug or sometimes really a backend issue. It can get busy during some on-call weeks but has not been wake-up from sleep type of alerts.

• Ruthless Prioritization & Adaptability: We adapt quickly when faced with new information. For example, an engineer may message the PM or EM to prioritize Task A vs. Task B in the middle of the sprint - we don't let inertia guide our decisions. Instead we focus on ruthless prioritization and pivot quickly as needed.
• Challenging Timelines (Execution Pressure): An engineer questions a teammate's proposed 3-week timeline, and constructively argues for condensing it to 2 weeks - backed by rationale, tradeoffs, and a plan to reduce scope or increase velocity. They show ownership of delivery speed and willingness to push for urgency.
• Time-Boxed Spiking (Rapid Learning & Decision-Making): An engineer proposes a 1-week spike with a clear time-box and success criteria to explore implementation options or validate feasibility through a proof of concept. They demonstrate speed not just in execution, but in de-risking decisions early.