We are a technology services partner for digital innovation and business transformation.
We combine our global experience in key industries and the latest technologies to help fast-growing and established companies transform and accelerate their business models, develop innovative digital solutions, scale technology capabilities, and sustain their growth.
We are change-makers, and the purpose of everything we do is to connect people and technology to build a better future together.
Our approval ratings on Glassdoor and the awards we've received from Great Place To Work since 2008 prove that we encourage work-life balance in a transparent and flexible environment, ensuring a unique experience for e-Coreans to be their best version.
Customer support at Trello is different.
To start with, we let our customers decide if they want to pay us or not. Seriously. If our customers are not amazingly happy, they get their money back with no questions asked. Our front line staff is empowered to make our customers happy. Usually, it means tapping a broad range of resources, whether that’s making sure you have all the right software or working directly with an engineer to troubleshoot a case. You’ll have what you need to get the job done.
You will not be glued to the queue. Sure, we need to get back to customers via email—that will always be there—but support is so much more than grinding through an inbox. This is a real problem-solving job. You’ll have an incredible amount of autonomy in determining how best to contribute your talents and skills to Trello. Think a short video will help customers get started? Make it. Want to write a script to help a customer with the API? Go for it. There’s plenty of room for creativity and technical exploration when it comes to better serving our customers.
The other side of support is working with the other teams at Trello. All of our teams—engineering, marketing, sales, etc—benefit from support's role in working directly with customers. It will be your job to determine how we can serve them as effectively as possible. This is no small task, especially when communication is happening asynchronously across time zones. For example, when working with the engineering team, you need to know when a bug can stay under the radar versus when you should sound the alarm.