Netic
Founding Web Platform Engineer
San Francisco
Sponsorship not specifiedDetected 179 days ago
TypeScriptReactNext.jsDatabricksDatadogPlatform EngineeringA/B TestingDesign SystemsAccessibilityLeadership
About the role
- Netic is the AI revenue engine for essential services who are the backbone of the American economy.
- There are now companies operating entirely AI-first on Netic.
- You think in terms of leverage, developer experience, and second-order effects on every product team downstream.
Responsibilities
- Build the Design System and Component Library: Year one, this is the centerpiece. Define the tokens, primitives, and patterns
- build a component library product engineers want to use because it's better than rolling their own. Own accessibility, theming, and the contracts that keep the UI coherent as the company grows.
- Create Frontend Platform Primitives with Leverage: Build the app shell, routing conventions, auth/session handling, typed API clients, data-fetching patterns, form and table frameworks, and the state primitives that product teams compose into features.
- Own Build, Performance, and Client Observability: Take responsibility for the Next.js build pipeline, bundle size, Core Web Vitals, error tracking, client-side logging, and feature-flag/experimentation plumbing.
- Set Frontend Platform Direction: Work with leadership to define the long-term architecture - build-vs-buy decisions, how the design system evolves, when to split into multiple apps or a monorepo, and how the platform scales as product surface area grows.
- Frontend Platform Experience: 5+ years building production web applications, with experience owning a design system, component library, or core frontend abstraction used by multiple product teams. Deep React and TypeScript fluency
- Design System Craft: You've built or substantially contributed to a real design system - not just a folder of components, but the tokens, primitives, accessibility baseline, documentation, and adoption story.
- You care about the difference between a component that works and one that's genuinely good to build with.
- Build the Design System and Component Library: Year one, this is the centerpiece.
- Define the tokens, primitives, and patterns; build a component library product engineers want to use because it's better than rolling their own.
Requirements
- You know when to generalize and, more importantly, when not to.
- Experience with frontend performance work, observability (Sentry/Datadog/equivalent), bundle analysis, migrations across many consumers, and shipping with confidence to production users.
- Operational Rigor: Experience with frontend performance work, observability (Sentry/Datadog/equivalent), bundle analysis, migrations across many consumers, and shipping with confidence to production users.
Skills
- Your success is measured by how easily other engineers ship powerful AI-driven product surfaces on top of your work.
Company info
- refinement of first principles thinking, execution, and craftsmanship
- We are an equal opportunity employer and do not discriminate on the basis of race, religion, national origin, gender, sexual orientation, age, veteran status, disability or any other legally protected status.
- Treat Product Engineers as Customers: Partner closely with product and engineering teams to understand their needs, eliminate friction, and design APIs and components that are intuitive, well-documented, and hard to misuse.
- Obsess over customers in each line of code
- With $43M in funding from Founders Fund, Greylock, Hanabi, and Dylan Field who led our Series B, we helped our customers book hundreds of thousands of jobs across services industries in North America.
This listing is sourced directly from Netic's careers page and normalized into a canonical job model.