Stand out for this role — generate a tailored resume and cover letter in about a minute.
WirelessCar is seeking a backend engineer to build and operate cloud-based services within the Assistance Services domain. You will work with Go, Python, and Java, leverage AWS, and contribute to monitoring, reliability, and incident response.
You will join Team Melvins and collaborate across WirelessCar and customer teams to deliver scalable, secure, and resilient backend solutions for connected-vehicle journeys.
Team Melvins builds and operates backend services within WirelessCar’s Assistance Services domain.
Team Melvins builds and operates backend services within WirelessCar’s Assistance Services domain. Our solutions support critical connected-vehicle journeys, including stolen vehicle tracking, emergency services, roadside assistance, vehicle positioning, and call-center operations. As part of the team, you’ll work with cloud-based services, APIs, integrations, databases and monitoring. Current initiatives include improving position handling for vehicle services, supporting new vehicle launches and customer rollouts, developing global assignment capabilities, migrating customer‑care solutions, and strengthening alarm management through PagerDuty. We work closely with teams across WirelessCar and with customers such as Volvo Cars, Jaguar LandRover, Polestar, and Subaru. Our responsibility extends throughout the service lifecycle—from design and development to testing, production rollout, monitoring, support, and continuous improvement. Join Team Melvins if you enjoy solving complex backend challenges, taking ownership of production services, and building reliable connected‑vehicle solutions used around the world.
You are open-minded, flexible and thrive under challenging and changing conditions. As person you are a curious, innovative, and analytical problem solver. You enjoy teamwork and have an inclusive approach to your work. You deliver high quality code and feel great ownership of the code you produce. You are willing to cater for the complete lifecycle of the code.
The team culture is based on collaboration and ownership. Instead of spoon-feeding individual team members with tasks, the team commits to delivering bigger user stories. User story breakdown and refinement is done in a collaborative on-demand fashion