Frontend Developer

About The Role Volta builds and operates large scale GPU compute infrastructure for AI workloads. Most of our platform is invisible to customers. This team owns the part that is not. You will join the platform engineering team that owns Volta's user-facing surface: the web console, the customer-facing APIs, and the infrastructure-as-code interfaces such as Terraform modules through which customers consume capacity programmatically. That team is a normal platform engineering team with two frontend developers embedded in it, not a separate frontend group. You will sit with the engineers building the services behind the console and work on the same problems from the other side. The people using what you build are engineers running large training and inference workloads. They care about density of information, speed, and predictability more than polish for its own sake, and they will notice when a console lies to them about the state of their cluster. What You Will Be Doing Build and extend the Volta web console: capacity and cluster views, provisioning workflows, quota and usage, access management, and operational visibility into customer environments. Work from designs and UX direction provided by the UX function, and give technical feedback on feasibility, performance, and edge cases before designs are finalized. Collaborate with platform engineers on API integration, contributing to that layer as part of the team rather than owning it independently. Act as the consumer voice on API design. You are the first user of every endpoint the team ships, so surface awkward shapes, missing states, and unclear errors while they are still cheap to change. Own the frontend codebase end to end: component structure, state management, styling, accessibility, testing, and performance. Handle the hard states properly: partial data, long-running provisioning operations, streaming telemetry, permission-scoped views, and multi-tenant boundaries where showing the wrong thing is a security problem. Contribute to frontend tooling, build pipelines, and quality standards, including generated API clients where we drive them from a schema. Support the developer-facing surface where it overlaps with your work: documentation examples, error messaging, and making sure the console and the API tell a consistent story. Participate in code review, technical design discussions, and cross-team collaboration in an Agile (Kanban or Scrum) environment. Take part in supporting what you ship in production, including triage of customer-reported issues against the console. What You Bring 3 to 5 years of professional frontend development experience. Strong proficiency in modern TypeScript, plus solid HTML and CSS fundamentals. Deep experience with at least one modern component framework (React, Vue, Angular, or equivalent), and comfort adapting to the team's chosen stack. Solid understanding of component design, state management, and frontend performance, including handling asynchronous and frequently changing data. Comfortable consuming REST or GraphQL APIs and collaborating with backend engineers on integration. Able to work effectively from UX designs without needing to own design decisions, and confident enough to push back when a design will not survive real data. Strong engineering fundamentals: clean code, testing, version control, code review, and CI/CD practices. Comfortable working in a technical domain. You do not need infrastructure experience, but you should be interested in what a GPU cluster is and why our customers care about it. Nice to Have (But Not Essential) None of these are required. Fluency with AI-assisted development: agentic CLI tools, IDE assistants, and orchestrating multiple coding agents through MCP, skills, or APIs to amplify delivery. Experience building developer-facing or technical UIs: cloud consoles, dashboards, admin panels, or observability tooling. Experience with data-dense interfaces: large tables, time series visualization, or real-time updating views. Familiarity with design systems or component libraries, or experience establishing one. Experience with schema-driven development: OpenAPI, generated clients, or contract testing between frontend and backend. Exposure to infrastructure as code from a user perspective: Terraform, Pulumi, or equivalent. Familiarity with authentication and authorization flows: OIDC, SAML, SSO, and permission-scoped UI. Some backend capability in any language, enough to make a small change on the other side of the API rather than waiting for someone else to. Experience working distributed across time zones with counterparts in other regions.