This job post is closed and the position is probably filled. Please do not apply. Work for ZibaSec and want to re-open this job? Use the edit link in the email when you posted the job!
We are looking for a senior infrastructure engineer, with deep AWS experience, who feels comfortable with new project implementation. Prior experience with serverless architectures is ideal.\n\nThe ideal candidate has experience with programmatically managing AWS infrastructure. We currently use Serverless Framework and Terraform.\n\nWe are looking for expert level proficiency in Python. Experience with any of the following is an additional asset:\n\n- Linux\n- Node\n- Working with the AWS SDK\n- Infrastructure as Code\n- Writing CLIs\n- CI/CD architectures including developing CI-server workflows\n- Terraform (or something similar like Ansible, etc)\n\n## **Weโd be especially interested in you if you have:**\n\n- Contributed to any infrastructure or security automation project in the open source world\n- Built systems around observability and tracing\n- Knowledge on Chaos engineering concepts and theory\n- Fought and won battles against AWS Lambda + AWS API Gateway\n- Worked under the constraints of FedRAMP\n\n# About ZibaSec\n\nThe best way to learn about our company is to look at our publicly available employee handbook at [https://www.notion.so/zibasec/Our-Why-f5245149408f4f43baad7ef4de4e0a91](https://www.notion.so/zibasec/Our-Why-f5245149408f4f43baad7ef4de4e0a91)\n\nWeโre an early stage, funded startup focused on helping organizations improve their security posture. We build easy-to-use tools that make it harder for attackers to exploit the people within an organization.\n\nOur flagship product is focused on helping organizations run email phishing campaigns against their own employees. This lets organizations assess their risk levels while also providing insight as to what type of training might be necessary for their organization.\n\nWe are a growing company and can promise you the following:\n\n- A diverse organization.\n- A safe workplace with zero tolerance for discrimination and harassment of any kind.\n- A solid workstation; your choice of a Linux, Mac, or Windows laptop.\n- A 100% remote and balanced work life. We actually prefer you don't work for more than 40 hours a week. We don't have VCs or other outside entities to answer to, and we rather our people have a balanced life than no life.\n- Flexible scheduling. Early riser? Night owl? No problem. We maintain an overlapping 3-hour window for synchronous work. Other than that, work any hours that work for you!\n- We're a tight-knit group and we value each other. Your voice will carry the same weight as anyone else.\n- You'll have dedicated time to learn, and a budget to pay for it.\n\n# **ZibaSec's Core Software Beliefs**\n\n- **Testing is important:**ย Untested code does not get shipped...but hitting 100% unit test coverage can be detrimental to productivity for no or very little gain; it's about the right balance. We're more fond of integration and end-to-end testing.\n- **Git activity != actual productivity:**ย Developers need time to debug locally, research, and learn.\n- **Continuous Deployment:**ย When code is ready, passes tests, it should make it into production within minutes.\n- **Readability > clever code:**ย Slick code isn't so slick if it's hard to grok.\n- **Continuous Improvement:**ย Everything can be improved and nobody knows any code, stack, framework perfectly; there is always room to learn and improve. In fact, we'll provide you with a budget that you can spend on learning (conferences, courses, etc).\n- **Dogma is bad:**ย Some method, technique, etc., may have been the right answer 100 times, but on the 101st time it's possible that another way could be the best path.\n- **Open Source is crucial:**ย As a company, we're very involved with open source, we are active consumers and contributors to multiple projects. We feel so strongly about this that if we find that a particular internal library could be beneficial to the outside world, then we take the time to package it up and open source it as a standalone library (we did exactly this for a Django SAML2 authentication back end). \n\nPlease mention the words **DRUM RIDE BOMB** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMjU=). 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
$180,000 — $180,000/year\n
\n\n#Location\nUnited States
# How do you apply?\n\nThis job post has been closed by the poster, which means they probably have enough applicants now. Please do not apply.
This job post is closed and the position is probably filled. Please do not apply. Work for Sketch and want to re-open this job? Use the edit link in the email when you posted the job!
Over a million designers use Sketch to transform their ideas into incredible products, every day. Would you like to join us and help take the infrastructure that supports this leading design tool to the next level? We're looking to expand our team with a full-time **Site Reliability Engineer**.\n\nAt Sketch, we work with a unique technology blend: a cloud platform and macOS and iOS applications. Our cloud stack is based on a mix of serverless and traditional server applications built on Elixir and Go, along with other cloud services like RDS PostgreSQL, S3, SQS, ... Most pieces are deployed on AWS ECS and automated through Terraform; we use Chef for configuration management where it's needed. Our SRE team usually codes with Python whenever we need to write a small program or script.\n\nAs a Site Reliability Engineer at Sketch, you will focus on shaping our cloud infrastructure and make sure all the pieces work well together: development environments, metrics processing and observability, security policies, network design, deployment strategies, high availability, etc. You will work closely with backend, frontend, Mac developers and product managers to guarantee product focussed, smooth engineering processes.\n\nAs an example of one complex project we have worked on lately, we recently migrated our production database from MariaDB to PostgreSQL using streaming replication to minimise the potential downtime and have replicated environments to adapt and test our backend APIs properly.\n\n**About you**\n\nWe look for someone who has experience with different stacks (mainly Linux based), technologies and production models and has participated actively on the build of essential pieces of a cloud platform.\n\nSomeone that knows how to conduct a technical operation that potentially affects users and at the same time can code small applications and scripts to automate the platform and also debug problems in other people's code.\n\nYou care about security, code quality, scalability, performance, and simplicity. Above all, you seek operational excellence and apply the best engineering practices possible. Not everything that you or your team do can be perfect, but you make sure that you always know the trade-offs. You back your decisions with arguments. You don't care for hype and always try to find the best solution and technology for the job and its context.\n\n**Essentials**\n\n* Professional experience managing Linux-based and cloud-native distributed systems in the past\n* Experience coding with high-level programming languages like Python\n* Experience with Infrastructure as Code tools such as Terraform, and configuration management tools to automate manual operations\n* A good understanding of the HTTP protocol and the behavior of production web services\n* Excellent communication skills and a good written and spoken English\n* You're based in European / African timezones.\n\n**About Sketch**\n\nSketch is a 100% remote company, and your colleagues are distributed around the globe. Being remote adds great flexibility, and helps us build a more diverse team. We put respect for each other above everything else.\n\nBesides being remote we work asynchronously as often as we can. This means that our team communicates mostly using Slack and GitHub. When we need it, we also have video calls.\n\nOur Technology team has more than 60 people today, split between Mac, Backend, Frontend, Infrastructure and QA. In particular, the Infrastructure team has 6 members. We work in multidisciplinary squads: people from different roles, including members of the Product team, work together on solving problems and delivering functionality to our users.\n\n**We care about your well-being and your professional success, so we offer you**\n\n* Flexibility to organize your own time, no set hours\n* As many vacation days as you need\n* Whatever training you need to develop in your job\n* The laptop you need\n* The option to work anywhere in European/African timezones\n* Company equity\n* Paid family leave \n* An annual company meetup \n\nPlease mention the words **UPDATE BANANA UNUSUAL** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMjU=). 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#Benefits\n
โฐ Async\n\n
\n\n#Location\nWorldwide
# How do you apply?\n\nThis job post has been closed by the poster, which means they probably have enough applicants now. Please do not apply.