Jeff Moser
I currently work at an international SaaS company. My title is Senior Cloud Engineer, but the bulk of the work is program leadership: cross-team priorities, incident command, and the status the SVP reads.
Each week I run the working session for a cross-functional group of about 40 people across development, production support, infrastructure, networking, and FinOps, in the U.S., Europe, and India. I ensure that every issue leaves with a clear owner and a next step. I surface blockers early, and I change course when the evidence says the plan is wrong. When a Severity 1 comes in, I take incident command and keep the SVP briefed until it's resolved. I've also delivered FedRAMP/GovCloud operations, including the NIST 800-88 decommissioning of a FedRAMP/ITAR environment with engineering, QA, and support.
That's been the pattern for twenty years: manage the work, and build the system the work runs on. At Boneal I was promoted from project manager to program manager when we won a $10M/year Air Force contract. I ran the program through its first renewal, and I designed and built the vendor portal, field ordering system, and control panels it ran on. Before that, at Lexmark, I managed 6 to 12 concurrent localization projects in up to 26 languages, coordinating engineering, product marketing, QA, and outside vendors to shared ship dates. Then I built the intranet tools that took hundreds of hours out of every project.
I run AI agents the same way. They work inside a platform I built, with hard stops in code for anything that touches production, money, or a client. The agents do the work. I make the calls that should stay with a person.
Next, I want a role where I'm accountable for the outcome, not just the coordination: the plan, the people it depends on, and the results. I've held that kind of seat on a federal contract, and much of my week now is the same work at a larger scale. (CSM, PMP candidate.)