Windmill Engineering is building the platform for cloud-native development. Imagine if every time you hit save, you could kick off workflows that run in the cloud, with results that are accessible across your team instantly and historically. How much more productive could you be with faster workflows? What workflows have we not even thought of yet?
This is a big mission, and we’re a small team (6 people, based in NYC’s Union Square).
We’re software engineers and toolsmiths. We’ve built developer tools and consumer products. Nick and Dan (founders) met working at Google on projects like Google Sheets, Google Code, and others. We think cloud-native products like GitHub and Google Sheets are great because of the new workflows they enable. We’re excited to be working towards it.
We want to be a better company in an industry that’s been neither diverse nor inclusive. Each month, we give $100/employee to an org that’s making tech less toxic. We recognize “meritocracy” and “work hard, play hard” as culture smells.
Our First Product
Tilt relieves the pains of local Kubernetes microservice development. It already automates and optimizes container image builds, and has a Heads-Up Display UI that saves you from having to play 20 questions with kubectl. But which pains do we relieve next? What features relieve them fastest or best?
We need a Frontend Engineer to help build prototypes and features to answer that question.
What You’ll Do
Write React components in Typescript
Design and evolve component libraries that help us iterate on product quickly
Build user interfaces that help engineers work with their local Kubernetes dev environment
Attend to our UI performance, accessibility, responsiveness, and compatibility to reach more users
Talk to external teams about the pain points of local Kubernetes dev. What new information could they see to get them unstuck? Which new affordances would they need to be more productive?
Prototype cloud-native dev features that we haven’t even thought of yet. How can we make your data available to your team, and make your team’s data available to you?
Help us build a team culture where everyone’s doing their best work
Ideal, but not Required
Lives in New York City, or would be willing to relocate.
(It would be hard to be the first remote engineer, but it might work if you had previous remote experience)
Familiar with Docker, containers, microservices, and Kubernetes. Can explain what problems they solve.
(We can teach you these tools to you if we need to, but it would be a shame to learn them only to find out that you hate them.)
Experience with Go
(Without at least some Go experience or a willingness to learn, you might have a hard time prototyping new features.)
Even if you don’t have experience or interest in every bullet, we want to hear from you. There’s no perfect candidate, and we want to find the right fit, even if it’s different than we imagine. We especially would like to meet underrepresented/underestimated candidates.