This morning a recruiter offered me a seat I would have killed for ten years ago. Lead Salesforce Engineer. A major enterprise. A $70M+ platform migration, mid-flight, being restructured after a third-party implementation hit the rocks. An AI-first development mandate. Presenting to Enterprise Architecture and the Office of the CTO. The kind of role you put on a slide at Thanksgiving.
I replied with one line, my calendar link, and a remastered cut of the Top Gun Anthem:
“Cloudnimbusllc.com — I run these streets carrying the American flag.”
No counter-offer. No “let me think about it.” No three-paragraph let-me-circle-back. Just a flag, a guitar solo, and a way to book time with me if you want to talk about my mission instead.
It reads like a joke. It is not a joke. It is the most accurate résumé I have ever sent. So let me translate it — into the language of the suite.
1. I'm already the principal.
The role was to lead an AI-first development strategy inside someone else's program. I run one. Every day I ship Salesforce-native product — a free delivery platform, a Gantt engine that renders the same UI from a public web page and from inside Salesforce, and a forecasting system that turns a prioritized backlog into a staffed, paced, auto-scheduled timeline. I don't need a chair at the table. I built the table.
2. A $70M migration in turbulence doesn't need another contractor.
It needs an owner. The reason big programs wobble is rarely talent — it's that nobody in the room is personally accountable to the outcome the way a founder is to their own company. I optimize for that accountability. I've chosen to point it at my own platform first, and at the handful of clients I actually believe in.
3. I build where the work happens.
Two or three days a week on campus, presenting to the Office of the CTO, is a perfectly good life. But the deck is the tell. My entire thesis is that clarity should live in the system, not the slide — scope, status, forecast, and spend, all visible in the tool, so the meeting gets shorter every quarter instead of longer. I'm not trying to present the migration. I'm trying to make it self-driving.
4. The flag isn't a bit.
Everyone laughs at the flag line, and they're supposed to. But strip the swagger and it's a thesis: independence, conviction, and the willingness to stand for something specific in public. That is the exact posture I bring to an engagement. A serious client isn't hiring a pair of hands. They're hiring someone who will plant a flag on the outcome and not move.
Here's the uncomfortable part for the recruiting industry: the best people to lead your turnaround are the ones who don't need the job. The conviction that makes them worth hiring is the same conviction that makes them hard to hire. You can't recruit a flag. You can only ask it to point at your problem.
So — respectfully, and with a guitar solo: no.
To the recruiter: thank you, genuinely. It's a real role and a strong team, and someone is going to do great work in that seat. It just won't be me, because I already took the harder job — the one with no salary, no campus, and no Office of the CTO to present to. Just the work, the flag, and a calendar link.
If you've got a nine-figure program that needs someone who will treat your outcome like his own company — that link works for you too. It's the same one the recruiter got.
Glen Bradford
Founder & Principal Engineer, Cloud Nimbus LLC
Purdue IE + MBA. 10+ years on Salesforce. I run these streets carrying the American flag — and I ship product every day.
Share this