During interviews, candidates often ask what working as an engineer at Cinder is like. They aren’t asking about our tech stack, which everyone can read about on our jobs page (we’re hiring!) or even how much fun we have - anyone who’s looked at our LinkedIn page can see that we’re a team that enjoys in-person and virtual hangouts. They really want to understand the foundation of our team culture. What sorts of people do we hire, and what kind of team are we building?
We put our company values – being empathetic, relentless, and intentional – into everything we do. But values without action mean nothing. To describe our team in more concrete terms, we look for the behaviors that support those values.
During our recent company onsite in Nantucket, we had a full-company brainstorming session during which we white boarded specific behaviors that we value in our teammates. We drew direct links between those behaviors and the values of our company. We narrowed them down to a select few, and we’re listing them here.
As a reminder, if these behaviors describe you, head over to our jobs page and consider joining our team.
We adapt, act fast, learn, and always keep evolving in order to achieve our mission and be one step ahead of the challenges facing our customers.
We’re focused on our mission and it drives everything we do.
We work to understand the problems of everyone we come into contact with, whether our own team, our customers, or others in the industry.
This is just a start. I’m sure we’ll continue to revisit this list, adding and revising as we learn more about which behaviors contribute to better outcomes for Cinder and our customers. But, I believe it’s important to begin codifying them now. Values and mission statements are great to rally around, but behaviors are what create the right culture and ultimately help push us to delivering what is best for our customers. Articulating behaviors helps hold us accountable to ourselves and to Cinder’s larger mission.
Organizations often start with simple Trust & Safety issues may use basic tools, but as needs grow, they face the build vs. buy dilemma. In this blog, we look at the complexity, costs, and benefits of both options.