The Salary Table as a Behavioral Anchor

Not every data visualization is a chart. On HackerU's course pages, the most important one is a potential-salary table, and it's deliberately a table — used as a behavioral anchor that gives a prospective student a concrete sense of the payoff before they read the syllabus. Designing it was as much about structure as styling. For engineering, the relevant detail is that this is a reusable, data-shaped component, not a hand-set graphic: it has to render varying rows across many courses, stay legible on mobile, and slot into the same modular system as the rest of the page. I designed it so the comparison reads at a glance — clear columns, restrained emphasis on the figures that anchor the decision — while remaining structured data the front end can populate per course rather than a one-off image. That distinction matters to an R&D team: a styled table scales and stays maintainable across the catalog, an exported graphic does not. The broader principle is matching the visualization to the cognitive job. Here the job is anchoring an expectation and supporting a comparison, and a well-structured, well-typed table does that better — and far more sustainably — than a flashier chart would.