Mateo
Full Stack Developer
ReactNode.jsPythonTypeScriptNext.jsMongoDBAWSAIAPIs
Shakers for companies
Work with a senior IoT Developer
A certified IoT Developer who bridges the three worlds of the craft: the device's firmware, the cloud platform that ingests its data and the pipeline that turns it into a decision. MQTT, sensors and AWS IoT Core are their daily workshop; the connected project, their deliverable.
Senior tech talent to take your IoT project from sensor to data, starting within days and on the stack that already runs in production.
- Certified talent in AI and agent skills
- Meet up to 3 AI Builders in 72 h
- Flexible collaboration models
+600
European clients across different industries
Top 4%
We work with the top 4% of certified talent in our community
72 hours
Meet 3 certified candidates in under 72 h
4.7/5
Our clients' satisfaction on Trustpilot
The talent mix your company needs
At Shakers you will find AI Engineers, IoT Developer and specialists across Tech, Product and Data
Ana
DevOps Engineer
DockerCI/CDAWSAzureKubernetesTerraformAmazon Bedrock
Lucas
Backend Developer
Node.jsPythonJavaGoPHPMySQLMongoDBDocker
.webp?width=1000&height=1000&name=Builder%20Kit%20(1).webp)
Emma
Security Engineer
Burp SuiteOWASP ZAPMetasploitNmapNessusTrivySnyk
IoT Developer: what this role brings to your project
An IoT Developer builds the bridge between the device and the decision: they program the sensor's firmware and connectivity, publish its telemetry via MQTT to the cloud platform that ingests it and leave it ready for the pipeline that turns it into useful data.
Their craft lives at the junction of three worlds: the device (sensors, ESP32, Arduino), the cloud platform that receives the data (AWS IoT Core) and the data pipeline that consumes it. They are firmware when they touch the device and cloud when they touch the data: the role is the bridge.
MQTTAWS IoT CorePythonfirmwaresensors and actuatorsC++ESP32ArduinoRaspberry PiLoRaWANBLEDockerKubernetesTerraformKafkaCI/CDLinuxAzure IoT Hubedge computing
One provider. One contract. Full traceability
How Shakers works for your company
Post your project
Tell us about the project, its scope, the expertise you need and when you want to get to work.
You get three options
We match your brief against certified talent and introduce the three AI Builders who fit best.
The last word is yours
Meet the three specialists and choose who you collaborate with; we handle the rest.
Why work with Shakers
The advantages of adding this profile with Shakers
From sensor to decision
Data travels from the device to your platform without patches: firmware, MQTT connectivity and cloud ingestion in a single brief, with every leg documented.
A connected prototype in weeks
From sensor to demo: the device publishing over MQTT and the platform ingesting, on ESP32, Arduino or Raspberry Pi depending on what your hardware calls for.
One team covering the three worlds
Firmware, cloud platform and data pipeline in the same brief: you do not hire one profile per layer or translate between two vendors.
On your cloud platform, not against it
AWS IoT Core, Azure IoT Hub or your own broker: the integrator works on the cloud that already runs in production and by its security rules.
Telemetry ready for your pipeline
Data arrives with an agreed schema and quality: what the device publishes goes straight into the pipeline that consumes it, with no manual processing.
Capacity without growing headcount
IoT by project, no hiring process: certified talent that joins with your access and scales the team when the project asks.
Can they take the IoT project end to end?
Yes: device firmware, connectivity, the cloud platform that ingests the data and delivery to the pipeline. The project team covers the width of the brief without you hiring four separate profiles.
Is an IoT Developer the same as a firmware developer?
They are firmware when they touch the device and cloud when they touch the data: they publish over MQTT, integrate the platform and leave the data ready for the pipeline. The craft is the bridge between the two shores, not just one.
What stack does an IoT Developer in Spain master?
The one real job ads ask for: MQTT as the protocol, AWS IoT Core as the platform, Python and C++ as the languages, ESP32 or Raspberry Pi on the device, and Docker, Kubernetes and CI/CD in the cloud layer.
Do I need the hardware chosen before kickoff?
No. If you already have devices, they work on them; if not, the scope includes recommending the hardware that fits your budget and your connectivity, from ESP32 to Raspberry Pi or a LoRaWAN gateway.
How much does it cost to work with an IoT Developer?
Scope sets it: which devices connect, which platform ingests the data and how much telemetry reaches the pipeline. At Shakers the budget closes per project before kickoff.
What happens to the project when the expert leaves?
You get every leg of the bridge documented: versioned firmware, platform configuration and the telemetry contract. Your team can maintain it or scale with the same specialist.
What gets delivered in the first weeks
The device publishing over MQTT, the cloud platform ingesting its telemetry and the first piece of data visible end to end: sensor, broker, cloud. Every leg documented.
A craft measured in real job ads
95 active tech job ads in Spain mention MQTT, according to Shakers market analysis (n=31,020, September 2026), and job boards show dozens of ads for the role (InfoJobs 74, LinkedIn 49-58). Niche demand, but real: they get hired as a cloud backend who also integrates devices.
Where the IoT Developer ends
They do not design the device's electronics nor build the pipeline: the hardware layer belongs to the electronics engineer and the already-ingested data, to the data engineer. Their ground is the bridge between the two.
A team by project, not a vacancy
The connected brief arrives as a goal: the device talking to the platform. Scope closes before kickoff, covering firmware, connectivity and cloud with the team the project asks for.
Connect with AI specialists to build your next project
Find specialists in Tech, Product, Data to complement your team
AWS Engineer
The device SDK and AWS IoT Core are their home: when the whole brief lives in Amazon, their platform integration shares account and deployment with yours.
Data Engineer
What the device publishes, they ingest: when the telemetry has to feed dashboards, a warehouse or models, the brief crosses from your bridge to their pipeline.
Backend Developer
Their APIs and microservices are the destination of the device's data: the cloud platform that ingests telemetry is almost always a backend they sustain.
DevOps Engineer
Their pipeline deploys the platform that ingests the data: containers, CI/CD and the cloud infrastructure where your telemetry lands.
The AI talent you need Certified by Shakers
We introduce you to three ready_to_build AI Builders in 72 hours.
