# Frontend Software Engineer, Data at Nominal

- Company: Nominal
- What the company does: Nominal powers mission-critical engineering with advanced data infrastructure, real-time observability, and analysis tools — all in one collaborative platform. Backed by General Catalyst, Lightspeed and Sequoia.
- Company website: https://www.nominal.io/
- Type: Startups
- Level: Mid level
- Location: New York, United States
- Work setup: On-site
- Pay: $225K to $275K base salary per year (USD)
- Posted: 2026-07-24
- Apply by: 2026-10-08
- Apply: https://jobs.gem.com/nominal/am9icG9zdDrbptXZF5p2IggDOYItrPMr
- Page: https://www.1752.vc/careers/jobs/nominal-frontend-software-engineer-data/

## About the role

Build interfaces that help engineers explore, understand, and act on large-scale telemetry and operational data. You'll help define the underlying data models and user workflows that power the product. Partner closely with product, design, and engineering to turn loosely defined ideas into intuitive user experiences. You'll challenge assumptions, validate workflows directly with users, and make confident product decisions when requirements are incomplete.

## What they're looking for

- 5+ years of experience building products for technical users where you’ve been involved in shaping the data model
- Strong experience with TypeScript, and modern frontend architecture, along with an understanding of how frontend systems interact with backend services
- A track record of navigating ambiguity by defining problems, forming hypotheses, and iterating with users instead of waiting for complete specifications
- Strong product instincts. You naturally ask "Why are we building this?" before "How should I implement it?" and aren't afraid to challenge assumptions when you believe there's a better solution for users
- A systems mindset. You enjoy reasoning about data models, user workflows, and how complex systems should behave before jumping into implementation
- Excellent communication skills and the ability to explain technical and product tradeoffs clearly across engineering, design, and product teams