How much of your team's efforts are devoted to features, developer experience, scaling infrastructure, and all the other things involved in writing code for a company like Pusher?
How do those responsible for scaling the infrastructure think about the end-user experience?
I've built and managed Engineering teams at companies large and small. Currently @ Pusher growing a team who build the world's best realtime web messaging platform.
We actually spend most of our engineering capacity on innovation at the moment, which is great. The core Pusher product is scalable and maintainable without constant firefighting, and we want to keep it that way! So it's less than 10% on that, with most people working on our newer products like Chatkit.
All our engineers spend time on support so they get a good idea of how our customers use our product, and our sales team are really great at publicly highlighting customer use cases.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How much of your team's efforts are devoted to features, developer experience, scaling infrastructure, and all the other things involved in writing code for a company like Pusher?
How do those responsible for scaling the infrastructure think about the end-user experience?
We actually spend most of our engineering capacity on innovation at the moment, which is great. The core Pusher product is scalable and maintainable without constant firefighting, and we want to keep it that way! So it's less than 10% on that, with most people working on our newer products like Chatkit.
All our engineers spend time on support so they get a good idea of how our customers use our product, and our sales team are really great at publicly highlighting customer use cases.