\nWe’re a highly skilled team of software engineers who are building an awesome product and moving fast. We value people who take initiatives, and empower everyone at Klue to make a real change in the product or processes. \n\n\nWe are looking for a Senior Backend Engineer to work with our Consumer team to deliver high-quality products in the most efficient way.\n\n\n💡FAQ \n\n\nQ: Klue who?\nA: We’re Klue and from a technical perspective, Klue’s mission is to descale huge amounts of data to the human level, so people can process it and make use of it. Klue is that trusted intermediary, right now it’s proven for sales enablement, but tomorrow it’s all teams enablement.\n\n\nQ: What level of experience are we looking for?\nA: Right now we are looking for a Senior-level Back-end Engineer. \n\n\nQ: What is our development team working on?\nA: As part of our backend team, we are concerned with data storage and retrieval and the infrastructure to enable that. Here’s what our development team is working on and the opportunity for motivated Software Engineers to dig into, alongside us:\n- Big Data - lots of data \n- Ingesting thousands of news articles, web pages, marketing and sales data points per day. The challenge is indexing them for a long period of time and making them searchable and ready for different analysis.\n- Expanding our Rails REST API and offering public APIs to enable integrations.\n- Architect infrastructure for a scalable, resilient and robust service. We are migrating from a monolith architecture to K8S-hosted microservices. \n\n\nQ: What tech stack is this team working with?\nA: Ruby (Rails), Python (Flask), PostgreSQL, Elasticsearch, Redis, GCP, AWS, Tensorflow, Keras, Docker, Kubernetes.\nWe code review all changes, continuously integrate, pay down technical debt, and aim for high automated test coverage. We love microservices and, while we mostly use Python, Ruby, Google Cloud Platform, Linux, JavaScript, and React, new services can be built using whatever tools make sense to get the job done and support our game-changing innovation.\n\n\nQ: Are you HYBRID FRIENDLY 🤩 ?\nA: YES! Hybrid. Best of both worlds (remote & in-office)\nOur main Canadian hubs are in Vancouver and Toronto, and most of our teams are located in EST and PST.\nYou and your team will be in office at least 2 days per week.\n\n\n\nQ: What skills do you bring? \n* Expertise in at least one of the general programming languages, with a strong preference for Ruby on Rails\n* Expertise in relational databases such as PostgreSQL or MySQL\n* Experience in designing REST APIs\n* Experience using NoSQL databases such as Elasticsearch or MongoDB is a plus\n* Experience using Docker, Kubernetes, AWS, GCP is a plus\n* Bonus if you have Data Engineering interest and experience; ETL Pipelines, Snowplow, Snowflake, Big Query Redshift, Airflow, or equivalent.\n\n\n\nQ: What motivates our current team right now?\n* The type of work. Challenging, stimulating and meaningful work. New and relevant tech stack. We know engineers/developers especially want to work on hard technical and innovative problems.\n* The inspiration from skilled and proven leaders.\n* Entrepreneurial fingerprints on what will be a future billion dollar company anchored in Canada.\n* Culture, team, and the work environment.\n* High degree of autonomy and accountability.\n* High degrees of transparency and high quality communication.\n\n\n\nQ: What are the people at Klue like?\n* Builders\n* Intellectually Curious\n* Ambitious\n* Objective Oriented\n* Check us out!\n\n\n\nQ: What about total compensation & benefits?\n* Benefits. We currently have extended health benefits starting on your 1st day.\n* Time off. Take what you need. We want the team to prioritize wellness and avoid burnout. Vacation usually falls into 3 categories: recharging, life-event, & keeping a work-life balance. Just ensure the required work gets done and clear it with your team in advance. You need to take at least two weeks off every year. The average Klue team member takes 2-4 weeks of PTO per year.\n\n\n\n\n$150,000 - $180,000 a yearWe gather compensation benchmarking data across the BC & Canadian Tech Industry and use that data to build a range for our current team and future talent.  Your exact salary is determined by experience level, skill, capabilities, whether or not you select options, and internal pay parity.\nIf you feel like this role is a great fit and have questions about comp, get in touch and we’re happy to discuss further. There is always an ongoing conversation around compensation.\n\n\n⬇️ ⬇️ ⬇️ ⬇️ ⬇️\n\n\n\n\n\n\n\n\nLastly, we take potential into consideration. An equivalent combination of education and experience may be accepted in lieu of the specifics listed above. If you know you have what it takes, even if that’s different from what we’ve described, be sure to explain why in your application. Reach out and let’s see if there is a home here for you now or in the future.\n\n\nWe’ve made a commitment to support and contribute to a diverse environment; on our teams and in our community. We’re early in our journey; we've started employee led resource groups, committed to Pay Up For Progress, and use success profiles for roles instead of 'years of experience'. We continue to scale our efforts as Klue grows. We’re proud to be an equal opportunity employer and have dedicated that commitment to our current and future #kluecrew. During the interview process, please let us know if there is anything we need to make more accessible or accommodate to support you to be successful.\n\n\nAll interviews will be conducted via video calls. We work in a hybrid model of WFH (remote) and in-office. We’re excited to meet you and in the meantime, get to know us:\n\n\n 🌈 Pay Up For Progress & 50 - 30 Challenge & Klue Blog\n✅✅ Win-Loss Acquisition (2023)\n🅰️ Series A (2020)\n🐅 Series B (2021)\n🏆 Culture, culture, culture! \n🎧 Winning as Women & Competitive Enablement Show\n🔍 Glassdoor\n🐝 About Us\n🐥 Twitter\n📸 Instagram\n☕️ LinkedIn\n🦄 Wellfound (AngelList)  \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Python, Video, Cloud, NoSQL, Ruby, API, Senior, Marketing, Sales, Engineer and Backend jobs that are similar:\n\n $60,000 — $110,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n

# We're building the Data Platform of the Future\nJoin us if you want to rethink the way organizations interact with data. We are a **developer-first company**, committed to building around open protocols and delivering the best experience possible for data consumers and publishers.\n\nSplitgraph is a **seed-stage, venture-funded startup hiring its initial team**. The two co-founders are looking to grow the team to five or six people. This is an opportunity to make a big impact on an agile team while working closely with the\nfounders.\n\nSplitgraph is a **remote-first organization**. The founders are based in the UK, and the company is incorporated in both USA and UK. Candidates are welcome to apply from any geography. We want to work with the most talented, thoughtful and productive engineers in the world.\n# Open Positions\n**Data Engineers welcome!** The job titles have "Software Engineer" in them, but at Splitgraph there's a lot of overlap \nbetween data and software engineering. We welcome candidates from all engineering backgrounds.\n\n[Senior Software Engineer - Backend (mainly Python)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Backend-2a2f9e278ba347069bf2566950857250)\n\n[Senior Software Engineer - Frontend (mainly TypeScript)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Frontend-6342cd76b0df483a9fd2ab6818070456)\n\n→ [**Apply to Job**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp) ← (same form for both positions)\n\n# What is Splitgraph?\n## **Open Source Toolkit**\n\n[Our open-source product, sgr,](https://www.github.com/splitgraph/splitgraph) is a tool for building, versioning and querying reproducible datasets. It's inspired by Docker and Git, so it feels familiar. And it's powered by PostgreSQL, so it works seamlessly with existing tools in the Postgres ecosystem. Use Splitgraph to package your data into self-contained\ndata images that you can share with other Splitgraph instances.\n\n## **Splitgraph Cloud**\n\nSplitgraph Cloud is a platform for data cataloging, integration and governance. The user can upload data, connect live databases, or "push" versioned snapshots to it. We give them a unified SQL interface to query that data, a catalog to discover and share it, and tools to build/push/pull it.\n\n# Learn More About Us\n\n- Listen to our interview on the [Software Engineering Daily podcast](https://softwareengineeringdaily.com/2020/11/06/splitgraph-data-catalog-and-proxy-with-miles-richardson/)\n\n- Watch our co-founder Artjoms present [Splitgraph at the Bay Area ClickHouse meetup](https://www.youtube.com/watch?v=44CDs7hJTho)\n\n- Read our HN/Reddit posts ([one](https://news.ycombinator.com/item?id=24233948) [two](https://news.ycombinator.com/item?id=23769420) [three](https://news.ycombinator.com/item?id=23627066) [four](https://old.reddit.com/r/datasets/comments/icty0r/we_made_40k_open_government_datasets_queryable/))\n\n- [Read our blog](https://www.splitgraph.com/blog)\n\n- Read the slides from our early (2018) presentations: ["Docker for Data"](https://www.slideshare.net/splitgraph/splitgraph-docker-for-data-119112722), [AHL Meetup](https://www.slideshare.net/splitgraph/splitgraph-ahl-talk)\n\n- [Follow us on Twitter](https://ww.twitter.com/splitgraph)\n\n- [Find us on GitHub](https://www.github.com/splitgraph)\n\n- [Chat with us in our community Discord](https://discord.gg/eFEFRKm)\n\n- Explore the [public data catalog](https://www.splitgraph.com/explore) where we index 40k+ datasets\n\n# How We Work: What's our stack look like?\n\nWe prioritize developer experience and productivity. We resent repetition and inefficiency, and we never hesitate to automate the things that cause us friction. Here's a sampling of the languages and tools we work with:\n\n- **[Python](https://www.python.org/) for the backend.** Our [core open source](https://www.github.com/splitgraph/splitgraph) tech is written in Python (with [a bit of C](https://github.com/splitgraph/Multicorn) to make it more interesting), as well as most of our backend code. The Python code powers everything from authentication routines to database migrations. We use the latest version and tools like [pytest](https://docs.pytest.org/en/stable/), [mypy](https://github.com/python/mypy) and [Poetry](https://python-poetry.org/) to help us write quality software.\n\n- **[TypeScript](https://www.typescriptlang.org/) for the web stack.** We use TypeScript throughout our web stack. On the frontend we use [React](https://reactjs.org/) with [next.js](https://nextjs.org/). For data fetching we use [apollo-client](https://www.apollographql.com/docs/react/) with fully-typed GraphQL queries auto-generated by [graphql-codegen](https://graphql-code-generator.com/) based on the schema that [Postgraphile](https://www.graphile.org/postgraphile) creates by introspecting the database.\n\n- [**PostgreSQL](https://www.postgresql.org/) for the database, because of course.** Splitgraph is a company built around Postgres, so of course we are going to use it for our own database. In fact, we actually have three databases. We have `auth-db` for storing sensitive data, `registry-db` which acts as a [Splitgraph peer](https://www.splitgraph.com/docs/publishing-data/push-data) so users can push Splitgraph images to it using [sgr](https://www.github.com/splitgraph/splitgraph), and `cloud-db` where we store the schemata that Postgraphile uses to autogenerate the GraphQL server.\n\n- [**PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) and [PL/Python](https://www.postgresql.org/docs/current/plpython.html) for stored procedures.** We define a lot of core business logic directly in the database as stored procedures, which are ultimately [exposed by Postgraphile as GraphQL endpoints](https://www.graphile.org/postgraphile/functions/). We find this to be a surprisingly productive way of developing, as it eliminates the need for manually maintaining an API layer between data and code. It presents challenges for testing and maintainability, but we've built tools to help with database migrations and rollbacks, and an end-to-end testing framework that exercises the database routines.\n\n- [**PostgREST](https://postgrest.org/en/v7.0.0/) for auto-generating a REST API for every repository.** We use this excellent library (written in [Haskell](https://www.haskell.org/)) to expose an [OpenAPI](https://github.com/OAI/OpenAPI-Specification)-compatible REST API for every repository on Splitgraph ([example](http://splitgraph.com/mildbyte/complex_dataset/latest/-/api-schema)).\n\n- **Lua ([luajit](https://luajit.org/luajit.html) 5.x), C, and [embedded Python](https://docs.python.org/3/extending/embedding.html) for scripting [PgBouncer](https://www.pgbouncer.org/).** Our main product, the "data delivery network", is a single SQL endpoint where users can query any data on Splitgraph. Really it's a layer of PgBouncer instances orchestrating temporary Postgres databases and proxying queries to them, where we load and cache the data necessary to respond to a query. We've added scripting capabilities to enable things like query rewriting, column masking, authentication, ACL, orchestration, firewalling, etc.\n\n- **[Docker](https://www.docker.com/) for packaging services.** Our CI pipeline builds every commit into about a dozen different Docker images, one for each of our services. A production instance of Splitgraph can be running over 60 different containers (including replicas).\n\n- **[Makefile](https://www.gnu.org/software/make/manual/make.html) and** [docker-compose](https://docs.docker.com/compose/) **for development.** We use [a highly optimized Makefile](https://www.splitgraph.com/blog/makefile) and `docker-compose` so that developers can easily spin-up a stack that mimics production in every way, while keeping it easy to hot reload, run tests, or add new services or configuration.\n\n- **[Nomad](https://www.nomadproject.io/) for deployment and [Terraform](https://www.terraform.io/) for provisioning.** We use Nomad to manage deployments and background tasks. Along with Terraform, we're able to spin up a Splitgraph cluster on AWS, GCP, Scaleway or Azure in just a few minutes.\n\n- **[Airflow](https://airflow.apache.org/) for job orchestration.** We use it to run and monitor jobs that maintain our catalog of [40,000 public datasets](https://www.splitgraph.com/blog/40k-sql-datasets), or ingest other public data into Splitgraph.\n\n- **[Grafana](https://grafana.com/), [Prometheus](https://prometheus.io/), [ElasticSearch](https://www.elastic.co/), and [Kibana](https://www.elastic.co/kibana) for monitoring and metrics.** We believe it's important to self-host fundamental infrastructure like our monitoring stack. We use this to keep tabs on important metrics and the health of all Splitgraph deployments.\n\n- **[Mattermost](https://mattermost.com/) for company chat.** We think it's absolutely bonkers to pay a company like Slack to hold your company communication hostage. That's why we self-host an instance of Mattermost for our internal chat. And of course, we can deploy it and update it with Terraform.\n\n- **[Matomo](https://matomo.org/) for web analytics.** We take privacy seriously, and we try to avoid including any third party scripts on our web pages (currently we include zero). We self-host our analytics because we don't want to share our user data with third parties.\n\n- **[Metabase](https://www.metabase.com/) and [Splitgraph](https://www.splitgraph.com) for BI and [dogfooding](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)**. We use Metabase as a frontend to a Splitgraph instance that connects to Postgres (our internal databases), MySQL (Matomo's database), and ElasticSearch (where we store logs and DDN analytics). We use this as a chance to dogfood our software and produce fancy charts.\n\n- **The occasional best-of-breed SaaS services** **for organization.** As a privacy-conscious, independent-minded company, we try to avoid SaaS services as much as we can. But we still find ourselves unable to resist some of the better products out there. For organization we use tools like [Zoom](https://www.zoom.us) for video calls, [Miro](https://miro.com/) for brainstorming, [Notion](https://www.notion.so) for documentation (you're on it!), [Airtable for workflow management](https://airtable.com/), [PivotalTracker](https://www.pivotaltracker.com/) for ticketing, and [GitLab for dev-ops and CI](https://about.gitlab.com/).\n\n- **Other fun technologies** including [HAProxy](http://www.haproxy.org/), [OpenResty](https://openresty.org/en/), [Varnish](https://varnish-cache.org/), and bash. We don't touch them much because they do their job well and rarely break.\n\n# Life at Splitgraph\n**We are a young company building the initial team.** As an early contributor, you'll have a chance to shape our initial mission, growth and company values.\n\n**We think that remote work is the future**, and that's why we're building a remote-first organization. We chat on [Mattermost](https://mattermost.com/) and have video calls on Zoom. We brainstorm with [Miro](https://miro.com/) and organize with [Notion](https://www.notion.so).\n\n**We try not to take ourselves too seriously**, but we are goal-oriented with an ambitious mission.\n\n**We believe that as a small company, we can out-compete incumbents** by thinking from first principles about how organizations interact with data. We are very competitive.\n\n# Benefits\n- Fully remote\n\n- Flexible working hours\n\n- Generous compensation and equity package\n\n- Opportunity to make high-impact contributions to an agile team\n\n# How to Apply? Questions?\n[**Complete the job application**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp)\n\nIf you have any questions or concerns, feel free to email us at [[email protected]](mailto:[email protected]) \n\nPlease mention the words **DESERT SPELL GOWN** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMQ==). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Location\nWorldwide

\nDevelopers at Perch write clean and maintainable Python3 and modern Javascript.\n\nOn the backend; we mainly use the battle-tested Django Rest Framework to create scalable, robust, queryable REST APIs. We architect performant database tables and queries in Postgresql, query our multi-terabyte Elasticsearch, connect to microservices, as well as 3rd party APIs to compose the data returned by our endpoints. We use Redis to cache expensive calls where necessary. We use Docker and AWS to support our infrastructure. On the frontend; we have a single page application written in React that connects to our Django API for data.\n\n Our growing development team follows an agile workflow; planning projects that can be broken down into tasks that can be completed in two-week sprints. If you’re a strong technology generalist who loves learning new things and isn’t afraid to dive in and figure things out, Perch might be the place for you.\n\nA day in the life\n\n\n* Work with a team of developers, designers, and stakeholders to plan, build, and deliver updates to our core products and services every sprint.\n\n* Write, test, and ship code for our production Django API.\n\n* Debug errors that might crop up and write patches to fix them.\n\n* Design database tables for new features.\n\n* Refactor and improve existing code for greater simplicity or performance.\n\n* Write code to integrate with 3rd party partners and data sources.\n\n* Write, test, and ship code for our production React app that consumes REST APIs (and possibly GraphQL in the future)\n\n* Write, test, and ship code for multiple Node.js services that consume and produce REST APIs (and possibly GraphQL in the future)\n\n* Work independently to identify bottlenecks and sources of potential failure and improve them.\n\n* Create, maintain, and monitor backend services deployed with AWS for things like email processing, data visualization, and data transformation ( at a pretty large scale )\n\n* Participate in code review and collaborate with other developers to ensure we’re shipping high-quality code and products.\n\n\n\n\n\n\nA perfect match\n\n\n* You have extensive experience writing modern, testable Python code with a team of developers.\n\n* You have experience with a web framework such as Django (Django Rest Framework) or Flask.\n\n* You are comfortable creating relational database models, and preferably have some experience with Postgresql.\n\n* You have experience writing code for web APIs and know what HTTP status codes to use when. You know when to use POST vs PUT requests and some REST API concepts.\n\n* You know some Linux and aren’t afraid to SSH into a server to check out what’s going at the operating system level. Checking disk usage, running processes, or tailing logs.\n\n* You have experience with a modern Javascript framework (NodeJs, Express, React).\n\n* You can follow patterns established by Javascript developers and make changes to React code.\n\n* You have experience querying Elasticsearch.\n\n\n\n\n\n\nAbove and beyond\n\n\n* Experience testing code with PyTest\n\n* Experience with Elasticsearch and other Elastic products\n\n* Amazon Web Services ( RDS, EC2, S3, Beanstalk, and seemingly a million others )\n\n* CI/CD ( Docker, Jenkins, GitHub, or similar )\n\n* Some networking experience, you know what a subnet is\n\n* Cybersecurity interest or background\n\n\n \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to InfoSec, Senior, Full Stack, Developer, Digital Nomad, React, JavaScript, Elasticsearch, Python, API, Linux and Backend jobs that are similar:\n\n $62,500 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n

**About Us**\n\nAt[ Close](https://close.com/), we're building the sales communication platform of the future. With our roots as the very first sales CRM to include built-in calling, we're leading the industry toward eliminating manual processes and helping companies to close more deals (faster). Since our founding in 2013, we've grown to become a profitable, 100% globally distributed team of ~33 high-performing, happy people that are dedicated to building a product our customers love.\n\nOur backend [tech stack](https://stackshare.io/close-crm/close) currently consists of Python Flask/Gunicorn web apps with our TaskTiger scheduler handling many of the backend asynchronous task processing. Our data stores include MongoDB, Postgres, Elasticsearch, and Redis. The underlying infrastructure runs on AWS using a combination of managed services like RDS and ElasticCache and non-managed services running on EC2 instances. All of our compute runs through CI/CD pipelines that build Docker images, run automated tests and deploy to our Kubernetes clusters. Our backend primarily serves a well-documented [public API ](https://developer.close.com/) that our front-end JavaScript app consumes.\n\nWe ❤️open source – using dozens of open source projects with contributions to many of them, and released some of our own like [ciso8601](https://github.com/closeio/ciso8601), [LimitLion](https://github.com/closeio/limitlion), [SocketShark](https://github.com/closeio/socketshark), [TaskTiger](https://github.com/closeio/tasktiger), and more at https://github.com/closeio\n\n\n**About You**\n\nWe're looking for an experienced full-time Software Engineer to join our engineering team. Someone who has a solid understanding of web technologies and wants to help design, implement, launch, and scale major systems and user-facing features.\n\nYou should have senior level experience (~5 years) building modern back-end systems, with at least 3 years of that experience using Python.\n\nYou also have around five years experience using MongoDB, PostgreSQL, Elasticsearch, or similar data stores. You have significant experience designing, scaling, debugging, and optimizing systems to make them fast and reliable. You have experience participating in code reviews and providing overall code quality suggestions to help maintain the structure and quality of the codebase.\n\nYou’re comfortable working in a fast-paced environment with a small and talented team where you're supported in your efforts to grow professionally. You are able to manage your time well, communicate effectively and collaborate in a fully distributed team.\n\nYou are located in an American or European time zone.\n\n\n**Bonus point if you have**\n\n* Contributed open source code related to our tech stack\n* Led small project teams building and launching features\n* Built B2B SaaS products\n* Experience with sales or sales tools\n\n**Come help us with projects like**\n\n* Conceiving, designing, building, and launching new user-facing features\n* Improving the performance and scalability our API. Help expand our GraphQL implementation.\n* Improving how we [sync ](https://close.com/emailing/) millions of sales emails each month\n* Working with Twilio's API, WebSockets, and WebRTC to improve our [calling features](https://close.com/calling/)\n* Building user-facing analytics features that provide actionable insights based on sales activity data\n* Improving our Elasticsearch-backed powerful [search features](https://close.com/search/)\n* Improving our internal messaging infrastructure using streaming technologies like Kafka and Redis \n* Building new and enhancing existing integrations with other SaaS platforms like Google’s G Suite, Zapier, and Web Conferencing providers\n\n\n**Why work with us?**\n\n* 100% Remote *(we believe in trust and autonomy)*\n* 2 x Annual Team Retreats ✈️ ([Lisbon Retreat Video](https://www.youtube.com/watch?v=gKjyXMz-q-Q&feature=youtu.be))\n* Competitive salary\n* Medical, Dental with HSA option - 99% premiums paid (*US residents)*\n* 5 Weeks PTO + 6 Government Holidays + Dec 24 - Jan 1 Company Holiday\n* Parental Leave *(10 wks primary caregiver / 4 wks secondary caregiver)*\n* 401k matching at 4% *(US residents)*\n* [Our story and team](https://close.com/about/) 🚀\n* [Glassdoor Reviews ](https://www.glassdoor.co.uk/Reviews/Close-Reviews-E1155591.htm)\n\nAt Close, everyone has a voice. We encourage transparency and practicing a mature approach to the work-place. In general, we don’t have strict policies, we have guidelines. Work/Life harmony is an important part of our organization - we believe you bring your best to work when you practice self care (whatever that looks like for you).\n\nWe come from 12 countries and 14 states; a collection of talented humans rich in diverse backgrounds, lifestyles and cultures. Twice a year we meet up somewhere around the world to spend time with one another. We see these retreats as an opportunity to strengthen the social fiber of our community.\n\nThis team is growing in more ways than one - we’ve recently launched 8 babies (and counting!). Unanimously, our favorite and most impactful value is “Build a house you want to live in.” We strive to make decisions that are authentic for our organization. At Close, we have a high care factor for one another, in making an awesome product and championing the success of our customers. \n\n*Interested in Close but don't think this role is the best fit for you? View [our other positions](https://jobs.lever.co/close.io/).* \n\nPlease mention the words **NEGLECT YEAR POSITION** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMQ==). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Elasticsearch, Python, Senior, Engineer, Backend, Redis, Developer, Digital Nomad, JavaScript, API, Sales and SaaS jobs that are similar:\n\n $62,500 — $125,000/year\n
\n\n#Benefits\n ⏰ Async\n\n🌎 Distributed team\n\n
\n\n#Location\nAMERICAS OR EUROPEAN TIME ZONE

**ABOUT US**\n\n\n\nAt Close.io we’re building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring engineers to join our DevOps team to help take our platform to the next level by adding new features, providing better performance, and even higher reliability. We are a ~30 person entirely remote team (with ~13 engineers) that is profitable and building a product our customers love.\n\n\n\nOur backend tech stack currently consists of Python Flask/Gunicorn web apps with our TaskTiger scheduler handling many of the backend asynchronous processing tasks. Our data stores include MongoDB, Elasticsearch, PostgreSQL, MySQL, and Redis. Our infrastructure runs on AWS using a combination of managed services like RDS and ElastiCache as well as EC2 instances managed by Puppet. These EC2 instances run everything from our databases to our Kubernetes clusters.\n\n\n\n**ABOUT YOU**\n\n\n\nWe're looking for a full-time DevOps Engineering Manager / Team Lead to join our core team who has significant experience in building, managing, and monitoring infrastructure and backend services at scale.\n\nIn this Team Lead role, you will be doing *both* hands-on technical work yourself *and* managing/leading a small remote team (2-3 people) of exceptional Senior SRE/DevOps Engineers.\n\n\n\n**Come help us with projects like**\n\n\n\n* Building out our Kubernetes infrastructure to include additional services, increased redundancy/scalability, and harnessing new k8s features\n\n* Scale our Elasticsearch and MongoDB clusters to support our data growth\n\n* Tune our MySQL and PostgreSQL databases\n\n* Improve our public Close.io API performance and resiliency\n\n* Tighten security across our infrastructure\n\n* Implement autoscaling techniques that balance performance, workload demands and costs\n\n* Improve our CI/CD process making builds/deployments faster and safer\n\n* Further develop our Prometheus/Grafana monitoring infrastructure\n\n* Enhance our Elasticsearch/Logstash/Kibana (ELK) logging stack\n\n\n\n**And leadership responsibilities like**\n\n\n\n* Being responsible for the happiness, well-fare, and productivity of the DevOps team; do regular 1:1s.\n\n* Leading the strategy, roadmap, and goals for the DevOps team\n\n* Coordinating with other engineers on current and upcoming infrastructure needs for Product and overall business goals\n\n* Having the primary responsibility for the stability, performance, and security of our infrastructure\n\n* Hiring/growing the team as needed, while keeping a high quality bar\n\n\n\n**You should**\n\n\n\n* Have 2+ years managing & leading an engineering team, including experience recruiting/hiring great engineers\n\n* Have a servant leadership attitude with the ability to foster a collaborative & positive energy work environment, especially when PagerDuty is calling\n\n* Have real world experience building scalable systems, working with large data sets, and troubleshooting various back-end challenges under pressure\n\n* Have significant experience with *nix, Python, bash, and Puppet or similar backend systems and frameworks\n\n* Experience working with large databases running on MySQL, PostgreSQL, and/or Mongo\n\n* Have experience configuring monitoring, logging, and other tools to provide visibility and actionable alerts\n\n* Enjoy automating processes using Python, bash, Puppet, or other scripting languages\n\n* Have experience with Docker containers and microservices\n\n* Understand the full web stack, networking, and low level Unix computing\n\n* Always be thinking of ways to improve reliability, performance, and scalability of the infrastructure\n\n\n\n**Why work with us?**\n\n\n\n* Our story and [team retreat video!](https://www.youtube.com/watch?v=gKjyXMz-q-Q&feature=youtu.be)\n\n* Stellar team reviews on [Glassdoor](https://www.glassdoor.com/Reviews/Close-io-Reviews-E1155591.htm)\n\n* Work remotely and create your own schedule (we believe in trust and autonomy)\n\n* Enjoy face-to-face time with the whole team on all-expense paid retreats 2x year.\n\n* Experience building a truly successful SaaS company with a dedicated, small team where you can have a huge impact\n\n* Above market salary\n\n* Excellent medical & dental coverage, including 99% paid premiums and HSA option (**US residents)\n\n* Matching 401k (**US residents)\n\n\n\nInterested in DevOps but think this Team Lead role isn't the right fit? View our [SRE/DevOps Engineering role](https://jobs.lever.co/close.io/38d0c4ac-c3eb-47e9-a49e-4611f96eef8d) or all our other positions. \n\nPlease mention the words **THUMB PERSON ROUTE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMQ==). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to DevOps, Elasticsearch, Engineer, Redis, Executive, Python, API, Senior, Sales, SaaS, Medical and Backend jobs that are similar:\n\n $70,000 — $120,000/year\n
\n\n#Benefits\n ⏰ Async\n\n