👉 Hiring for a remote position?on the 🏆 #1 remote jobs board
This job post is closed and the position is probably filled. Please do not apply.
At GrapheneDB we proudly manage thousands of Neo4j databases, catering individual developers working on pet projects to large companies with challenging workloads and reliability requirements.\n\nWe're growing our team and looking for a site reliability engineer to join our team. Our team is fully distributed and spread out all over the word. We value pragmatism, accountability, early feedback and helping others. We write and support our own production code. This means that DevOps is a real thing for us. In short: we are team players.\n\n## What You'll Be Doing\n\n* Report and solve problems within the GrapheneDB infrastructure.\n* Participate in SRE software engineering, writing code for the continuing reduction of human intervention in operational tasks and automation of processes.\n* Monitor the GrapheneDB infrastructure, responding to incidents, correcting and improving systems to prevent incidents and planning capacity.\n* Manage infrastructure, system deployments and product releases.\n* Implement and enforce security best practices at scale.\n* Write specifications for secure, robust, resilient and observable services, both centralized and distributed.\n* You will participate in 24x365 on-call schedules.\n\n## Experience:\n\nYou'll bring into our team some nice skills:\n\n* Experience as a Linux systems engineer/administrator in the Amazon Cloud (AWS).\n* Experience deploying, managing and monitoring Docker containers at scale. We don't plan to use Kubernetes in the near future, but CoreOS seems tempting.\n* Relentless desire to automate and build tools to achieve it. We use Python/Ruby for scripting. Go is our choice for small, efficient networking tools, whereas Rust is a safer choice for our core services. You don't have to be proficient in all of them.\n* Ability to troubleshoot problems using high and low level debugging tools and techniques throughout all our stack.\n* Familiarity with "infrastructure-as-code" tools: eg. Ansible and Terraform.\n* A passion for security, observability and monitoring.\n\n### Non-essential, but desirable:\n\n* You have monitored and tuned the Java Virtual Machine to ensure apps run smoothly.\n* You have managed any combination of these: MongoDB, Kafka, ElasticSearch.\n* Familiarity with NGiNX\n* AWS Lambda Functions and Elastic Container Service.\n\n### Soft skills\n\n* You enjoy working remotely and the (over)communication it requires.\n* You have worked with Git, Github, Gitflow and are familiar with code reviews.\n* You lead a healthy lifestyle and enjoy your time outside work.\n\n\n## What we offer\n\n* A fair transparent salary (depending on location and experience).\n* 100% remote work.\n* Numerous planned company events throughout the year.\n* Flexible working hours and a generous vacation policy.\n* Global minimum of 16 weeks of paid in full parental leave (moms & dads)\n* Budget for personal development: books, training, conferences, etc.\n\n## Application Process\n\n* You submit your application via our online form.\n* We review applicants, screening for a variety of criteria.\n* If you pass the screening, we will ask you to complete a small coding test.\n* We will review code test submissions and conduct calls to interview candidates based on their solutions.\n* We will make an offer to the candidate we think is the best fit.\n\nGrapheneDB is committed to the principles of equal employment opportunity and affirmative action for all applicants and employees. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender perception or identity, national origin, age, marital status, protected veteran status, or disability status or any other basis protected by federal, state or local law, ordinance or regulation.
See more jobs at GrapheneDB
# 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.