Home / Careers
Work on products that ship, and stay shipped
Our engineers see their code installed in buildings, plants and homes, and then live with it for years. That is a specific kind of satisfaction and a specific kind of discipline.
Most software careers are spent on things that are replaced before they mature. Embedded and connected‑product work is different: what you write today will be running on hardware in five years, in places you cannot reach, on a version you have to be able to rebuild exactly.
That changes how we work. Reviews are thorough because a bad merge can reach the field. Documentation is real because someone here will need it. And engineers stay on a product long enough to understand it properly instead of rotating between accounts.
What we offer
- Long engagements on real products with real users
- Hardware on your desk, not only a simulator
- Time allocated for learning and for paying down technical debt
- Direct contact with clients and their engineers
- Flexible hours, with overlap for the team you work with
Open roles
Where we are hiring
Send a CV and a short note about something you have built. Links to code or a project you are proud of count for far more than a covering letter.
Embedded Linux Engineer
Yocto and Torizon images, device drivers, systemd services, secure boot and OTA on i.MX and similar platforms.
Firmware Engineer
STM32, ESP32 and nRF firmware on FreeRTOS, Zephyr or bare metal, with real low‑power and connectivity work.
Backend Engineer
NestJS or Go services, MQTT ingest, PostgreSQL, and the update and provisioning paths behind device fleets.
Frontend Engineer
Angular or React consoles that stay fast with large fleets, built on a shared design system.
Mobile Engineer
React Native applications with real device integration — BLE commissioning, offline sync and store releases.
Test & Quality Engineer
Automated test suites plus hardware‑in‑the‑loop rigs for firmware, including release verification.
Nothing here that fits? Write to info@nescorp.in anyway. We keep good applications on file and open roles as programmes grow.
Hiring process
Four steps, about two weeks
A short call
Twenty minutes on what you have built and what you want to work on next. No competency questionnaire.
A technical conversation
Ninety minutes with two engineers, working through a real problem from our domain. You may use any reference you would normally use.
A practical exercise
A small, scoped task you complete in your own time, capped at a few hours. Paid if it exceeds that. We review it with you rather than grading it silently.
Offer and start
A decision within three working days of the last step, with feedback either way.
Interested but not ready to apply?
Write to us anyway. A short conversation about what you are working on is welcome at any time.