Res is Research. Devs is Development. Those two are unambiguous, and most firms would have stopped there.
The n is doing two jobs at once, and both are deliberate.
Research and Development, joined by a nexus — the point where our own research stops being a paper and becomes software someone runs their day on.

Res is Research. Devs is Development. Those two are unambiguous, and most firms would have stopped there.
The n is doing two jobs at once, and both are deliberate.
The better reading. In computer science a nexus is the critical hub where data, architecture, and logic converge — a precise description of a firm that bridges theoretical research and working software.
A nexus is also where the high-level thinking happens: the environment where complex, abstract concepts get synthesised into functional technology. That is the company, compressed into one letter.
Seven research areas, six development practices, everything routed through the middle. Not an org chart — how a three-person company has to work.

Research Scientist
Data Scientist
AI Engineer
Leads the research arm. Core work is data science, computer vision, and artificial intelligence, extending into IoT and embedded systems — the span from a model to the device it runs on. Holds the line on a simple rule: a result that has not been evaluated is not a result.

UI/UX Engineer
Development Production Engineer
Leads the development arm and owns the path from prototype to production. Sits at the seam where interface design meets release engineering, which means caring equally about a focus ring and a deployment pipeline. Responsible for the design system this site is built on.

Consultant
Works across both arms — advising on research direction and on how it becomes product. Provides the clinical perspective behind DrChamber, and the outside view that keeps a small team from confusing an interesting problem with a worthwhile one.
Across data science, AI, NLP, vision, IoT and embedded systems — the work is peer-reviewed and published, not marketing.
Findings feed products; products surface real problems worth researching. The two halves keep each other honest.
CMS and DrChamber are live with real customers. The same team takes on selected client work to the same bar.
Code, architecture, and documentation are all communication. If the next engineer cannot follow it, it does not matter how clever it was.