👉 Hiring remotely?
Backend Python Engineer
Backend Python Engineer
Stats (beta): 👁 6,072 views,✍️ 0 applied (0%)
\nYou probably haven’t run into a company like Olark before. \n\nWe are 35 people distributed around the globe. We care deeply about customer service, which means everyone on the team spends time talking directly to our customers. We call this All Hands Support. It’s a unique way to make sure we all remember why we are building our product. We focused on our customers and now help over 10,000 of them provide amazing service. \n\nThis is a unique point in our company history. We just crossed the 30 employee mark this year, and you will play a pivotal role in helping define our engineering culture, and help us fulfill an important part of our mission, to build a positive organization.\n\nYour primary responsibility will be to join the team that builds applications, systems, and infrastructure. You’ll be helping scale Olark to help 100,000s of people better serve their customers. \n\n\nYou will help us solve key engineering challenges:\n\n\n* How do we ensure real time message delivery to hundreds of thousands of concurrent visitors on tens of thousands of websites?\n\n* How do we design a robust integrations API that makes it easy for other developers to integrate with Olark without increasing our support cost?\n\n* How do we maintain real time state across mobile, desktop, and web?\n\n* How do we reliably store terabytes of transcripts and customer interactions?\n\n* How do we act on the vast quantities of data available to us, to make our users the most informed and capable chat agents on the internet?\n\n\n\n\n\nYou bring a lot to the table:\n\nYou:\n\n\n* Work well as part of a distributed team. You are comfortable working outside of a typical office. You are happy to work independently, but know when to ask for help. You know how to give, and receive, direct feedback. You are a team player, and comfortable leading and contributing to projects.\n\n* Great communication skills. You are comfortable giving technical talks and mentoring other engineers. You are able to clearly communicate your thoughts in writing. You realize listening is just as important as speaking your mind. You know when a conversation should be in chat, skype, or face-to-face.\n\n* Curious. You are comfortable with ambiguity, and like to figure out how things work or what to do next.\n\n* US Time Zone. You are willing to work in US time zone hours.\n\n\n\n\nYour technical background and experience:\n\n\n* Very familiar with web technologies and patterns for scaling software like message queues, caching, and load balancing. \n\n* Meticulous attention to detail. You should be able to review code written by other engineers and find room for improvement. You should be able to write test suites for your code that exercise complicated code paths and prevent production mishaps. Every time we push out new code is an opportunity to delight thousands of customers (or a risk of making a bad day for those people).\n\n* Strong understanding of network programming, and operating system fundamentals. You’ve used command line tools to debug networking issues, know the difference between processes and threads, and understand the challenges of building software in the cloud.\n\n* Write good code. You should have examples of code you have written that is easy to read, maintainable, and testable. You should be able to decompose complicated problems into elegant solutions anyone on the engineering team can understand. \n\n* Always learning. This is a Python position, but you don’t need to have a ton of production Python experience. You are excited to learn our tech stack, and to help lead it forward. You’re comfortable making the right call when it comes to choosing between new technologies and tried and true standbys.\n\n* Significant production experience. You have 2+ years of experience shipping and maintaining production code that is used by 1000s of people. You have run into the edge cases of operating at scale, and can teach us how to avoid them.\n\n\n\n\n\nYou can expect a lot from us:\n\nFirst off, make sure to read about our team culture at olark.com/jobs, and our values at olark.com/values. You can also get a sense of our history at olark.com/10000. \n\nBeyond what you see there, as a member of your engineering team you can expect:\n\n\n* A great remote culture: much of our collaboration takes place via Hipchat, Github and Skype. That said, we’re happy to facilitate in-person meetups too -- in addition to our annual company retreat.\n\n* A life outside of work: Olarkers generally work 40 hour weeks, work is a marathon, not a sprint. We are building a company for the long haul. \n\n* Work within a large Service Oriented Architecture built on Python, Twisted, Thrift, and RabbitMQ. There’s MySQL, Redis, Elasticsearch, NodeJS, Rails and Ejabberd as well (bonus points if you're already familiar with these technologies!)\n\n* Quality-driven culture: we strive to automate testing and heavily monitor our production system. Our goal is ensuring that any end-user issues are short-lived and limited in scope.\n\n* One weekly required engineering meeting and team wide sync - we also only allow meetings on Monday and Wednesday to keep ourselves focused.\n\n* Great compensation and benefits: competitive pay, phone/internet stipend, health benefits, $1K vacation bonus for the first week you take off a year, 401k, charitable donation matching, coworking space if you are remote.\n\n\n\n\n\nOlark is committed to diversity in its workforce. Olark is an equal employment opportunity employer and considers qualified applicants without regard to gender, sexual orientation, gender identity, race, veteran or disability status.
See more jobs at Olark
# How do you apply? This job post is older than 30 days and the position is probably filled. Try applying to jobs posted recently instead.Apply for this Job
👉 Please reference you found the job on Remote OK, this helps us get more companies to post here!