We're looking for our first engineers: flexible, full-stack folks with a passion for front-end, a desire to collaborate, and a comfort with ambiguity.
Miter is an early-stage startup committed to eliminating bad, wasteful meetings—without making people write agendas. (And yes, this job description is our entire careers page. Did we mention we're early-stage?)
This isn't our first rodeo. Dave Feldman (CEO) has led design teams at Google, Facebook, and Yahoo; he built the design practice at Heap from zero. In 2012 he co-founded Emu Messenger, acquired by Google in 2014. He's a pragmatic designer with a passion for behavioral science. He's also a bit of a unicorn, with experience in product and engineering.
Damian Wisniewski (COO) is a veteran of LinkedIn who's made a career of building sales teams at B2B startups of varying sizes including GoodHire, CleverTap, and Got It. He holds an MBA from MIT Sloan and a Mathematics degree from Harvard. Damian is not afraid of SQL. (Dave may or may not be afraid of SQL.)
We've founded Miter to create a product, but also to build a company where people love to work. As a super-early colleague you'd be a key part of that, ensuring that as we grow we live up to our values:
We probably don't need to convince you that a lot of meetings are a waste. And it's an expensive waste: we spend over $1.5 trillion a year on meetings in the US alone. A twenty-person weekly status meeting (and c'mon, at that size there's no way it's productive) costs $67,000 a year.
We can solve this. But we're not going to solve it by defragging our calendars, or writing more agendas. We can't just get rid of meetings—they're a cornerstone of effective collaboration. But we can make them work better. And better meetings means fewer meetings, shorter meetings, better decisions, happier teams, and more actual work getting done.
Miter's platform starts with the purpose of the meeting, then gives meeting leaders the tools they need to reach their goals.
You're excited by our vision, eager to contribute to it, and energized by our ambiguity. You're ready to write a lot of code, and comfortable throwing a lot of that out as we test and iterate, especially since you'll be an integral part of driving that iteration. You're happy working in an unstructured environment, and eager to create the structure it lacks.
"Founding engineer" is a fuzzy term, and for us it covers a range. If your aspirations are to become VP Engineering or a CTO, we'd like to help you get there. If you'd rather be heads-down building product for the foreseeable future, great. But either way, the latter will be your focus in the near term. Skill-wise, here's what we're looking for: