Skip to content

Careers

Small team. Your name on the proposal.

We build the board, the firmware, the cloud and the app in one team — which means the person who writes the firmware sits with the person who writes the app, and both of them talk to the client. If you want to own a whole thing rather than a ticket, this is the trade.

Where we are right now

We hire against project load, so we would rather list the disciplines than invent vacancies.

Below is what we hire into and what we look for in each. Open applications are read — if there is nothing live when yours arrives we will say so plainly and keep it on file with your permission, rather than leave you waiting on a pipeline that does not exist.

What we hire into

Six disciplines, one team.

Embedded & firmware

C/C++ on ARM Cortex-M and ESP32, schematic reading, bring-up, RTOS, low-power design, and the OTA path that makes a fleet maintainable.

  • You have brought a board up from bare metal
  • You have debugged something with a scope, not just a printf
  • You care what happens when the power fails mid-write

Product & full-stack

TypeScript end to end — React or Next on the front, Node or Python on the back, Postgres underneath, deployed to AWS or GCP and maintained afterwards.

  • You can design a schema before you write an endpoint
  • You have owned something in production, including the pager
  • You write the boring admin screen properly

AI & machine learning

Applied work rather than research: retrieval pipelines, evaluation harnesses, fine-tuning where it earns its keep, computer vision, and getting models onto constrained hardware.

  • You measure before you claim
  • You have shipped something where a wrong answer mattered
  • You will say when a rule engine is the better answer

3D, games & interactive

Unity and Unreal, 3D modelling and texturing, architectural visualisation, VR/AR, and the optimisation work that makes any of it run on the target device.

  • A portfolio or a build we can open
  • You understand the budget — polys, draw calls, memory
  • Art and code are not separate people to you

Design — product & UX

Interface design for operational software and hardware companions. Dense screens that non-technical staff use all day, not marketing pages.

  • You have designed something with more than twelve screens
  • You can defend a layout with a reason
  • You design the empty, loading and error states too

Internships

Six months, paid, on a real project with a named mentor. We do not take interns to do documentation — you will have commits in something that ships.

  • Final year or recent graduate
  • Something you built that you can walk us through
  • Available for six months, not six weeks

How hiring runs

Four steps, and you are paid for the one that takes real time.

01

Apply with something you made

A repository, a build, a PCB, a portfolio, a write-up of a problem you solved. A CV alone tells us almost nothing we can act on.

02

A conversation, not a quiz

Forty-five minutes with the person you would work with, about what you have built and what went wrong in it. No whiteboard algorithms.

03

One paid exercise

A small, real, scoped piece of work — a few hours, paid at our standard rate. We do not ask anyone to work for free, and we do not run five rounds.

04

An answer either way

Within a week of the exercise, with the actual reason. Being told nothing is the worst part of applying anywhere and it costs us nothing to fix.

The terms, up front

  • Based in Lucknow, Uttar Pradesh. Hybrid, and fully remote across India for senior roles.
  • Pay is benchmarked and stated as a range in the first conversation, not extracted from you first.
  • You will be named on the proposals you work on. Clients know who built their system.
  • Hardware, licences and a machine that can actually run your toolchain are on us.
  • No unpaid overtime culture. If a deadline needs a weekend, the estimate was wrong and that is a management problem.
Apply to admin@thegradlew.com

Put the discipline in the subject line and a link to something you built in the body.

Start a project

Come with a problem. We'll scope it before we quote it.

Send us the constraint that worries you most. An engineer reads it — not a form queue — and replies within one working day.

Under NDA already? Say so in the brief and we'll send ours before you share anything technical.