jefflembeck’s avatarjefflembeck’s Twitter Archive—№ 25,173

                      1. Let's talk hiring _again_ today. Our team is opening up ANOTHER position. This time: Senior Infrastructure Engineer. Let's break down this job 🧵
                    1. …in reply to @jefflembeck
                      As part of the team, you'll improve the environment that our services are deployed to; keeping deploys fast, reliable, & ergonomic, while expanding the deploy flows to new technologies; securing our systems; supporting its current software system & building new tools as needed
                  1. …in reply to @jefflembeck
                    To succeed in this role, it takes a type of person: - You are a custodian, not an owner. - You open gates and do not close them. - You take responsibility for your work. - You care about the developers you're enabling: you care about their experience writing and releasing code.
                1. …in reply to @jefflembeck
                  - You automate - You think about the effects of changes in infra on the team as a whole. You think about the impact of your actions and how they might go wrong - You work with the people around you to model security threats, and work with developers constructively to address them
              1. …in reply to @jefflembeck
                - You seek to make the systems you work on observable, so the team as a whole can usefully understand how their systems behave - You can untangle undocumented legacy systems as part of the process of replacing them - You are willing to learn new technologies - You like teaching
            1. …in reply to @jefflembeck
              As far as techs we use? - AWS: mostly EC2, RDS, and ALBs - Ubuntu - GitHub Actions - Terraform - Ansible - Cloudflare - bash familiarity helps, but mastery is not necessary Nice-to-haves include Honeycomb.io, edge proxies (Envoy/haproxy), and edge caches (varnish).
          1. …in reply to @jefflembeck
            - We currently do not plan to move into Docker-centric deployments. - We currently do not plan to move into language ecosystems other than JavaScript and Rust. I don't have any beef with any other systems. This is just our current plans.
        1. …in reply to @jefflembeck
          I like working at Eaze. The cannabis industry presents a unique set of challenges and we're always preparing for what's next. More importantly, though, I have support all the way up the ladder on creating a diverse and inclusive environment and we put our money where our mouth is
      1. …in reply to @jefflembeck
        We actively acknowledge that today’s cannabis industry is wholly indebted to decades of work and activism by Black and Brown communities, and without them, we're not here. (There was a blog post listing things, and I actually think they're all important: eaze.com/article/listening-and-learning)
    1. …in reply to @jefflembeck
      So if this sounds interesting to you, come talk to me. DM me. This is a remote job that is (unfortunately) only available to people eligible to work in the US. Job post coming soon.
  1. …in reply to @jefflembeck
    (shoutout to my colleagues ceejbot and isntitvacant for writing this job post, btw)
    1. …in reply to @jefflembeck