Hello! I'm Taylor Turner, a DevOps/Site Reliability/Platform Engineer born and raised in the San Francisco Bay Area. I've been working in the DevOps space since 2012; my focus has been on enabling developer velocity through close collaboration and supporting their teams with tooling, code pipelines, monitoring, and much more. A strong second is on architecting scalable, highly available infrastructure and implementing thoughtful monitoring practices to provide much needed insights to prevent outages.
I'm certified as an AWS DevOps Engineer (Professional), AWS Solutions Architect (Professional), Red Hat Certified Engineer (and System Administrator), A+/Net+/Linux+, and soon CKA.
- AWS (EC2, RDS, VPC, EKS, ECS, IAM, Lambda, API Gateway, SQS, SNS, R53, KMS, Secrets Manager, CloudWatch etc.)
- Containerization, Kubernetes, Helm, CNI networking, Unix
- Terraform, Ansible, Puppet, Cloudformation, boto3
- CI/CD (GHA, Jenkins, CircleCI, GitLab, Travis, ArgoCD)
- Monitoring (Datadog, Grafana, Prometheus, Graphite, Nagios, Cacti, ELK)
- Python, Bash, some C+, Javascript, Golang
- Process optimization, project management, troubleshooting, documentation, diagramming, and more
For synchronous communication, Meet/Zoom > Slack > Email. For asynchronous communication, Slack is always best.
For discussing projects, I prefer high-bandwidth communication in the form of Meet/Zoom or in-person (where applicable).
I prefer direct and analytical communication. I like to know the facts and key deliverables, but I'm also happy to help figure out those things as we go. At times I can be very to the point and it may come across as cold. This usually means I'm deep in thought and working through the problem internally.
Never hesitate to bug me on Slack if I failed to respond to you. I have a terrible habit of reading a message and jumping into finding the answer without acknowledging that I read it. You'll find that I have the answer for you I may have just been pulled in another direction before getting back to you.
Troubleshooting or debugging, creating design docs (or other useful documentation), defining project deliverables, mentorship on the above technologies, sharing embarassing moments and stupid mistakes from the past, and really anything else! If you're honestly stuck I'll do my best to help in whatever capacity I can.
I tend to dislike unstructured meetings or general unpreparedness. I prefer to have a clear agenda for upcoming meetings so that I can come prepared to discuss the topics you have in mind. If you're unsure of the agenda, shoot me a Slack message and I'll gladly help you come up with one!
When it comes to giving personal feedback, I prefer written form where I can take my time and carefully articulate my responses. If I need to provide negative feedback I try to be conscientious of my wording to ensure it comes across as helpful as possible.
I'm usually openly complementative when recogizing peers for doing great work either on Slack or on team calls. If you would prefer that I don't do this in public forums, please let me know.
In general, I prefer feedback via Slack or email but what's most important is that you share your feedback with my in whatever way is comfortable.
I'm always open to hearing feedback, at any time. If there is something I could be doing better, PLEASE speak up and let me know. If you're not comfortable giving it to me directly, feel free to pass it along to my manager.
Racing, I'm a huge fan of F1 and I have a simracing setup at my house that I play in my free time. I'm also an avid gamer in general, it's something I do with my older son whenever I can. Lately we've been playing Fortnite and Valorant.
Once upon a time I was really into bodybuilding, I'm still passionate about fitness and cooking. I also enjoy outdoor sports like hiking, skiing/snowboarding, dirt bikes, etc.