How three teammates turned shared principles into stronger infrastructure, clearer customer conversations, and a successful product launch

A culture is easiest to understand when someone has to make a choice.

Do they wait for a problem to be assigned, or take responsibility for the outcome? Do they hand off the first workable answer, or improve the part that will matter later? Do they keep hard-won knowledge to themselves, or turn it into something the team can reuse?

Those are the choices our Operating System award recognizes. During each award cycle, TwelveLabs teammates nominate a peer whose work made our principles visible. Chris Jeon, Simon Lecointe, and Shannon Hong work in different parts of the company, but their stories share the same pattern: each saw a gap, expanded their ownership, and made the people around them more effective.

Chris Jeon	Simon Lecointe	Shannon Hong

Chris Jeon builds for the next problem too

When TwelveLabs needed to move critical model-training infrastructure across cloud environments, Chris, our ML Research Engineer, configured a new AWS GPU cluster and helped migrate the necessary data pipelines in 48 hours. Research teams were able to continue large-scale model training without losing momentum.

Completing the migration solved the immediate problem. Chris kept looking at what the system would need next.

During a related deployment, the GPU serving architecture was functional but unoptimized. Chris implemented additional quantization and performance improvements rather than pass those limitations downstream. Serving performance increased by 2.5 times, and model loading time fell from more than two minutes to 15 seconds. The improvement also made efficient autoscaling possible.

Chris’s work shows what Never Settle and Unbreakable Discipline look like when they are applied with judgment. The goal is recognizing when a shortcut will restrict the team later, then investing where rigor creates lasting value- not just endless optimization.

Simon Lecointe turns expertise into team leverage

TwelveLabs models can search hours of video for a single moment and reason about what is happening in a scene. During a live customer conversation, the field team also needs to make that capability concrete and easy to understand.

Simon, who leads Field Engineering, saw that the same gap was being solved repeatedly through one-off demonstrations. He built Gateway, a reusable product surface that helps the field team demonstrate TwelveLabs to enterprise and non-technical audiences, and shipped it in time for NAB.

Gateway moved knowledge that had lived in one person’s head into a tool the broader team could use. Simon paired it with onboarding that helped new teammates understand TwelveLabs and become productive faster. The result was a stronger demo and greater confidence and capacity across a growing team.

That is Own It End-to-End, Undeniable Customer Impact, and Compounding Velocity working together. Simon started with friction in a customer conversation, took responsibility for the system around it, and created a reusable solution rather than another temporary fix.

Shannon Hong creates the conditions for a team to deliver

Shannon joined TwelveLabs with the Pegasus 1.5 launch date already on the calendar. By her second week, she was working with engineering and science leads to define what had to ship, what could wait, and how a six-person team could protect the parts that mattered. Pegasus 1.5 launched as planned.

The same instinct appears outside the product roadmap. Shannon helped drive a company hackathon that produced tools people continued to use, and she contributes to Culture Club. In her words, knowing people beyond their day-to-day work ‘improves the everyday.’

That connection matters. Trust affects how quickly people surface a concern, share context, and depend on one another when a launch becomes difficult. Shannon’s story shows Compounding Velocity as a team property. A strong product manager creates clarity and helps excellent people move in the same direction.

Shared principles and different contributions

Chris made model infrastructure faster and more durable. Simon turned specialized knowledge into a tool the field could reuse. Shannon aligned a lean team around a difficult launch and invested in the trust behind it.

The same principles produced different choices in each role. A useful Operating System helps people make stronger decisions in the context of their own work. Across these three stories, the logic is consistent: take responsibility for the outcome, connect excellence to value other people can feel, and leave the next person and the next iteration stronger.

That is what we mean by excellence, validated by customer impact, compounded through velocity.

Congratulations to Chris, Simon, and Shannon. Thank you for showing us what the Operating System looks like in practice.

If this is the kind of work and team you want to help build, explore open roles at twelvelabs.io/careers.