Loading...
{{notif_text}}
How often have you read job descriptions and gone ‘I have read this before’ or ‘the real job description will come out during the interviews, so why bother reading this’. In other instances when job descriptions are actually well-written, ie not just copied and pasted from somewhere and try doing justice to what you’d be doing at the job, 2-4 months of a typical interview cycle make those descriptions obsolete by the time you actually start at the job. Also not unsurprising then: just like you ignore or skim through job descriptions, most recruiters do the same with your resumes – look for specific keywords and leave all the assessment for during the interview itself. Even worse: the human recruiter in some cases is being replaced by an algorithm to automate screening. You therefore will try to put as many keywords in your resume to ensure you get that interview call. Nobody is being ingenuine in this process but the very process is fundamentally broken. And that is exactly what we want you to help us solve: create an effective ‘matching of work to the worker’ that is an accurate and real-time reflection of both ends, thus increasing the actual engagement with the work itself. What you’ll be doing - Work with co-founders to conceptualize and build backend of innovative products. - Continually improve code quality, performance and reliability in your products, with a focus on backend technology. What we need from you - BS in Computer Science or equivalent practical experience. - Significant practical experience with at least one of the following languages: Python, Java, C++, C#, Go. - Ability to effectively collaborate with and influence members of a frontend product team. Something more is always good though not mandatory - As a member of a cross-functional team, you’ll need to be comfortable making changes outside of the backend stack, typical applications here have a React frontend.
How often have you read job descriptions and gone ‘I have read this before’ or ‘the real job description will come out during the interviews, so why bother reading this’. In other instances when job descriptions are actually well-written, ie not just copied and pasted from somewhere and try doing justice to what you’d be doing at the job, 2-4 months of a typical interview cycle make those descriptions obsolete by the time you actually start at the job. Also not unsurprising then: just like you ignore or skim through job descriptions, most recruiters do the same with your resumes – look for specific keywords and leave all the assessment for during the interview itself. Even worse: the human recruiter in some cases is being replaced by an algorithm to automate screening. You therefore will try to put as many keywords in your resume to ensure you get that interview call. Nobody is being ingenuine in this process but the very process is fundamentally broken. And that is exactly what we want you to help us solve: create an effective ‘matching of work to the worker’ that is an accurate and real-time reflection of both ends, thus increasing the actual engagement with the work itself. What you’ll be doing - Work with co-founders to conceptualize and build frontend of innovative products. - Continually improve code quality, performance and reliability in your products, with a focus on frontend technology. What we need from you - 3+ years professional experience in frontend engineering, including experience working on at least one public-facing product with a global presence and significant traffic. Comfort with “vanilla” JS is a must. - Significant practical experience with client-side JavaScript, CSS, component-driven UI development, and frontend tooling. - Ability to effectively collaborate with and influence members of a backend product team. Something more is always good though not mandatory - As a member of a cross-functional team, you’ll need to be comfortable making changes outside of the frontend stack, typical applications here have a Python backend.
How often have you read job descriptions and gone ‘I have read this before’ or ‘the real job description will come out during the interviews, so why bother reading this’. In other instances when job descriptions are actually well-written, ie not just copied and pasted from somewhere and try doing justice to what you’d be doing at the job, 2-4 months of a typical interview cycle make those descriptions obsolete by the time you actually start at the job. Also not unsurprising then: just like you ignore or skim through job descriptions, most recruiters do the same with your resumes – look for specific keywords and leave all the assessment for during the interview itself. Even worse: the human recruiter in some cases is being replaced by an algorithm to automate screening. You therefore will try to put as many keywords in your resume to ensure you get that interview call. Nobody is being ingenuine in this process but the very process is fundamentally broken. And that is exactly what we want you to help us solve: create an effective ‘matching of work to the worker’ that is an accurate and real-time reflection of both ends, thus increasing the actual engagement with the work itself. What you’ll be doing - Being a senior member, you will be responsible for hiring and managing the devops team. - Automating our deployment processes, customizations, upgrades and monitoring all the active services. - Conceptualizing and creating devops library that can be reused for different clients. - Developing effective tooling, dashboards, alerts, and response to identify and address reliability risks. - Understanding complex projects and working closely with the team and global clients towards a solution. - Guiding us to better tools and practices, and champion adopting better technologies. What we need from you - At least 3 yrs of experience in hiring and managing the devops team. - Bachelor's degree in Computer Science, Mathematics, related technical field with 5 yrs of mandatory experience in DevOps field. - Experience in writing software in one or more languages, such as Java, Python, Go, JavaScript, C++ or similar. - Experience maintaining internet facing production-grade applications in virtualized environments. - Experience managing internal or client-facing projects, troubleshooting clients' technical issues and working with engineering, sales and services teams and customers. Something more is always good though not mandatory - Experience working with scalable networking technologies such as Load Balancers/Firewalls and web standards (REST APIs, web security mechanisms). - Experience working with deployment and orchestration technologies (such as Docker, Kubernetes, Terraform, Jenkins). - Experience working with cloud providers (such as AWS, GCE). - Understanding of open source server software (such as NGINX, RabbitMQ, MYSQL, Redis, Elasticsearch, Prometheus). - Familiarity with standard IT security practices such as encryption, certificates and key management.
How often have you read job descriptions and gone ‘I have read this before’ or ‘the real job description will come out during the interviews, so why bother reading this’. In other instances when job descriptions are actually well-written, ie not just copied and pasted from somewhere and try doing justice to what you’d be doing at the job, 2-4 months of a typical interview cycle make those descriptions obsolete by the time you actually start at the job. Also not unsurprising then: just like you ignore or skim through job descriptions, most recruiters do the same with your resumes – look for specific keywords and leave all the assessment for during the interview itself. Even worse: the human recruiter in some cases is being replaced by an algorithm to automate screening. You therefore will try to put as many keywords in your resume to ensure you get that interview call. Nobody is being ingenuine in this process but the very process is fundamentally broken. And that is exactly what we want you to help us solve: create an effective ‘matching of work to the worker’ that is an accurate and real-time reflection of both ends, thus increasing the actual engagement with the work itself. What you’ll be doing - Automating our deployment processes, customizations, upgrades and monitoring all the active services. - Creating and supporting devops library that can be reused for different clients. - Developing effective tooling, dashboards, alerts, and response to identify and address reliability risks. - Understanding complex projects and working closely with the team and global clients towards a solution. What we need from you - Bachelor's degree in Computer Science, Mathematics, related technical field with 3 yrs of mandatory experience in DevOps field. - Experience in writing software in one or more languages, such as Java, Python, Go, JavaScript, C++ or similar. - Experience maintaining internet facing production-grade applications in virtualized environments. - Experience managing internal or client-facing projects, troubleshooting clients' technical issues and working with engineering, sales and services teams and customers. Something more is always good though not mandatory - Experience working with scalable networking technologies such as Load Balancers/Firewalls and web standards (REST APIs, web security mechanisms). - Experience working with deployment and orchestration technologies (such as Docker, Kubernetes, Terraform, Jenkins). - Experience working with cloud providers (such as AWS, GCE). - Understanding of open source server software (such as NGINX, RabbitMQ, MYSQL, Redis, Elasticsearch, Prometheus).
Hiring team responds within a day
