Knight CTO
AI systems & client engineering
Agent harnesses, swarms, autonomous repair, orchestration, inference and cloud execution. Creator of the Atlas avatar and a Slack auto-responder, alongside customer AI deployments.
About / Boris Knight
Deep in the build.
Accountable for the outcome.
AI systems engineer, founder and engineering leader. I connect hands-on technical work with the judgment it takes to build a product, lead a team and deliver for a customer.
The work I’m drawn to
Hard problems.
The whole system.
My applied-AI work developed over three years, with an intensive acceleration through a Knight CTO client engagement. I build the harness, the agent loop, the orchestration and the infrastructure—and stay with the work when it reaches the customer.
That has taken me from autonomous repair swarms to the Atlas avatar and a Slack auto-responder, from retrieval evaluation to model serving and customer deployments.
Founding SettleOn also meant leading people, choosing a market, bringing products to paying users and owning the decisions around them. Earlier engineering roles at AWS and Workday gave me another perspective on scale, reliability and cross-functional delivery.
See the systems I’ve builtExperience that informs the work
Founder perspective.
Enterprise depth.
SettleOn
Founder & CEO
Led 10 people across engineering and business development, including a tech lead and a business-development manager. Launched AI products with paying users; RevNode supported internal GTM.
AWS
Engineering & program leadership
Led two engineering teams totaling 15 people, including one manager. Separately led a 40-person program across six teams. Work spanned EC2 Spot pricing, capacity and allocation.
Workday
Enterprise engineering
Enterprise SaaS, integration platforms, engineering leadership and work across product and organizational boundaries.
Education
MBA · UC Berkeley, Haas School of Business
BS, Computer Science · Rutgers University
How I work
Judgment in the choices.
Care in the execution.
01
Start with the workflow.
Understand who needs the system, what they are trying to do and what success looks like before choosing the architecture.
02
Make the work inspectable.
Define acceptance criteria, retain evidence and distinguish an implementation from a verified outcome.
03
Stay close to delivery.
Carry decisions through code, integration and operation. Collaborate with the existing team and leave ownership clear.