- Ruby on Rails Engineer / Architect: you've worked before on an at-scale Rails app and love making it easier for our customers to use our app and make it easier for your fellow developers to contribute improvements.
- Graphic Designer: you'd like to apply your understanding of both functionality and aesthetic to improve our website and chat window.
- Marketing Communications: you'll help us educate the world about how the meaning of customer service is changing
### What's our culture like?
- Our all-hands retreat in August combined team outings (winery tours / biking / canoeing) with talking about the future of interacting with customers and how we were going to change it.
- Engaging with our customers! At conferences, answering e-mailed questions, and (of course) chatting with them on Olark. Interacting with our customers has repeatedly gave us insights that couldn't have come from simply writing code.
- We have project-based teams that shift (roughly) quarterly. We want to give our teams enough time to make sizable changes, but experience has taught us that iterations need an end date so we can collect feedback from real-world usage.
### Who is Olark?
Simply, we're the people that put live chat on thousands of websites across the Internet.
More than that, we're helping businesses scale their personal touch to the Internet, as the lines between customer discovery, sales, and support blur.
### Who are we looking for? (details on http://www.olark.com/jobs)
- Ruby on Rails Engineer / Architect: you've worked before on an at-scale Rails app and love making it easier for our customers to use our app and make it easier for your fellow developers to contribute improvements.
- Graphic Designer: you'd like to apply your understanding of both functionality and aesthetic to improve our website and chat window.
- Marketing Communications: you'll help us educate the world about how the meaning of customer service is changing
### What's our culture like?
- Our all-hands retreat in August combined team outings (winery tours / biking / canoeing) with talking about the future of interacting with customers and how we were going to change it.
- Engaging with our customers! At conferences, answering e-mailed questions, and (of course) chatting with them on Olark. Interacting with our customers has repeatedly gave us insights that couldn't have come from simply writing code.
- We have project-based teams that shift (roughly) quarterly. We want to give our teams enough time to make sizable changes, but experience has taught us that iterations need an end date so we can collect feedback from real-world usage.
### How to apply
For more details and to contact us, check out http://www.olark.com/jobs