Front End Developer

At Taruvi, the JavaScript layer is what every engineer on the platform builds on typed client SDKs, shared UI packages, data provider abstractions, and the admin console that ties it all together.

This is not a build-screens-from-Figma role. Youll design TypeScript APIs that other engineers consume, maintain npm packages with real semver discipline, review and merge console PRs, and make architectural decisions that compound over time. If youve built SDKs or libraries, contributed meaningfully to open-source packages, or taken ownership of a complex admin console youll feel at home here.

What Youll Own

1. TypeScript Client SDK

Build and maintain the typed JavaScript SDK developers use to interact with the platform authentication, database queries, file storage, serverless functions, and analytics. Own the API design, error handling, request lifecycle, and versioned releases.

2. Data Provider Layer

Design and maintain the adapter layer that connects our React frontend to backend APIs covering filtering, sorting, pagination, auth state, and access control. This is the abstraction that keeps our data layer consistent and extensible as the platform grows.

3. Shared UI Component Package

Own a shared React component library used across multiple applications navigation, user profile, app switching, and embedded integrations. Ship it as a versioned npm package with TypeScript declarations and maintain backward compatibility across consumers.

4. Authentication Application

Maintain the login and authentication experience: email/password, OAuth provider flows, and token lifecycle management. Keep it reliable, secure, and easy to extend as auth requirements grow.

5. Admin Console Architecture and PR Reviews

Serve as the primary technical reviewer on a large, data-heavy React admin console. Set and enforce patterns, guide architectural decisions on new feature modules, and own frontend quality across the codebase.

What Were Looking For

Must have

1. TypeScript strict mode, generics, discriminated unions, utility types. You don't reach for any without a reason.

2. React depth you know how renders happen, how to prevent unnecessary ones, when use Layout Effect is the right call, and how React 19 changes your code. Not just component building.

3. Strong UI craft and modern CSS you build polished, responsive interfaces. You know Tailwind CSS, Grid, Flexbox, container queries, CSS custom properties, and mobile-first design. Not Bootstrap-era patterns. You make smart UI decisions independently.

4. Structured JS system experience SDKs, libraries, packages, framework adapters, or complex admin consoles. You write code that other engineers consume, with all the discipline that requires.

5. Package/library experience built or maintained reusable TypeScript packages, SDKs, or shared modules. If you haven't authored an SDK yourself, you've used them deeply enough to

understand their design API surface, error contracts, versioning, and DX. Published npm packages are a strong plus; internal or closed-source work counts equally.

6. API client design Axios interceptors, typed error hierarchies, fluent/builder APIs. You turn inconsistent backend contracts into stable abstractions.

7. Strong REST API understanding you read a backend API contract and model it cleanly on the client side. You understand REST conventions well enough to integrate new backend

modules independently and flag painful API designs early.

8. PR review judgment patterns and architecture, not just bugs. Your reviews are specific, constructive, and teachable. You hold a bar consistently across a team.

9. Node.js ecosystem fluency Common JS vs ESM, build tooling (tsup, Vite, tsc), module resolution, browser vs Node runtime differences.

10. Written communication clear PR reviews, API docs, migration notes, changelogs.

Strong plus

• Published npm packages with real download counts
• Maintained a library with semver discipline, changelogs, migration guides
• Meaningful open-source contributions to React, TypeScript, or build-tooling projects
• Experience with Refine.dev, React Admin, or similar data-driven admin frameworks
• Optimised large React apps re-renders, bundle size, slow routes
• Package release CI, compatibility testing, semantic versioning

What Success Looks Like

• You understand all five platform surfaces well enough to review changes in any of them with confidence
• Console PRs are held to consistent standards across types, tests, performance, and behaviour
• At least one shipped improvement that reduces duplicated auth/data logic or improves package reliability
• SDK and provider changes ship with better typed APIs, tests, and documentation
• The frontend platform is easier for other Taruvi engineers to build on than before you joined

Tech Stack

TypeScript, Node.js, React 19, Refine.dev v5

Material UI, Axios, Vite / tsup, Vitest

React Router, Monaco / CodeMirror

How to Apply

Send us:

1. GitHub profile or npm packages youve published

2. One project youre proud of — what made it hard (2–3 sentences)

3. One sentence on why SDK/platform work interests you over building from designsRole & responsibilities