Consulting
AI made building cheap. Knowing what’s worth building, and getting developers to use it, is the hard part.
Teams can ship a first version of almost anything in a weekend now. What they skip is the step in between: talking to the people they’re building for. So they build on assumptions, opinions and AI-generated conclusions, and wonder why developers don’t stick.
I help teams separate what customers actually said from what they assumed, test the riskiest assumptions first, and turn that evidence into products and stories developers trust. I’ve done it inside Amazon, Capital One, Google and Adobe, and at Major League Hacking with student developers.
Four ways to work together
Pick the one that fits where you are.
01 · Customer discovery coaching
You have an idea or an early product, and you’re not sure who it’s really for.
Hands-on coaching for founders and early teams: finding a real customer problem, running customer interviews, sharpening the value proposition, scoping the MVP and getting the pitch ready. I bring the questions and the push to test your riskiest assumptions; you keep ownership of the answers. You’ll know when the evidence says iterate, keep testing or pivot.
I’ve done this coaching before: with hackathon organizer teams at Major League Hacking, and with student developers. MLH · Google
02 · Developer journey audit
Developers sign up, then disappear, and you’re not sure where you lose them.
I go through your product the way a new developer would: sign-up, docs, first build, the emails that follow. I write down every place someone gets stuck. You get a ranked list of fixes across docs, onboarding and messaging, and the three to change first.
I did this at Adobe: I built a plugin following the published steps, documented the friction, recommended changes to the API docs and onboarding emails, and with an engineer helped launch a plugin-building wizard. See the Adobe story →
03 · Launch and adoption campaign
You’ve shipped something good, and developers don’t know about it or don’t believe it yet.
Research into who your developers really are, a story built on engineering proof they’ll trust, and a campaign that meets them where they already are: technical content, events, partners and the conference floor.
At Capital One, it meant repositioning a company developers saw as a bank as a technology company, all the way to re:Invent and its first developer-focused billboards in Las Vegas and San Francisco. See the Capital One story → At Amazon, it meant product marketing campaigns that helped developers take up new tools and AI. See the Amazon story →
04 · Part-time developer marketing and community
You need someone senior on this for months, not a one-off.
Ongoing developer marketing, DevRel programs, community and events, on a retainer of three months or more. I work across product, engineering and marketing so everyone tells the same story.
The same work I did managing brand and marketing for Google’s developer community programs, and hackathons at MLH. Google · MLH
What changes when I’m involved
- You learn what’s worth building before you spend months building it.
- Developers reach their first success faster, and more of them stay.
- Your message is one engineers believe, because it’s built on real proof.
- Product, engineering and marketing tell the same story.
- Decisions rest on customer evidence, not assumptions, opinions or AI-generated conclusions.
Teams and clients I’ve worked with
Amazon · AWS · Capital One · Google · Adobe · Major League Hacking · Dev Bootcamp · OliveWing
Rob’s ability to bridge the gap between innovative tools and the builders who use them, while continuously sharing his learnings with the team, made him an invaluable colleague.
He navigated onboarding into complex projects and programs with ease and rave reviews for going above and beyond his core scope. His work was so strong that Google was able to extend his contract beyond the 6 months.
Rob revitalized campus tours, engaging the entire staff on them in a lightweight fashion. … In the process, campus tours became one of our highest converting activities.
Hi, I’m Rob
I started out in QA and project coordination, fell for Chrome DevTools, and have spent the years since between product and the people who use it: admissions at Dev Bootcamp, hackathons at MLH, developer platforms at Adobe, developer communities at Google, and developer marketing at Capital One and Amazon. Read the whole story →
I still build, too. For OliveWing, a consulting client, I added a Neo4j graph database to its Replit app and set up Apify scrapers for Facebook posts and groups. Together they source and curate the highest-impact engagement and map it to candidate coverage and the people running. That work helped get OliveWing included in Substack’s midterms roundup. Read the OliveWing case study → · See all case studies →
How I think: Field Notes, short lessons from the work, and Megashift, my videocast with founders, developer-relations leaders and marketers.