Engineer- Data Visualization Platform

Tell me about a time you had to choose between a quick fix and a more scalable solution for a reporting or data tool. What did you pick and why?

judgment about engineering tradeoffs under time pressure and how they weigh cost versus reliability

Describe a situation where a team wasn't adopting a tool you built. What did you figure out was actually stopping them, and what did you do about it?

ability to diagnose adoption barriers rather than just blaming users or walking away

Tell me about a time you evaluated a new tool or technology and had to decide whether it was worth rolling out to the wider team.

judgment in vetting new technology versus chasing shiny tools

Tell me about a time you had to support a tool or platform you built after handing it off, when something broke that you didn't expect.

sense of ownership and follow-through on reliability, not just initial delivery

Walk me through a dashboard or reporting tool you built end to end, from the first data pull to what the user actually saw on screen.

whether the candidate has real hands-on experience shipping a visualization tool, not just querying data

How would you design a system that lets traders explore massive datasets in a notebook without waiting minutes for every query to come back?

understanding of performance tradeoffs when connecting interactive tools to large-scale backends like BigQuery

What's your experience with Looker, BigQuery, Plotly Dash, or Jupyter specifically, and where have you hit their limits?

depth versus surface familiarity with the actual tool stack this team maintains

How do you think about cost when a team wants to run heavy queries against a data warehouse for exploratory analysis?

awareness that visualization and reporting tools have real infrastructure costs, not just engineering effort

How do you structure Python code that's meant to be shared across many notebooks and dashboards, so people aren't copy-pasting the same logic everywhere?

software engineering discipline applied to what's often treated as throwaway analysis code

What's an example of a visualization or report that looked technically correct but still misled the person reading it? What was the fix?

attention to the gap between data correctness and honest, usable presentation

Say a live dashboard used by the trading desk starts showing stale or wrong numbers right before market open. What do you do in the first ten minutes?

incident response instincts and prioritization when reliability directly affects trading decisions

How would you go about learning the trading logic or business rules behind a dataset you've never worked with before, so your visualizations don't mislead anyone?

capacity to master complex domain-specific logic, which the posting flags as essential

If two trading teams want conflicting features in the same reporting platform and you can only build one this quarter, how do you decide?

stakeholder prioritization skills across teams with competing needs