Company
Five centers, 32 engineers: who actually builds your remote
Published 2026-11-02 · Company · 5 min read
A supplier review often begins with a factory tour. The more useful question comes after it: who sits between the tour and the production line, and who owns the change when a detail moves?
One company in Shenzhen since 2014
Shenzhen Serow Electronics was established in 2014 and operates as an engineering-led ODM with its own manufacturing center. The company is not a trading desk that forwards a brief to a factory. Design, tooling, electronics, firmware and assembly sit inside the same organization, under one general manager and five centers.
Where the 32 engineers sit
The engineering organization is 32 people: 10 in software, 7 in mechanical, 4 in electronics, 2 in industrial design, 4 in project management, 2 in certification, 1 in design quality assurance and 2 in verification. The split matters more than the total. A housing change is reviewed by the mechanical team that will release the tool, the electronics team that owns the PCB envelope, and the firmware team that has to keep the key map working. They are in the same building.
What that changes in a program
In a fragmented supply chain, the ID studio, the tool shop and the firmware house each finish their part and hand it on. Problems appear at the handoff, when the housing no longer fits the board or the key legends no longer match the firmware. Here the handoff is an internal review with one configuration record. When a buyer asks why a sample changed, the answer comes from the same team that built it.
How a program is staffed
A program does not consume the whole group. A project manager pulls a small team from each discipline, and the same verification engineer follows the build from first sample to pilot. That continuity is deliberate: the person who wrote the test plan should be the person who signs the result. When the program ends, the configuration record stays with the platform, so the next variant does not start from a blank page.
How a first review runs
A first review is not a sales presentation. We ask for the control target, the radio the installed base uses, the market the product ships to and the date the buyer is working towards. From those four answers the team can sketch an architecture and name the decisions that will constrain it: battery or cell type, key count, housing process and certification route.
If the answers are not settled, the review ends with a shorter list of questions rather than a quotation. That is deliberate. A price issued before the control target is fixed is a number that will move, and moving numbers cost more time than the questions would have.
What the number does not prove
Headcount is not capability. Thirty-two engineers can still miss a deadline, and a smaller team can run a cleaner program. The useful test is a reference call and a review of how a previous change was handled: who found it, what it cost and whether the schedule moved. We publish the structure so a buyer can ask better questions, not so the number can replace them.
Figures describe the current engineering organization. Project teams are assigned per program.
More from the newsroom
Keep reading.
Three other notes from the same team.
Start a project
Send the control target, not a catalogue request.
Tell us what the remote has to control, which radio the installed base uses, and where it ships. We will reply with the questions that decide the architecture.