> Markdown version of [/jobs/ext/154284-chief-of-staff-to-the-cto](https://www.wearedevelopers.com/jobs/ext/154284-chief-of-staff-to-the-cto). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Chief of Staff to the CTO - **Company:** Ron Turley Associates, Inc. - **Location:** Glendale, AZ, United States - **Experience:** Expert - **Salary:** $110,000.0 - $120,000.0 - **Contract:** Permanent contract - **Skills:** Microsoft Word, Microsoft Excel, Microsoft Windows, Artificial Intelligence, Confluence, JIRA, Microsoft Outlook, Software as a Service, Collaborative Software, DevOps, Microsoft PowerPoint, Scrum Methodology, Software Product Management, Release Management, Reliability Engineering, Software Engineering, Hubspot, GPT - **Published:** May 22, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=732dd7ec26912b18 ## About the Role Do you have experience in Video conferencing systems operation?, OK, the boring HR part of the job posting that looks like every other posting out there, but it's necessary: * 2 to 4 years of experience in some combination of: program or project management, release management, agile delivery, executive assistant or business operations support, technical product management, or a prior Chief of Staff role. Title doesn't matter, pattern does. * Proficient with Microsoft 365 (Outlook, Word, Excel, PowerPoint). * Experience with virtual collaboration tools like Zoom and Teams. * Excellent written communication. Clear, structured, no fluff. If your cover letter reads like generic AI output, we will notice. Bonus points and nice to haves: * SaaS background, especially vertical SaaS or B2B with a non-tech-native customer base. * Working knowledge of agile delivery (scrum, kanban, SAFe, or similar). You don't need to be a certified scrum master, but you should know how a healthy delivery process feels and what breaks it. * Hands-on with Jira, Confluence, HubSpot, Intercom. Our actual stack. * Experience supporting a CTO, CIO, CPO, or VP Engineering directly. * You've built a scorecard or dashboard from scratch (not just maintained someone else's). * You've run a release train, an incident review, or a leadership offsite. * Triple Yahtzee if you've sat in board prep cycles, even from the bench. The Bottom Line You've made it this far, so congratulations. We are really looking for ideal team players, with an almost frightening intensity around making things run well, the discipline to make a reporting rhythm look effortless, and a passion for serving the people on either side of them., * Ability to sit or stand for extended periods * Ability to work at a computer for prolonged periods * Ability to travel up to 10% (minimal travel based on business needs) ## Description RTA is looking for a Chief of Staff to the CTO. This role is the operational backbone of the CTO office, which spans Product Management, Software Engineering, QA, Infrastructure, Site Reliability, and Customer Support. You will own the reporting cadence, drive cross-team coordination, run point on release planning with Marketing, and keep the CTO's time and attention pointed at the things that actually matter. It is part program manager, part operations lead, part executive partner. None of those hats is full-time on its own. Together they are more than full-time, which is exactly the point. We don't do silos. Our four delivery teams (Innovation, Roadmap, Customer Experience, DevOps) work shoulder to shoulder, and the Product Steering Committee keeps us all rowing the same direction. You will be in the middle of all of it. A note up front: we care more about aptitude than checked boxes. If you don't hit every item on the list below but you have the wiring to pick it up fast, apply anyway. The learning curve here is vertical, and the people who thrive in this seat treated their last job as a launchpad rather than a destination. What We're Looking For In general, someone who: * Feels at home being a member of a healthy team. This means they aren't afraid to mix it up or be held accountable by the team, and they are willing to hold others accountable as well. * Passionately cares about our clients and helping them be more successful. Our clients are fleet managers, parts clerks, automotive technicians, and they maintain everything from squad cars to school buses so that everyone comes home safely at the end of the day. * Thinks of themselves less, while not thinking less of themselves. They are other-centric, compassionate, and self-assured. * Is willing to lift boxes, clean floors, and hold doors if that's what it takes to get something done, because no job is beneath them. * Takes ownership and initiative. They don't wait to be told what to do. They own their role and how to make it better. * Loves to read, learn, grow, and stretch themselves. Bonus points for each book they've read by Patrick Lencioni. * Is AI-native. Uses Claude, ChatGPT, or equivalent every day, and has views on what they're good and bad at. We will ask. Specifically for this job, someone who: * Owns the operational drumbeat: weekly C-suite tactical scorecards, Monthly Business Reviews, trimester board materials, and the monthly board-member check-in. Reporting isn't a fire drill, it's a rhythm. * Builds and maintains the dashboards and metrics that feed the reporting cadence, instead of rebuilding them every cycle from scratch. * Runs release coordination across Product, Engineering, QA, Customer Experience, and DevOps. Is the connective tissue when handoffs break. * Partners with Marketing on go-to-market and communications planning for releases. Makes sure customer-facing messaging, enablement, and launch timing line up with what's actually shipping. * Drives cross-functional initiatives end to end. New QA tooling rollout. AI workflow adoption push. A customer-impacting release. They don't all fit on an org chart, but they all need to get done. * Preps the CTO for every meeting that matters. Talking points, context, what's changed since last time. * Drafts internal communications: all-hands updates, board memos, Executive Team briefs, internal announcements. Writes clearly and structurally, with no fluff. * Is a thought partner. Can push back on a half-baked idea respectfully, in private, before it leaves the room. * Actively manages the CTO's calendar. Triages requests, defends deep-work time, sequences meetings logically, resolves conflicts before they show up. * Handles meeting prep and follow-through: agendas built in advance, materials staged, action items captured and chased to completion. * Supports inbox and Slack triage. Flags what needs attention, drafts responses for review, keeps low-value noise out of the queue. * Owns travel planning, expense management, and other executive operations hygiene. This is real work, done at a high level, and it frees up CTO focus for the things only the CTO can do. * Coordinates CTO Team logistics. Offsite planning, leadership team rhythms, executive guest visits. Does this sound like you? Let's talk. Key Results Areas (aka the Job Outcomes) * The CTO's reporting commitments (weekly tactical, Monthly Business Reviews, board materials, monthly board check-in) are delivered on time, accurate, and visually clean, without becoming the CTO's job to assemble. * Cross-team release coordination runs predictably. Marketing knows what's launching when. Customers don't get surprised by what shows up. * The CTO's calendar reflects strategic priorities, not whatever filled the white space first. * Commitments made in leadership meetings actually get done, tracked transparently, and closed out. ## Related Videos - [Hidden efficiency - How to enable your non-engineers as a CTO](https://www.wearedevelopers.com/videos/1412-hidden-efficiency-how-to-enable-your-non-engineers-as-a-cto) - [ Evaluating AI models for code comprehension](https://www.wearedevelopers.com/videos/1462-evaluating-ai-models-for-code-comprehension) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [From DevOps to Scaled DevOps: How We’re Rebuilding Continuous Delivery as a Platform](https://www.wearedevelopers.com/videos/100018-from-devops-to-scaled-devops-how-we-re-rebuilding-continuous-delivery-as-a-platform) - [Beyond the 9–5: Designing Work Around Humans](https://www.wearedevelopers.com/videos/1321-beyond-the-9-5-designing-work-around-humans) - [Speak, Code, Deploy: Transforming Developer Experience with Voice Commands](https://www.wearedevelopers.com/videos/1159-speak-code-deploy-transforming-developer-experience-with-voice-commands) ## Related Articles - [Remote Work: Best Practices for Developers](https://www.wearedevelopers.com/magazine/315-remote-work-best-practices-for-developers) - [Tips on mastering remote job interviews](https://www.wearedevelopers.com/magazine/23-tips-on-mastering-remote-job-interviews) - [Best US AI Conferences for CTOs in 2026: Build vs. Buy, Vendor Evaluation, and Peer Intelligence](https://www.wearedevelopers.com/magazine/736-best-us-ai-conferences-for-ctos-in-2026-build-vs-buy-vendor-evaluation-and-peer-intelligence) - [Should Tech Managers Be Developers First? Pros and Cons](https://www.wearedevelopers.com/magazine/327-should-tech-managers-be-developers-first-pros-and-cons) - [How to Have an Effective 1-on-1 Meeting](https://www.wearedevelopers.com/magazine/451-how-to-have-an-effective-1-on-1-meeting) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer)