Principal Engineer, Frontend
PlaneIndiaOn-Site
Needs a free Superjobs account. You'll finish on Plane's Ashby page.
Skill score
Summary
The Principal Frontend Engineer owns the frontend of Plane's local-first client, including dense issue views, the collaborative editor, the offline and caching layer, and shared design system components. The role suits a senior engineer who has built real-time, offline-capable, performance-sensitive React and TypeScript applications and can set architecture standards for a team.
- Function
- Development
- Estimated salary
- Est. ₹21–32 LPA
- Estimated for a staff-level role, ~10 yrs experience, India. Not published by the employer.
- Work mode and location
- On-Site, India
- Experience
- 10+ yrs
- Employment type
- Full-time
Job description
Overview
Plane's client is local-first. State lives in the browser and syncs when the network allows. It has to stay correct when two people edit the same document at once, and when a customer's cluster never touches the internet at all. Agents now act inside those same workspaces, so the interface has to show a change made by a machine as clearly as one made by a colleague. You will own the frontend of that client: the dense views that hold tens of thousands of issues, the collaborative editor, the offline and caching layer under both, and the design system components the rest of the product is built from. Day to day you work with designers, product, and backend engineers in San Francisco and Hyderabad, and your commits land in a public repository where contributors read them.
Roles and responsibilities
- Take Plane's frontend to real-time and local-first across work items, boards, documents, and other core product surfaces.
- Own client-side state, synchronization, caching, offline behavior, and conflict resolution.
- Own frontend performance in large workspaces: rendering, memory usage, load times, and interaction latency.
- Set frontend architecture and engineering standards, and review the designs and implementations that carry the most risk.
- Work with product, design, and backend teams to ship features that hold up from the API to the screen.
Skills required
Top skills
- React
- TypeScript
- Frontend architecture
- Real-time applications
All skills (8)
- WebSockets
- Local-first systems
- Client-side synchronization
- Frontend performance
- State management
- CRDTs
- IndexedDB
- Service Workers
Qualifications
- 10+ years of software engineering experience, with React, TypeScript, and frontend architecture at scale.
- You have built real-time applications using WebSockets, subscriptions, or event-driven architectures.
- You have worked on local-first problems: client-side persistence, synchronization, caching, and offline behavior.
- You have found and fixed frontend performance problems in complex, data-heavy applications.
- You understand state management and browser architecture, and you design frontend systems other people can maintain.
Nice to have
- You have built collaborative or multi-user applications with concurrent updates.
- You have worked with CRDTs, OT, or other synchronization and conflict-resolution approaches.
- You have built dense products such as project management tools, editors, spreadsheets, or design tools.
- You have used IndexedDB, Service Workers, virtualization, Web Workers, or similar browser technologies.
- You have contributed to or maintained large open-source applications.
Other details
- Frontend: React, TypeScript, Tailwind CSS, MobX, React Router
- Real-time and local-first: WebSockets, IndexedDB, Service Workers, client-side synchronization
- Editing: ProseMirror-based editor
- Platform: Electron, Vite, Rolldown, internal React component library
- Backend and observability: Python/Django, Golang, Postgres, Redis, REST/GraphQL, Datadog, Sentry
Company info
About Plane
Plane's mission is to build the infrastructure the world's work runs on. Every organization runs on three things: the projects it's driving, the knowledge it keeps, and the requests it fields. Plane brings all three into one open, adaptable platform: simple enough for any team to adopt, dependable enough for