juliettech

growth eng 👩🏻‍💻 | co-founder @surge_women prev head of devrel @helicone_ai @cyfrinaudits @aragonproject

[juliettech @_juliettech]

Canadians are consistently some of the nicest people I’ve met.

I’ve also been in Vancouver for less than 1h and have already seen 3 people doing crack on the street.

What’s going on?

[juliettech @_juliettech]

can confirm

[Connor Loi @connortbot]

when i was working at helicone i just spent every day third wheeling two work husbands

[juliettech @_juliettech]

is it crazy that I kinda want to buy @posthog swag?

[juliettech @_juliettech]

Really love this idea.

We've been organically doing it at Play Money in the last quarter and results are pretty wild.

- Built an entirely new product
- Regenerated our email marketing campaigns w/ cron jobs
- Live dashboards help us make decisions and understand data we then feed into our AI for context
.... the list goes on

[Praveen Neppalli @praveenTweets]

Agentic AI adoption is on fire at @Uber, and it's changing the way we build, not just in engineering, but across the entire company.

Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents. And our engineers have built 2,500+ agent skills across the software development lifecycle.
Those numbers are exciting, but they led us to a much bigger question:

How do we bring agentic AI beyond engineering?

Finance. Legal. Operations. Marketing. Customer Support. HR. Procurement.

These functions run on complex workflows that are often manual, highly nuanced, and spread across dozens of systems. You can't automate them effectively by looking at process diagrams or documentation. You have to understand how the work actually gets done.

So we created something called Agentic Pods.

The idea is simple.

We handpicked ~30 of our most AI-proficient engineers (people with deep knowledge of Uber's systems) and paired each of them with a domain expert from a business function.

Then we gave every pod just two weeks.
• Days 1 – 2: Shadow the expert. Observe every step. Document workflows. Ask questions. Build intuition.
• Day 3: Prioritize opportunities based on scale, repetition, business impact, and data availability.
• Days 4 – 5: Build a working agent alongside the person doing the job.
• Days 6 – 9: Validate with several others performing the same work. Does it generalize? Does it actually make their job better?
• Day 10: Ship.

In just the past two months, we've run 16 Agentic Pods across 16 different business functions.
• Capital allocation across 150 cities: 15 hours → 30 minutes.
• Financial pacing reports: 2 days → 10 minutes.
• Marketing web quality assurance: 2 weeks → 50 minutes.
• Support workflow creation: 9,000 manual workflows → self-service automation.

The productivity gains are impressive, but what surprised us most wasn't the speed.
• It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight.
• The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making.
• The workflow becomes the unit of automation - not the individual task.
• The most impactful agent skills cut across teams, orgs, functions, tools, and systems.

The biggest lesson? The best AI opportunities are rarely visible from the outside.

You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them.

We're now forming a dedicated team to scale this further and go deeper. They'll deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates.

It's exciting times!

[juliettech @_juliettech]

you know you’re in latam when people start clapping upon landing

[juliettech @_juliettech]

ok im fable-pilled

[Cole Gottdank @coleywoleyyy]

33k views & hundreds of comments later...

The GTM engineer community is live!!! 🥳

If you want to join, you must fill out the Google form (linked below).

This is a requirement to ensure the community is high quality.

👇
https://t.co/1cM3ZX8Q2I

[juliettech @_juliettech]

@coleywoleyyy have you tested GLM 5.2 yet? rumor on the streets is it kills gpt 5.5 at half or the price

[juliettech @_juliettech]

@coleywoleyyy lol yes please

[juliettech @_juliettech]

@rohanpaul_ai @grok what's the source of this data?

[juliettech @_juliettech]

you catch more flies with honey

[Alex Lieberman @businessbarista]

I stole this idea and now use it with every single employee.

It’s the best illustration I’ve seen of teaching someone to be high agency.

It says there are 5 levels of work:

Level 1: “There is a problem.”

Level 2: “There is a problem, and I’ve found some causes.”

Level 3: “Here’s the problem, here are some possible causes, and here are some possible solutions.”

Level 4: “Here’s the problem, here’s what I think caused it, here are some possible solutions, and here’s the one I think we should pick.”

Level 5: “I identified a problem, figured out what caused it, researched how to fix it, and I fixed it. Just wanted to keep you in the loop.”

Using this framework, here’s what I say to every new employee…

You will live at Level 4 from Day 1 and as we build trust you will rise to Level 5.

Being high agency doesn’t just mean tackling problems in this way. It means your entire way of working should be oriented to being a Level 4+ employee.

Plz feel free to steal it as well.

And ty @stephsmithio for the framework!

[juliettech @_juliettech]

@justinstorre @frantzfries

[juliettech @_juliettech]

I love that my mom’s fav new phrase is: “but, what did Claude say?”

[juliettech @_juliettech]

tsa precheck is so good I regret getting it bc I feel like I sold my soul

[juliettech @_juliettech]

@justinstorre Lol said no one ever

[juliettech @_juliettech]

@justinstorre @h2shami I’ll apply just to work with @h2shami

[juliettech @_juliettech]

yes, you need your own custom domain

[Connor Loi @connortbot]

I joined Y Combinator with 14 users, building a dev tool for myself.

Then @SaaiArora joined as CTO, and we started growing and shipping 2x faster. It forced us to rebuild product and infra from the ground up for teams, not solo devs.

We are ending the batch with >300k agent minutes per week, and teams like @mintlify, @knowunity, and @modaflows shipping through Replicas every day.

Today we're launching Replicas V2.

[juliettech @_juliettech]

I'd love to be able to save pinned answers directly from a @claudeai conversation to go back to them quicker in the future.

I'm surprised that's not yet a feature.