The most important thing to me is that I can operate complex technical systems and I work well with other people while following community guidelines. Not only can I operate those systems, but I can also contribute to them to add value and affect change.
Four direct reports. Together we built out an infrastructure and container platform on proxmox, and Kubernetes. All on prem, coming from a pure Linux/Chef/KVM environment.
- In the first 30 days, built an entire turn key local K8's development environment using flux.
- Using the aforementioned environment, I had to sell a green field project, at a company I was fresh to myself to hook 2 new hires.
- Set team culture, work directives, and vision. I really fostered a collaborative environment.
- Did gap analysis for an upcoming infrastructure order. Working across Linux interfaces regarding KVM and Ceph to generate reports for current resource allocation as well as projected growth.
- Got quotes from multiple vendors. Cisco, Dell, Vast, Nimble. Some of which I meticulously hand crafted.
This one almost needs a blog post. It's an interesting one. Hyper Growth Fintech Unicorn. A lot of cool stuff going on, but I have less of a broader architectural success here, and I'm not sure I'll find it. It's almost like super high level administrative work. It's terraform, it's k8s, lots of IAM, complex data services, multi account AWS, but it's incoherent. Very ticket based, all Jira. There's often a strong lack of context, and no time to properly gain that context amongst competing and poorly prioritized priorities. It's as if the company is beholden to scale free correlation. That's not to say it's bad, just perhaps not quite what I was hoping it was going to be. It's DevOps through a firehose.
- You look at my previous roles. I have a success story. I took "thing" from state A to state Z with the only real directive being "Ryan, make it better". I just don't have that at socure right now. TONS of work, but there's no headline. I'm kind of a glorified infra engineer. I don't really have any autonomy.
My identity at this organization has been tumultuous. Ultimately I'm an IC across a variety of domains including authentication, data services, and dominantly platform engineering surrounding kubernetes.
- Personally led two of the highest profile data migrations at Rocket Companies.
- First, an esoteric high performance ldap data store Ping Directory, housing all of our customer data. No down time.
- Second, the unification of an azure data store and an auth0 datastore for clients of Rocket Pro. Minimal down time given the architecture.
- I've built out the on-premise kubernetes installation. Part of this is organizational; negotiating with security, networking, and infrastructure. A larger portion is programmatically shiming missing functionality from our cloud installation.
- Using the meta controller framework to build custom controllers
- Utilizing the rancher api to orchestrate the installation of flux for fleet management
- Converting and adding a series of helm charts to handle discrepancies on prem.
- Built some tooling around converting CSVs to auth0 data structures
Responsible for managing one of the largest Cloud Foundry (sort of like a highly opinionated k8s) installations on the planet.
- Moved the "Grid Migration" through sandbox and framed the migration process. The Grid was an in house application orchestration platform. The goal was to migrate 1000 or so applications to cloud foundry without code rewrites.
- Emulating the netscaler and building the rule set for routing grid applications to cloud foundry
- Managing the nuances of container runtimes. Garden and runc vs docker
- Using chisel to accelerate development velocity
- Built a sort of bash scripting framework for managing cloud foundry installations and their infrastructure.
Managed the Chef installation for GE and built data service pipelines for the open service broker to facilitate data services to cloud foundry
- Bridged areas where apis were not available with puppeteer wrapped by express server through node.
- Improvements to various ruby api’s. Both a cloud foundry broker, and internally developed api to manage Jenkins pipelines.
- Contributed to the development of the Azure Chef provisioning driver
- I lead and organize the Demo Fridays meeting