
founding engineer + talent @getserval
Burlingame, CA
Joined September 2015
- Tweets24
- Following71
- Followers109
- Likes72
Kaz Hishida retweeted
Starting today, every engineer who joins Serval begins with a weeklong, $10,000 paid vacation. We’re building the next generational company. We need generational talent to see it through.
Our mission has always been to empower people across every team to turn their understanding of a problem into working, trustworthy automations. Making that function inside the largest enterprises takes world-class engineering.
That’s what you’d be joining us to do. There are foundational decisions still to make, and the engineers making them will shape the future of how big we can build this company.
We want you to arrive rested and ready to do the best work of your life. So your first week is a chance to get away.
And if a @getserval employee refers you, both you and that employee receive $30,000, on top of the vacation.
Come build with us: serval.com/careers
Kaz Hishida retweeted
I was on @CNBC Squawk Box with one of our customers, @JackGretz, the CEO of @SeatGeek to talk about how they used Serval to eliminate the ticket backlog and redeploy their engineers as embedded business partners.
⚡ 50% of IT requests automated in first 60 days
⚡ 132 automations built in 8 weeks
⚡ Zero layoffs. Hiring this year already ahead of all of last year
⚡ IT time redeployed to solve harder problems
When you automate the low-hanging tasks, the support requests and the password resets, you can take the most technical people in your organization and deploy them into work that's more productive than what they were doing before.
Full clip below. 👇 @getserval
Kaz Hishida retweeted
Jake Stauch joined @SquawkCNBC this morning with @SeatGeek CEO Jack Groetzinger.
With Serval, SeatGeek went from 0% to 50%+ of IT requests automated in 60 days, built 132 automations in the first eight weeks, and embedded their engineers into business units as FDEs.
Software is mostly just workflows on top of a database. This hasn't changed. What's changed is how those workflows are built. @jakeserval and @getserval saw the world changing and nailed it.







