[Spam check] What is the name of Elon Musk's company going to Mars?
👉 Hiring for a Remote position?on the 🏆 #1 Remote Jobs board
Remote Health by SafetyWing
Global health insurance for freelancers & remote workers
Site Reliability Engineerclosed
This job post is closed and the position is probably filled. Please do not apply.
\nRide team @Heetch\n\nThe mission of the Ride team is quite simple: make passengers and drivers meet, and get where they need to be.\n\n“Transportation is serious business” — Jason Statham as Frank Martin\n\nOur team is responsible for providing the best ride experience, by building both the smoothest ordering experience and the platform and algorithms responsible for real-time execution and online optimization of Heetch's marketplace across all our markets(matching, dynamic pricing, ETA, heatmaps). We have high standards and high expectations on our output, we ship fast, and we scale our work for all markets. To achieve this, we’re all working together among Product, Mobile & Backend Devs, Design, Data Analysts & Scientists, and Ops team to successfully target structural next steps, deliver, track and iterate.\n\n\nSRE within Ride \nOur infrastructure handles 2.5 millions of events per day and processes 100M of API requests. We also serve over a dozen thousand rides and process hundreds of gigabytes of log and interaction data daily. Our team owns more than 50 microservices on top of Golang, Kafka and Docker.\n\n To put it simply; Our impact on the business and the experience of both passengers and drivers is unprecedented. Every ride should be reliable, efficient, and affordable, and we're building the algorithms that make that possible by optimizing supply and demand.\n\n\nHow do we work ? \nMindset\n\n• Move fast not furious. \n• Don’t be scared of failure, learn from it and try again. \n• Unit and functional tests are as important as code. \n• Code is always evolving we don't think in versions. \n• We’re not just here to push code; product ownerships equally spread among the team.\n\nTech Stack \n• Microservices. \n• Docker with Mesos & Marathon. \n• We ship new services on a weekly basis (at least we try to ). \n• Services owned by our teams are written in Go. \n• We follow community guidelines and standard methodologies. \n• Kafka.\n\n\nTeam Life \n• Work wherever you want: we’ve always been remote first but also have a shiny new office in Paris, London, Milan, Bruxelles, and Casablanca. \n• Open communication: everything is public within the team. \n• You are not alone: we use Slack, and video calls every day. \n• Continuous improvement: weekly team retrospective and strong Speak Up value. \n\n\n\nYour role \n\nIn this role, you'll be in charge of building the tools and systems that every backend engineer in the Ride team uses to develop, scale, understand, and monitor their operations. \n\nYou will dive deep into gnarly operational issues; from the software, systems, automation, and process perspectives, and, you will work with our production services throughout their entire life cycle, from design and architecture, through implementation, deployment, and sustaining operations. \n\nWhat will you do? \n\n• Build tools and infrastructure to make the team iterate faster without overthinking about the core infrastructure. \n• Partner with fellow backend engineers to architect and develop mission-critical systems that can stand the test of scale and availability, while limiting operational overhead. \n• Perform deep dives into both systemic and latent reliability issues; partner with software and SRE engineers across the organization to produce and roll out fixes. \n• Design, build & support systems to detect, alert and remediate or escalate on the team' platform. \n• Contribute to standardization efforts across multiple disciplines and services in conjunction with the Core SRE team. \n• Handle efficiencies in systems and processes: design, configuration management, performance tuning, monitoring, and root cause analysis. \n• Participate in an on-call rotation and contribute to needed escalation missions. \n\nWhat do you need? \n\n• Software Engineer background (+5 years). \n• Practical knowledge of various aspects of service design like messaging protocols & behavior, caching strategies and software design practices. \n• Solid understanding of systems and application design, including the operational trade-offs of various designs. \n• Excellent programming skills in Go, and an ability to pick up new programming languages. \n• Excellent written and social communication, and documentation skills in English. \n• Be adaptable and able to focus on the most straightforward, most efficient & reliable solutions. \n• Experience in the Linux environment and a deep understanding of its fundamentals and internals: filesystems and modern memory management, threads and processes, the user/kernel-space divide, networking. \n• Exposure to the AWS ecosystem. \n• Real world experience with Packer/Terraform. \n• Customer service skills and empathy to develop solutions that span multiple teams. \n• Work well with and be able to influence a myriad of personalities at all levels.\n\n Bonus \n• Experience building highly-available fault-tolerant distributed systems with microservices, including containerized architectures, application security, monitoring, and storage systems. \n• Experience with message brokers (such as RabbitMQ or Kafka). \n\nPerks \n\n• Stocks. \n• Paid conference attendance/travel. \n• Heetch credits. \n• A Spotify subscription. \n• Code retreats and company retreats. \n• Travel budget (visit your remote co-workers and our offices).
See more jobs at Heetch
# How do you apply?\n\n This job post is older than 30 days and the position is probably filled. Try applying to jobs posted recently instead.