Scott Lundgren

Summary

"Oh, that really sucks; Let's fix that" - conversation with a colleague Early on in my development career, I was entranced by what I could make a computer do. These days, I think about the system affecting the people creating & using it. My transition from writing software into operations was about being frustrated at what it took to get code I'd written deployed. I knew I had to understand what the system administrators knew to make their job easier and faster. Starting with Linux operating systems through 3 tier web application farms to Cloud and now serverless/event-driven architectures I've immersed myself in learning what I needed to know as the next age dawns. Now when presented with new projects I ask more questions of the product owner/business team about how the application contributes to the business (revenue vs cost of goods sold) and its expected usage to discover nuance for architectural decisions (EC2 versus Fargate in EKS) or opportunities for innovation. I'm interested in collaborative environments, innovative industries undergoing transformation, and working with joyful interdisciplinary teams. Industries: transportation/logistics, media/advertising, higher education, automotive, commercial real estate, pharmaceuticals, agriculture, fintech/payments Skills: Languages: PHP, Ruby, Python, Javascript, PERL, C Cloud: Amazon Web Services (EC2, ECR, ECS, EKS, ElastiCache, S3, VPC, Route53, API Gateway, Global Accelerator, AWS Organizations, CloudWatch, CloudTrail, Systems Manager, EMR, Elasticsearch Service, IAM, Secrets Manager, Certificate Manager, Directory Service, WAF, SNS, SQS, SES, WorkSpaces) CI/CD & Version Control: Jenkins, Circle CI, git, Bitbucket, Gitlab, Github Infrastructure: Terraform, Docker, Ansible, Packer, Puppet, Vagrant DB: Amazon Aurora, RDS (MySQL, PostgreSQL, SQL Server), DynamoDB, Redis OS: Amazon Linux 2, Ubuntu LTS, CentOS, RHEL, Windows Server 2016, 2012 R2, 2008