Frontend Engineer
Wordware Inc
San Francisco, CA, United States
2 days ago
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Apply on startup.jobs
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Contract type
Temporary contract
Employment type
Full-time (> 32 hours)
Experience level
Expert
Experience required
4 years minimum
Compensation
$180,000.0 - $240,000.0
Working hours
Regular working hours
Job source
Tech stack
Big Data
Large Language Models
Backend
Front End Software Development
Requirements
- 4+ years of frontend engineering with a portfolio of complex web apps you’ve shipped - we want to see multiplayer experiences, apps handling large data with sophisticated fetching and caching, or work with server-sent events (SSE).
- You love React and deeply understand state management. You know when to useMemo, how callbacks work, the component lifecycle, and you write beautiful, reusable components. You recognise when props are being drilled through multiple layers and should be lifted into context or Zustand instead.
- You’re comfortable owning a feature full-stack. You can do the DB migration, write the route in the backend, fetch on the frontend, and create the UI for it.
- Product sense and design intuition - you can take a rough product direction, sketch an interaction, and ship something that feels right.
- You care about performance. You know when to cache, when to refetch stale data, and how to optimistically update the UI. You notice duplicated network requests. You care about the app feeling snappy and responsive.
- You make design decisions - you’ll need to own some UX decisions, create simple designs when needed, and unblock yourself.
- High autonomy, low ego - you don’t wait for permission or perfect specs. You ship, gather feedback, and iterate.
- You care about craft - details like loading states, empty states, error messages, keyboard shortcuts. The 1000 small decisions that make software feel good.
Bonus
- Experience with multiplayer apps (Y.js, Automerge, CRDTs, or similar real-time collaboration frameworks).
- Built interfaces for LLM-based tools (streaming responses, handling uncertainty, progressive disclosure).
- Experience with local-first architectures (IndexedDB, service workers, sync strategies).
- Design background or strong visual sense - you can make things look good without a designer.
- Been a founding frontend engineer and established standards from scratch.
Benefits & conditions
- This is a full-time, in-person role based in San Francisco (Presidio) - we work from the office 5 days a week.
- You must be based in the Bay Area or willing to relocate before starting.
- We require US work authorisation, but are open to O-1 or J-1 visa sponsorship for exceptional candidates., Base salary: $180K-$240K + meaningful early-stage equity + health, dental, 401(k), considerable PTO, gym budget, lunch.
The Process
We keep our process simple. Exceptional candidates go from first touch to offer within 2 weeks.
- Application: Submit your resume and answer a few short questions. If it looks like a fit, we’ll invite you to send a 1-minute Loom video telling us who you are and why Wordware.
- 15-minute intro call: Align on location, motivation, and logistics. If it’s a go, we move fast from here.
- System design interview: A deep dive into how you think and architect systems. We’ll walk through a real Wordware problem together.
- Final conversation: We answer your questions and scope out the work trial.
- Work trial: Paid, in person, usually a few days to two weeks. You work on a real project with us. See how we work, see if it fits - both sides.
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Apply on startup.jobs
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Talks and stories from around this role — technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
CH
Chris Heilmann
about 2 years ago
CH
Chris Heilmann
Dev Digest 121 - AI goes offline
over 2 years ago
CH
Chris Heilmann
Dev Digest 118 - not a total recall
over 2 years ago
CH
Chris Heilmann
Dev Digest 132 - Binging WADFlix?
almost 2 years ago
CH
Chris Heilmann
Dev Digest 133 - Back to Front
almost 2 years ago
CH
Chris Heilmann
Dev Digest 129 - Now that's what I call private data!
about 2 years ago