EricFr@nkenberger.com

HOME   RESUME/CONTACT   GITHUB

[07-04-2025] | we do a little interviewing


An Unlikely Teacher

While going full goblin mode playing world of warcraft for 5-10 hours a day during covid quarantine, I met a Hashicorp DevOps engineer who became an unintentional mentor. He gave me a tip to always get a feel for the subject of the day-to-day work, in order to build something to discuss in the next interview. I've applied this advice for my past 3 jobs.

The first was setting up a Selenium grid after learning the company ran a massive internal deployment. The second was spinning up a VM in Azure, connecting a datadog agent to it, configuring alerting, and intentionally triggering an alert. I try to keep time spent to 5-7 hours, over 3-4 nights.

My third execution didn't have as clear of a path from the first interview. I ended up settling on a design prompt from distilling some of the main talking points:

  1. How might I automate Azure resource deployment with something other than Terraform?
  2. If a developer came to me with an API, how would I deploy it?
  3. How can I demonstrate ownership mentality, and design philosophy?

The final deliverable was a wrapper for the Azure CLI as a series of shell commands that deployed an API which served JSON containing the folder structure and all files in the repo used. The build and redeploy scripts read from a configuration file for resource naming, making the solution portable and modular.

It can be viewed at api.nkenberger.com. The top level response contains a link to the Git repo, as JSON doesn't lend itself well to the data I'm displaying.

Other Notes

Due to GitHub Pages being the host for this site, subdomain redirects are difficult. I switched to Cloudflare for DNS after Google sold to Squarespace. Cloudflare prefers proxied DNS, but GitHub Pages won't work properly or issue SSL cert without more work than necessary for this.

I settled on using a Cloudflare worker, a new DNS A record with name API and 192.0.2.1 with Cloudflare proxied DNS. Any requests to api.nkenberger.com are intercepted by the Cloudflare worker, and redirected to the public URL that Azure provisions for the API.

HOME