Plane frontend engineer: India role building a React and TypeScript product

About Plane’s frontend engineering role

Plane is recruiting an India-based frontend engineer for its React and TypeScript work-management product. The role is built around a local-first client: information lives in the browser and needs to remain correct through intermittent connections and concurrent edits. That makes it more specialised than a simple marketing-site implementation. The employer expects demonstrated production engineering work rather than specifying a compulsory degree or minimum years.

Product surfaces and day-to-day engineering

The engineer owns user-facing features from design review through rollout, working with designers and backend colleagues. Responsibilities include dense issue views, a collaborative editor, caching and shared design-system components. Plane describes users across hosted and self-hosted environments, including versions that may differ from the latest cloud release. Engineers therefore investigate behaviour across browsers, screens and deployment contexts.

Performance, offline operation and shared state

The work includes profiling large issue views and improving rendering through techniques such as virtualisation and memoisation. Offline behaviour involves Service Workers and IndexedDB. Collaborative editing and synchronisation bring questions of serialisation and conflict resolution. These details are part of the advertised remit; candidates should consider whether their experience goes beyond rendering a component to understanding the state and data that keep the interface consistent.

Required production experience

Plane asks applicants to point to React and TypeScript they have shipped and discuss a decision they would now make differently. State-management reasoning, responsive CSS and experience with a shared component library are requested. The named examples include MobX, Redux and Zustand. The notice does not set a minimum number of professional years or a mandatory educational qualification.

Technology and preferred specialisms

The listed frontend environment includes React, TypeScript, Tailwind, MobX and React Router, with a ProseMirror-based editor and local-first synchronisation. Rich-text editor internals, offline-first or CRDT-backed work, open-source contributions and measured performance improvements are advantages. Electron, build tooling and backend services also appear in the broader stack, but this remains a frontend vacancy rather than an expectation to own every technology listed.

Location and terms not disclosed

The application is for India. The reviewed page does not specify the workplace arrangement, a salary figure or an application closing date. References to collaboration with Hyderabad and San Francisco do not by themselves establish a required office location or a particular working-hours schedule. Confirm the employment location, team hours and remote or office expectations with Plane’s recruiting team.

Application through Plane’s linked employer form

The official careers page links to the Ashby application for role 15cf6387-af74-4616-924f-3659fb76de01. Use that destination and supply accurate experience and contact information. If linking a project, make sure the link opens and that you can identify your contribution. The employer has not published a fixed interview-round count or a mandatory take-home assignment in this notice.

Practical preparation: choose a stateful interface example

A strong example might describe a large table, an editor or a feature that needed to survive a network interruption. Explain the user problem, where state lived, how updates were reconciled and what you measured after changing the implementation. This is suggested preparation for the published work, not a new eligibility condition. A small, well-explained project can be more informative than an unexplained collection of screenshots.

Questions to ask about the role

Clarify the initial feature ownership, expectations around community contributions and how frontend changes are tested against self-hosted versions. Ask how the team handles synchronisation bugs and coordinates changes with backend engineers. These questions arise from the advert’s specific constraints and help distinguish production frontend work from assumptions based only on the React title.

Relevant skills

• React
• TypeScript
• CSS
• State management
• IndexedDB
• Service Workers