First and most key: we want people to succeed here. That means we act like it, starting with the interview. We don't play games – we interview for strengths rather than the absence of weaknesses. aka "nobody will beat you up about things you're not great at."
If you're working more than 40 hours it's a rarity and we should do something about it. We're fixing AWS bills, not SOME NONSENSE HERE. You aren't your job.
Most of us are parents ourselves; absolutely nothing we do here is more important than our lives.
Your manager will be @jesse_derose. He's new at it (internal promotion), and he's awesome. That said, management is its own skill: we're providing him professional coaching to set him up for success rather than playing HackerNews First Principles with people's careers.
We're a distributed company. There isn't an office for you to sit in. @mike_julian and I are in different cities; there's no "core group" in one place, then a bunch of folks who miss out on decision making scattered around.
Speaking of my business partner, Mike and I are the sole investors. The only goals we're pursuing are our own; we don't need to make a 100x return for anyone, and instead of "runway" we're consistently profitable and have been so for years.
The 401(k) match (6%) vests immediately because we aren't interested in fucking with you, or keeping you around when you don't want to be here.
We're a young company. We don't always get it right. Our hearts are in the right place, we *listen* to our team, and we build the culture we want to have here. You'll have input to that.
We have no on call rotation because we have no public infrastructure. Sleep soundly; the @awscloud bill is very much a business hours problem.
Contrary to myth, @awscloud actually likes us quite a bit. A lot of our consulting engagements are helping clients negotiate contracts. Despite what you may think, there's very little "pound the table" and quite a bit of "let's make sure we're asking for the right things."
If this sounds like you, we should chat. duckbillgroup.com/careers/#open-… lists the roles; I will now field questions in this thread should you have any.
Profit sharing: we don't have anything formal at the moment, but we do annual bonus tied to profit. We're looking at making that more formal and transparent.
Equity: Our current corporate structure makes this incredibly difficult, plus equity is worthless if we don't sell (which we have no intention of doing). This is the last job @mike_julian and I will have. Services companies don't have fabulous exits...
Same as we do every day: unlimited sick leave (including mental health days), as well as incredibly flexible schedules. Our team owns their own availability. If someone is having a rough week despite the workload being half what it was last week? Okay.
Hey @jesse_derose we should do a Twitter Spaces about what it means to be a Cloud Economist.
After all...
I am the very model of a modern Cloud Economist
I’ve seen pricing stored in CSV, Parquet and in a JSON list
I’ve walked the booths of re:Invent, and I know services historical
From SQS to EKS, RDS including Oracle
I'm very well acquainted, too, with matters more contractual,
Both PPAs and EDPs, multi-cloud and all-in fanatical
About data transfer pricing I'm spitting figures fast and furious,
Hmmm... furious... furious... Aha!
While cross-AZ is bad enough, managed NAT Gateways are usurious
In order to help hire some of you (sales and cloud economics roles currently open!), it's me: the Worst Employee as imagined by your company's HR department and resulting policies. duckbillgroup.com/careers/#open-…
I'm just the right blend of malicious idiot that I should be walked out as soon as I resign; I clearly didn't think to steal any company data BEFORE I resigned.
I'm simultaneously trusted with root in production and not $20 of company money.
Hello, and welcome to our company's oh-so-very-shitty Security Awareness Training. I'm Chief Cloud Economist Corey Quinn of the Duckbill Group, and I'll be delivering this training for you because I was absolutely NOT the lowest bidder for a change.
The whole point of security awareness is to protect company information. That's what they say, anyway. Here in reality we're going to reference back to the things I spew at you rapid fire and blame you for our institutional shortcomings once we get breached.
Confidentiality is important. Assume that people will read what you write. I know, it's a heavy lift for some of you who haven't figured out that the failure mode of "clever on Twitter" is "being a huge asshole," but pretend it'll be read.