Full-Stack Developer — Telematics & Fleet Analytics Platform

About the role We run a production telematics + fuel-management platform for industrial fleets (mining, steel, logistics) — millions of MQTT messages a day, an R/Plumber REST API, a Next.js 16 / React 19 reports front-end on Vercel, and an Ansible-managed Linux fleet behind nginx. You'll ship end-to-end: design a new report, expose the API for it, optimize the slow query behind it, and roll the change out to prod. We move fast — typical week is 15–25 PRs across the stack. You should enjoy that pace, write tight diffs, and care about p95 latency the way other people care about pixels. What you'll actually do (sample PRs from our stack) Cut a dashboard endpoint's p90 from ~4s to <500ms with smarter caching and SCAN keys Build a new fuel consumption report — Plumber endpoint + TanStack Query hook + Plotly/Recharts visualization + deep-link parameters shared across reports Wire a postroute hook into the API to log per-request rt + status code, then dashboard it in Grafana/Loki Add a new auto-deploy user to the Ansible inventory and ship the playbook update Fix a UTC-vs-IST timezone bug that made "today" jump back a day between 00:00–05:29 IST Decommission a churned client end-to-end (entities, crons, DB, deploy config) in one clean PR Must-have skills Backend / API Strong REST API design — pagination, caching, idempotency, OpenAPI/Swagger Comfortable in R (or willing to ramp fast; we use Plumber, data.table, dbx); Python/Node experience also welcome SQL (MariaDB/MySQL) — query plans, indexes, window functions, timezone semantics Familiar with columnar formats (Parquet, Arrow) and time-series data Front-end TypeScript + React 18/19, Next.js (App Router, Turbopack) TanStack Query + Table + Virtual, Radix UI, Tailwind v4, shadcn-style components Charting with Plotly / Recharts / D3 / visx Map UIs (Google Maps via @vis.gl/react-google-maps or equivalent) Sense for perf: virtualization, polling/visibility gating, broadcast cache invalidation DevOps / Ops Ansible playbooks + inventories; Linux (Ubuntu) sysadmin basics Git + GitHub workflow — feature branches, draft PRs, conventional commits, code review etiquette nginx, systemd, cron, rsync, SSH key management Vercel (or similar) for front-end deploys; environment/secret hygiene Grafana / Loki / Prometheus dashboards and alerts; PostHog or similar product analytics Engineering judgement You write small, reversible PRs and verify before merging You read code before writing it; you don't refactor unrelated things in a bug-fix PR You spot a hardcoded secret, a NULL default that breaks Swagger, or a CURDATE() that means UTC midnight — and fix it without being told Nice-to-have IoT / MQTT / telematics protocol experience (Teltonika, NavTelecom, Concox, Omnicomm flespi) Fuel/EV/fleet domain background Experience migrating Shiny → React + API architectures Familiarity with Claude Code or AI-assisted development workflows What we don't expect A CS degree Knowing R on day one : if you're strong in Python/TypeScript and SQL, you'll pick it up "Senior" titles — 1 year of high-output work counts more than 5 years of coasting Working style 100% remote, async-first, India-hours Small team — your PRs ship the same week, often the same day We use Claude Code heavily; AI fluency is a multiplier, not a replacement for thinking To apply: send a GitHub link + 2–3 PRs you're proud of (yours or open-source contributions) to sm@mindshiftapps.net. Cover letters optional; a one-paragraph note on something you'd refactor in a project you've shipped is more useful.