Location: Boston(ish), USA
Remote: Preferred
Willing to relocate: SF, LA, NYC, Seattle, Chicago, ...?
Technologies: Python, Go, C++, bash, Lua, etc. Terraform, CloudFormation, Chef, Puppet, Ansible. AWS, GCP. Docker, Kubernetes, containerd.
Résumé/CV: https://drive.google.com/file/d/11QKYWGj4TbZW_k09ZM2xSVCOg7Hqnq0k
Email: [email protected]
Github: http://github.com/sparr
I am a software developer with infrastructure related skills, looking for a role probably described as software engineering, site reliability engineering, or devops. I am most at home working on projects creating tooling used by my peers, acting as a force multiplier for their productivity.
When I see someone using these features as part of their workflow, I semi-confidently predict that they spend the majority of their time working on a single codebase, such that the time investment to get everything working was worthwhile.
If, like me, you work on multiple different codebases most weeks, it rarely makes sense to even try setting those things up.