No engineering team? Ship anyway.
How an ops person ends up building the tools the whole team runs on.
I started out wrenching on bikes. Now I run operations for five hubs across three metros — and I build the apps my team runs on every day. No engineering team, no CS degree. Just a decade of knowing exactly how the work should flow.
I started on the shop floor at fifteen. I learned how the work actually flows — the parts, the people, the 10mm wrench nobody can find. Now I build the tools that make it flow better.
I'm Frenk — 29, born and raised in North Hollywood, the son of Guatemalan and Salvadoran immigrants and a first-gen Latino kid from the Valley. I've been riding since I was 14, and at 15 I became the grom at a small neighborhood bike shop. From there I worked my way up to running an entire shop. At 18 I decided wrenching wasn't a summer job, it was my career — and I've never looked back.
In 2023 I joined Ridepanda as its first mechanic and the fourth person on the Operations team. Six promotions later, I run day-to-day operations for five hubs across San Francisco, Palo Alto, Seattle, and the DMV. I lead Hub Managers and Service Leads, own hiring and development for every hub teammate, and launch new hubs from location search to go-live.
Along the way I grew a delivery operation from me driving bikes around in my Prius to a six-van fleet across three cities. And when the tools we needed didn't exist, I built them — work orders, warranty tracking, career ladders, compensation planning. Those apps run real parts of the business today.
Off the clock I'm a pretty disciplined guy with a lot of hobbies: chess, cycling, hot yoga, and stretching a borderline unreasonable amount. I truly believe in saunas and sensory deprivation tanks. I'll watch any horror movie you put in front of me, and most of my soundtrack is improvisational jazz or reggaeton.
Tap any card to try a working demo. Every name and number in them is made up — the real tools stay internal for security reasons.
Spot the spreadsheet, gap, or manual process quietly slowing the team down.
Sit with the people doing the work and map how it actually happens, not how the doc says it does.
Build it, click every button, break it on purpose, and push back until it feels right.
Put it live on its own domain, train the team, and keep iterating on what they tell me.
Hello —
I'm an operator who loves the unglamorous stuff: the schedule that finally works, the inventory count that's actually right, the new hire who feels ready on day three instead of day thirty. I came up through bike shops, so I learned early that people remember how you made things easy for them.
At Ridepanda I've done almost every job in operations — mechanic, lead tech, hub manager, back of house lead — and now I run the whole thing across five hubs. Whenever I've hit a wall, I've built my way through it. That's how a team of bike mechanics ended up running on software I made.
If you need someone who can lead a team, fix the process, and build the tool that keeps it fixed — I'd love to talk.
— Frenk

| Frame | 2024 ENVE Melee |
| Wheels | ENVE SES 4.5, tubeless |
| Chain | Waxed, always |
| Shoes | Lake, Speedplay cleats |
| Head unit | Wahoo Roam |
| Crew | Rapha RCC · City Boyz |
Strava (my most-used app, no contest), good tools, well-run spaces, and building things that make other people's days easier.

My dog, my co-pilot, and the toughest critic of everything I build. Tongue out, always. Tap the photo for more Beanie.
Mostly bikes, mostly early mornings. Tap to look closer.
Improvised jazz and live sessions up top, reggaeton below. Tap any track, or hit shuffle.
Pick an album and it'll play right here.
How an ops person ends up building the tools the whole team runs on.
What the data said about intake, and why it changed how we staff.
On designing internal tools people actually like opening.