By: Natalie Johnson
Distributed engineering has become a permanent competitive advantage for technology companies. Unlike the old model of centralized teams operating from a single office, modern engineering organizations are increasingly built around globally distributed talent, asynchronous collaboration, and artificial intelligence (AI)-supported workflows. Yet while some organizations have mastered remote collaboration at scale, others continue to struggle with misalignment and burnout. For John Campbell Crighton, Chief Technology Officer (CTO) at ONEngine, the difference comes down to trust. “The thriving leader has engineered trust as infrastructure, not as a cultural aspiration, but as a technical discipline,” Crighton says.
Over more than two decades in software development, AI integration, and engineering leadership, Crighton has overseen global teams across healthcare, finance, energy, and technology. His work has included scaling electronic medical record (EMR) and revenue cycle management software used by more than 100,000 users, leading Amazon Web Services (AWS) migration initiatives, implementing quality assurance (QA) automation, and integrating AI-driven product efficiency across complex software environments. As AI integration accelerates across healthcare technology and software as a service (SaaS) scaling environments, Crighton believes the companies succeeding with distributed engineering are the ones creating systems where autonomy, accountability, and communication reinforce one another.
Building Distributed Engineering Around Clarity
“Distributed teams cannot survive in a surveillance culture, and you lose your best people first,” he says. High-performing remote teams succeed when every engineer can answer three questions clearly: What am I responsible for? Where do I go when I’m blocked? And what does “done” look like? Those principles became central while overseeing development, development operations (DevOps), product management, and support operations for a healthcare SaaS platform. By standardizing workflows and creating clear ownership structures, his teams maintained consistent delivery cycles, while supporting hundreds of thousands of users.
AI integration has further strengthened that approach. AI-assisted documentation, automated decision logs, and intelligent knowledge systems now help distributed teams access context faster without relying on constant synchronous communication. Still, Crighton cautions against assuming tools alone solve organizational problems. “The tools amplify the culture that already exists. They don’t create it,” he says.
Recognition and Autonomy Drive Retention
One of the clearest indicators of Crighton’s leadership philosophy is retention. Across globally distributed teams, he achieved a 98% employee retention rate while recruiting, onboarding, and mentoring more than 180 developers and QA professionals. “In a distributed environment, good work is invisible by default,” he says. Specific recognition matters more than generic praise. Rather than acknowledging entire departments broadly, he emphasizes publicly highlighting individual contributions and the real impact behind them.
At the same time, autonomy must remain genuine and Crighton opposes monitoring software that tracks idle time, online status, or keystrokes. He believes distributed engineers who feel micromanaged will disengage or leave. His approach to engineering leadership in the AI era looks at performance through outcomes and ownership. Visible growth also plays an important role. Engineers stay where they are challenged with meaningful work, exposed to difficult problems, and encouraged to expand their technical range.
AI Agents Are Reshaping Software Teams
The conversation around AI often focuses on replacement. Crighton sees something more nuanced happening inside engineering organizations. “AI tools are no longer just tools you invoke. They’re participants in the workflow,” he says. At ONEngine, AI agents assist with code reviews, documentation drafting, anomaly detection, unit testing, and onboarding support. Routine execution work, such as boilerplate code generation and repetitive debugging, increasingly moves toward AI systems. “An engineer who can direct agents effectively and review their output critically is worth dramatically more than one who can only execute manually,” Crighton says.
This evolution is also changing how CTOs build high-performing remote teams. Technical leaders now need engineers who can ask strong questions, challenge flawed AI output, and integrate automated work coherently into broader systems. The most effective organizations will continue investing heavily in human capital even as AI adoption accelerates. “Teams that are just replacing humans with agents are not growing. They’re failing internally,” he says.
The Operational Rhythm Behind SaaS Scaling
Beyond culture and AI integration, Crighton points to operational rhythm as one of the defining characteristics of successful distributed engineering. His teams typically operated on two-week sprints with four-week release cycles supported by strong continuous integration and continuous delivery (CI/CD) pipelines, close DevOps collaboration, and asynchronous workflows. “The rhythm is going to beat the intensity every time,” he says, pointing to how this supported major initiatives such as AWS migration projects, application programming interface (API) infrastructure scaling, and mobile application development.
Automated testing and QA automation also became central to maintaining release quality while accelerating delivery. AI-driven code reviews and regression testing allowed engineering teams to catch issues earlier and reduce operational friction. The future of engineering leadership will depend on building resilient systems that combine distributed talent, operational discipline, and AI-enhanced execution. The tools may continue evolving rapidly, but Crighton’s broader philosophy remains unchanged. “Trust is not a soft value. It’s the whole thing,” he says.
Follow John Campbell Crighton on LinkedIn for more insights.
