A connection can cross a continent and still struggle with a bedroom. That is an awkward achievement for an industry accustomed to measuring progress in bigger numbers. The journey looks impressive until its final few metres, where a wall, a crowded radio channel or a badly placed access point gets a vote. For the person waiting on a video call, the geography of the rest of the network is largely beside the point.
Adam Hotchkiss has worked on both sides of that journey. Before co-founding Plume, he helped define optical transport systems at companies including Fujitsu, Qtera and Nortel. At Plume, his work turned toward cloud-managed connectivity inside homes. The scale changed. The recurring question did not: what has to happen between the equipment and the person for a service to become useful?
There is a revealing little scene from Plume’s early years. During a 2017 visit to its headquarters, Hotchkiss showed a visiting writer a tent used to test Wi-Fi equipment in a controlled environment. He also walked through a pod teardown. Around him were the unglamorous instruments of making a wireless product behave: isolation equipment, test mounts and the pieces inside a small casing. A tent in a networking lab is a useful reminder that even the cloud has to contend with physical reality.
That scene makes a better entrance to his story than an executive title. A product is easy to describe after it has become a neat object in a photograph. The harder work is arranging the conditions under which it can fail, learning something from the failure, and trying again. The laboratory offers fewer opportunities for applause, but considerably more opportunities to find the problem.
First, carry the light
Hotchkiss’s earlier career belonged to the optical side of telecommunications. At Fujitsu Network Communications, he worked on the launch of its first wavelength-division multiplexing system and supported SONET infrastructure. Wavelength-division multiplexing, usually shortened to WDM, puts multiple channels of light to work on a fibre. The vocabulary is specialist; the commercial purpose is straightforward. Carry more information, and deliver a service that operators can depend on.
He moved through product work at Qtera and Nortel, with responsibility for requirements and architecture on WDM transport products. Qtera was acquired by Nortel in 2000. Later, he became vice president of products at Menara Networks. These were roles concerned with bringing technical systems into service, where a promising design still had to satisfy the people buying and operating it.
His education was in electrical engineering. A 2022 conference biography records a bachelor of science from the University of Texas and more than eleven published or pending patents. That patent count belongs to the biography’s date, rather than serving as a running scoreboard. The more useful detail is the continuity: his product career has been grounded in network engineering, even as the networks and customers changed.
Read that career as a route toward Plume and the domestic setting becomes less surprising. A household is a small network with an unusually unruly membership. Devices arrive without an infrastructure planning meeting. Furniture moves without consulting the radio engineer. People expect coverage wherever they happen to sit. The house has very few of the manners one might wish for in a technical specification.
- Optical transportFujitsu · Qtera · Nortel
- Network productsMenara Networks
- The connected homePlume
The house refuses to hold still
Hotchkiss co-founded Plume with Fahri Diner, Aman Singla and Sri Nathan. By 2016, the company was bringing its self-optimizing Wi-Fi approach to market. Its pods made the system visible, but the ongoing management of those access points was central to the proposition. Coverage had to be considered together with the decisions that determined how the network behaved.
In a technical paper co-authored with Bill McFarland, Hotchkiss set out the case for a distributed access network managed by a centralized controller. The paper connects the design to differences in home size, surroundings and patterns of use. Its premise gives the home a history: the system can take account of what has been happening there, as well as what devices need now.
This is an appealing idea because a home is a moving target. Buying equipment happens on a particular day; using the network happens every day afterward. Those are different kinds of problem. Installation can establish a starting point. It cannot supply a permanent answer to every later change in where people work, what they connect or which neighbouring networks compete for the same air.
Hotchkiss also appears among the inventors on a 2017 patent application covering the process of claiming devices for a distributed home Wi-Fi network. It deals with discovering an access point, assigning it to a home network and relaying that claim to a cloud controller. This is the sort of detail a customer should be able to pass through without acquiring a new hobby. Making setup manageable requires someone to take the underlying machinery seriously.
Room AAccess point
Room BAccess point
Room C
A product with two audiences
Hotchkiss’s Plume roles have included product, customer solutions, client success and the business serving other companies. The combination matters. Plume works with communications service providers, so its product has to make sense to an operator while also improving the subscriber’s experience. An operator needs systems it can deploy and support. A household needs a connection it can use.
His recorded discussions repeatedly return to that relationship. In a 2021 podcast, he discussed Plume’s hardware-independent connected-home approach. In a separate video conversation about the platform, he addressed legacy firmware and the practical aims of reducing operating costs and customer departures. These subjects are less picturesque than a new gadget. They are also part of what determines whether a gadget’s accompanying service lasts.
OpenSync gives this work a concrete setting. The framework supports the delivery and modification of services across different networking devices. Hotchkiss was scheduled to introduce OpenSync Lite at the June 2024 summit in Taipei. A shared framework can make the conversation between a device and a cloud service more consistent; a provider still needs to turn that consistency into something its customers value.
There is an interesting burden in a job that sits between these audiences. The explanation has to travel in both directions. Technical capability must become an offer that a provider can operate. Customer frustration must become a problem engineers can identify. A lost connection is an experience before it is a diagnosis. The product work starts when someone can translate between the two.
Who gets the next packet?
One example arrived in February 2024, when Plume began rolling out Network Priority in its HomePass app. The feature used enhanced traffic identification covering more than 3,500 applications. It combined automatic prioritization with controls that let a subscriber temporarily boost an application category, a person or a particular device.
The choices included gaming, streaming and video calls, with boosts lasting three hours, six hours or until the end of the day. There was also a performance view using the ratings Excellent, Fair and Poor. These are modest words compared with the language used to sell networking equipment. Their advantage is that someone can understand them without first studying a radio standard.
The significance lies in the decision being presented. A network contains several demands at once, and a household can have a reason for caring about one of them more at a particular moment. Giving people a temporary control acknowledges that context. Automation can handle routine decisions; the person using the service can still have an opinion about today’s priorities.
Hotchkiss’s work also extended to the organization building those services. In March 2024, he oversaw the opening of Plume’s Hyderabad office. The company’s tenth office, and its first in India, was established for research and development spanning software, data engineering, DevOps and quality assurance. Product development in this setting includes the less visible work of putting a team in place to maintain what customers will eventually see.
Applications identified by the traffic-analysis capability behind the feature.
A brief turn in the chief executive’s chair
By February 2025, Hotchkiss was serving as Plume’s acting chief executive. In an interview that month, his emphasis was on effective consumer engagement and subscriber satisfaction, with less attention to the familiar catalogue of speeds and technical specifications. It was a continuation of the question his career had brought into the house: how does the network’s capability become a better experience for someone using it?
On April 23, 2025, Plume appointed Daniel Herscovici president and CEO and announced Hotchkiss’s transition to chief product officer. At that point, the company reported serving 65 million homes and small businesses worldwide. Hotchkiss described the mission as “to enable CSPs to deliver exceptional connected experiences.” The language stayed focused on providers and their customers, even during a change at the top.
His incoming colleague thanked him publicly for leading with “clarity and care.” The present-day leadership roster has since changed again: Alan Coleman is listed as Plume’s chief product officer. Hotchkiss’s time as interim CEO and his 2025 move into the product role are chapters in his career, with dates attached. The co-founder credit connects him to the company’s origins through those changes.
The sequence puts an ordinary truth about founding a company into view. There is more than one kind of work to do, and the title attached to a person can shift while the product continues evolving. A founder’s contribution is spread across decisions, teams and technical choices. An organizational chart captures a moment; a career takes longer to read.
“to enable CSPs to deliver exceptional connected experiences”
Adam Hotchkiss · April 2025
Yosemite, Bon Jovi, and a useful question
There are a few personal details that puncture the executive vocabulary. Asked about the most beautiful place he had visited, Hotchkiss chose Yosemite National Park. His last concert, he said in the same 2025 questionnaire, had been Bon Jovi, several years earlier. Asked where else he would like to spend a working day, he picked Anduril, because he wanted to learn about its projects.
His public profile also records service on the Dallas Margarita Society’s board from 2012 to 2015 and an emeritus directorship afterward. The society supports children’s charities and hosts the Dallas Margarita Ball. It is a pleasingly specific entry beside the networking work: civic involvement with a name that sounds considerably less like an engineering conference.
These details do not need to be forced into a theory of his personality. They give the profile some human scale. An engineer can spend years working through complicated systems and still offer an uncomplicated answer about a national park. A working life includes formal responsibilities, passing interests and things that require no product roadmap at all.
The useful question running through Hotchkiss’s professional story remains close to the user. What happens at the point where a capable network meets a person trying to get something done? The answer involves optical transport, software, access points, setup and support, depending on which part of his career you enter. Eventually, though, the connection has to reach the room. The household has other plans for its evening.