We are small, we make mains-voltage hardware, and we ship it ourselves. That combination means the work is unusually concrete: what you design on Tuesday is in a wall by autumn, and if you get it wrong someone's lights do not come on.
You cannot patch a switch that is screwed into a wall in another country. It focuses the mind in a way software rarely does.
Nobody here owns one narrow slice. Engineers talk to the people answering support email, because that is where you find out what you got wrong.
Our spec sheet says ±2% and means it. If a claim will not survive a customer with a meter, it does not go on the box.
Tooling, boards, firmware and assembly happen in the same building, so the feedback loop between designing something and building it is short.
If nothing here fits but you think you should be here, say so anyway. We have made roles for people before.
You would own the firmware that runs on every unit we ship: the Matter stack, the Thread radio, the power-harvesting logic that keeps a no-neutral switch alive, and the over-the-air update path.
Mains-side design, safety compliance and the physical guts of the product. You would be the person who signs off that a relay fails open.
Half of our support email is a wiring question and half is an LED driver behaving badly. You would be the person who works out which, and who tells engineering when the same thing turns up for the fifth time.
One form, five minutes. We reply to everyone, including the noes.
