> Markdown version of [/jobs/ext/3973688-founding-web-platform-engineer](https://www.wearedevelopers.com/jobs/ext/3973688-founding-web-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Founding Web Platform Engineer

- **Company:** NETIC CORPORATION
- **Location:** San Francisco, CA, United States
- **Contract:** Permanent contract
- **Skills:** JavaScript (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Computer Programming, Web Development, Design of User Interfaces, Human-Computer Interaction, Unix Shell, Next.js, TypeScript, Web Applications, Web Platforms, Web Usability, Datadog, Data Logging, Network Routers, ReactJS, Material UI, Sentry, Front End Software Development
- **Published:** October 27, 2026
- **Apply:** https://www.careerbuilder.com/job-details/founding-web-platform-engineer-san-francisco-ca--6bb30f18-47f4-48c7-b0a9-0a63949a0049

## About the Role

Web Programming, Funding, Artificial Intelligence (AI), Customer Support/Service, JavaScript, Unix Shell Programming, Product Engineering, User Interface/Experience (UI/UX), Web Programming, Application Programming Interface (API), * Frontend Platform Experience: A strong track record 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; strong Next.js experience (App Router, RSC, rendering tradeoffs).

 * 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.
 * Abstraction Thinking: Ability to design component APIs, hooks, and contracts that remain stable over time while supporting rapid product iteration. You know when to generalize and, more importantly, when not to.
 * Operational Rigor: Experience with frontend performance work, observability (Sentry/Datadog/equivalent), bundle analysis, migrations across many consumers, and shipping with confidence to production users.
 * Ownership Mentality: You take responsibility for long-term outcomes, not just shipping code. You think in terms of leverage, developer experience, and second-order effects on every product team downstream.

## Description

* 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. Your success is measured by how easily other engineers ship powerful AI-driven product surfaces on top of your work.
 * 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. Office hours, RFCs, migration guides - whatever it takes to make adoption the easy path.
 * 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. Make intentional tradeoffs around rendering strategy (SSR/RSC/CSR), caching, and code-splitting based on real product needs.
 * 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.