As a team, we believe in transparency, ownership, and clear expectations. In that spirit, keep on reading to learn more about what we value, how we work, and what to expect during the engineering interview process.
Each engineer can expect to be in less than six hours of meetings during a typical two-week sprint:
While we use calendar tools to automatically create large blocks of focus time throughout the week, we also encourage engineers to block off their best focus time. You know if you're a morning person or a night owl, and we want you to be set up for success.
We're a digital-first company, but happily headquartered in New York City. This means remote work is the primary experience for all Cubers (a.k.a. what we call ourselves), but everyone has a home whenever they're in NYC.
We embrace a high level of ownership. This means the team works together to decide on solutions instead of taking orders from management. We leave our egos at the door and respect everybody's experience.
We encourage Request For Comment (RFC) documents for larger changes to our codebase, which allows everyone on the team, regardless of experience or tenure, to suggest improvements to how we build.
We value thorough documentation both within our codebase (through standardized doc-string comments) and alongside it (with Confluence write-ups to explain core functionality and architecture decisions).
Quality leads to stable releases, happy customers, and easy refactoring. We maintain 90%+ code coverage on average across our repos, and we're striving for even more.
Cube is a remote-first company and our engineers live all over the US and Canada. We emphasize clear, written communication to keep everyone aligned.
Our CEO & Co-Founder Christina recently reaffirmed our commitment to a digital-first culture in The New York Times. Read more here.
We have "Flex Days" built in throughout the year that everyone at Cube takes off to enjoy a long weekend. We use this as an opportunity to recharge and celebrate all the hard work that we do.
Nicely done! Your information caught our eye. To start, you'll chat with our friendly recruiting team for 20-30 minutes so you can learn more about Cube (and so we can learn more about you).
Next up is a quick 45-minute chat with your potential manager. You'll get to learn more about them, the team, our culture, and the exciting technical projects you’d be working on.
No tricks, algorithms, or deadlines here. Work on a problem relevant to Cube’s tech (we'll use your code in the next step). Time to show off what you can do!
The final step! Here you'll code review your challenge response with your future peers and learn more about what it's like to work at Cube.
Welcome to the team and congratulations! Now that you're officially a Cuber, our recruiting team will get you all set up and ready for your first day.
“Our engineering teams are built on collective ownership, individual expression, and mutual support.
“I believe in the product and love working with my teammates. If we do our jobs well, we help our users do their jobs well.
“There are plenty of opportunities to propose solutions to technical problems. Nothing is too big, wild, or off-limits.
Hire smart people, provide high-level direction, then stay out of the way.
This is the foundation to my management philosophy and one of the reasons I enjoy startups. It provides the opportunity to find smart people, give them a common goal, and then stand back, help where needed, and watch it unfold. As a manager, I see one of my main jobs as shielding the team from various distractions and roadblocks, and clearing a path for the team to get the important work done.
Unsure whether Cube might be a fit for you? Have a read through my operating manual first. If you're still unsure, click the button below to ask me any question you'd like.
Send Josh a question
Thanks for taking the time to learn more about what we're building at Cube.