Hello, I’m not sure which role you considered applying for but I’m the hiring manager for the BE Python position, so I wanted to share my thoughts. We appreciate your feedback and are regularly tuning our process to make it the most effective for candidates and our recruiting teams. We recognize it is an investment in time to complete the application, but we find those additional questions give us the extra information we need to make good decisions on moving forward with an applicant. We consider your responses alongside your resume, so they really give you an opportunity to set yourself apart from other candidates. If you are interested, I hope you apply and thanks again for your feedback!
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 ~45 high-performing, happy people that are dedicated to building a product our customers love.
We are currently hiring for a few 100% remote positions:
At Close we’re a 100% remote team of ~35 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 product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python/Flask, Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our frontend JavaScript/React app consumes.
We <3 open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
We selected Kubernetes on AWS but there are a lot of details to go from source code all the way through to automated k8s deployments. We are currently using our own framework (https://github.com/closeio/devops/tree/master/scripts/k8s-ci...) but I’m keeping an eye on helm/chart to see if it makes sense to incorporate that at some point. Pykube (https://github.com/kelproject/pykube) has made it easy to automate the k8s depoyment details. We needed a process that would take Python code from our GitHub repos, build and test on CircleCI and then deploy to our k8s clusters.
A single commit to our master branch on GitHub can result in multiple service accounts, config maps, services, deployments, etc. to be created/updated. Making all of that work is complicated enough but then we also need to deal with things like canary deployments and letting us build and deploy to k8s from our local workstations. And then there are details like automatically deleting old images from ECR so your CICD process doesn’t fill that up without you knowing. Incorporating CICD processes with Kubernetes is kind of new so there is a lot of different projects and services starting to address this area.
