We use essential technologies to keep Swiftcruit secure and running. With your permission, we also use analytics and marketing technologies to understand usage and improve the product. You can change this anytime from Cookie Settings in the footer. Read our Cookie Policy.
Software Engineer — Frontend at clearwateranalytics | Swiftcruit
Location: Mumbai Hybrid: Yes (4 days WFO) Experience: 5–8 years Team: UI/UX Engineering — Capital Markets Platform
About the role
We are looking for a hands-on senior engineer who treats the front end as a first-class engineering discipline — someone who can ship pixel-precise, fully-tested features across a complex web platform and a mobile companion app, and is energised by the challenge of building real-time, data-heavy UI for institutional finance users.
You will join a tight-knit frontend group that owns a large-scale TypeScript monorepo powering a desktop-class web application (deployed inside a multi-window desktop shell), a React Native mobile companion, and a Storybook-driven component library that ties them together. The work is deeply technical, deeply user-facing, and visibly impactful — our users make decisions worth millions of dollars on screens we build.
What you'll work on
Build production features across the stack — from data-grid blotters showing thousands of live-updating rows, to portfolio analytics dashboards, to mobile workflows for on-the-go users.
Own real-time data pipelines on the client — Web Workers, IndexedDB-backed live queries (Dexie + Observable patterns), WebSocket-driven state, all under tight latency and memory budgets.
Treat performance as a feature — virtualised grids, memoised render trees, careful re-architecture when something slows down; profiling and fixing isn't optional, it's the job.
Design and evolve shared packages — we ship 25+ internal libraries (components, hooks, utilities, domain-specific modules); your work routinely benefits every team using them.
Drive quality — Jest + React Testing Library for units, Playwright for end-to-end, snapshot discipline, coverage ratchets in CI. Tests are written by the author, reviewed by peers, and required before merge.
Review code with intent — RFC-style design discussions, thoughtful PR feedback, and a willingness to push back when something can be done better.
Collaborate cross-functionally with product managers, designers, and back-end teams to ship features end-to-end.
Tech you'll work with day-to-day
React 18, TypeScript 5.x, styled-components for the web client
React Native + Expo for the mobile companion app
Rush + PNPM monorepo with 25+ internal packages, code generators, and a CI build matrix
AG Grid Enterprise for high-performance data grids and Highcharts for visualisations
Dexie / IndexedDB for client-side persistence and reactive live queries
Web Workers for off-main-thread message processing
OpenFin (HTML5 desktop runtime) for multi-window, multi-monitor desktop deployments
Jest, React Testing Library, Playwright for testing; Storybook for component-driven development
Jenkins, SonarQube, ESLint, Prettier, Conventional Commits in the delivery pipeline
What we're looking for (must-have)
5–8 years of professional software engineering, with a substantial portion (3+ years) building production React applications in TypeScript.
Deep React fundamentals — hooks, rendering model, reconciliation, suspense, performance characteristics. You can debug a slow render or a stale closure without reaching for a tutorial.
Strong TypeScript — generics, conditional types, mapped types, discriminated unions; you reach for type safety, not any.
Production React Native experience — Good to have knowledge of developing and shipping Mobile apps, ideally maintained across both iOS and Android, and working knowledge of native modules, build pipelines, and the realities of mobile (offline, low-bandwidth, app-store review).
Solid CSS and design-system sensibility — you can read a Figma file, build it accessibly, and know when to push back on a spec.
Testing as a habit, not a chore — unit, integration, and end-to-end. You can describe what screen.findByRole does and when to reach for waitFor.
Comfort in a monorepo with shared packages — versioning, dependency graphs, the discipline of not breaking your neighbours.
Clear written and verbal communication — most of our team operates across multiple time zones; words on a PR thread are how decisions get made.
Nice-to-have (any one of these is a real plus)
Java exposure — even reading-level fluency is valuable. We integrate with Java-backed services daily; engineers who can navigate both sides of the wire move faster and design better APIs.
Experience with AI-assisted development tooling — Claude Code, Cursor, Windsurf, GitHub Copilot, or similar agentic / coding-assistant workflows. We're actively investing in raising the team's leverage with these tools; people who already think this way will shape how we adopt them.
Capital markets / financial-services / fintech domain knowledge — buy-side or sell-side, OEMS/EMS, portfolio management, risk, compliance, trading workflows, market data, reference data, settlement, or anything adjacent. Domain fluency is rare and prized: it shortens the path from requirement to working feature.
Real-time / data-grid heavy applications — experience building UIs over WebSocket / SSE streams, with virtualised tables of thousands of rows.
Desktop-app development — Electron, OpenFin, Tauri, or similar.
Open-source contributions to the React / TypeScript / RN ecosystems.
How we work
Quality over speed — we ship when it's right, not when it's first.
Small PRs, fast feedback — no week-long branches if we can help it.
Tests with every change — non-negotiable, but supported with strong tooling.
Documented decisions — design docs for non-trivial work, ADRs for cross-cutting changes.
Conventional commits + automated changelogs so release notes write themselves.
Modern tooling, with a willingness to evolve it — we replace what no longer serves us, and we expect you to push for those replacements.
What you can expect from us
A team of senior engineers who care about craft.
Direct, written feedback on your code and your ideas.
Latitude to choose the right tool for the job — and the responsibility that comes with that.
Visible, business-critical work used every day by sophisticated users.
