{"id":24600,"date":"2022-01-13T12:00:13","date_gmt":"2022-01-13T17:00:13","guid":{"rendered":"https:\/\/webdevstudios.com\/?p=24600"},"modified":"2024-04-15T11:55:28","modified_gmt":"2024-04-15T15:55:28","slug":"webdevstudios-backend-engineer","status":"publish","type":"post","link":"https:\/\/webdevstudios.com\/2022\/01\/13\/webdevstudios-backend-engineer\/","title":{"rendered":"WebDevStudios Day in the Life of a Backend Engineer"},"content":{"rendered":"

Dave Romsey<\/h2>\n

Job Title: Backend Engineer<\/h3>\n

Years at WebDevStudios: 2.25<\/h3>\n
\"Dave
Dave Romsey, Backend Engineer<\/figcaption><\/figure>\n

I’ve always been a big fan of WebDevStudios (WDS). I can’t remember precisely what drew me in, but WDS always seemed to make good choices about WordPress development practices.<\/p>\n

When trying to stay on top of WordPress happenings, something related to WDS would always be part of the conversation, whether it was wd_s<\/a>, CMB2<\/a>, the podcasts, or informative blog posts. I adopted a “what would WDS do?” approach to problem solving, which yielded great results. Oh yeah, WDS’ 100% remote thing greatly appealed to me too.<\/p>\n

Years later, after long commutes to do agency work, then dabbling in freelance, an opportunity to work for WDS presented itself. I applied, and went through a paid<\/em> engineering trial, which re-enforced my opinion that that these folks were _doing_it_right()<\/code>.<\/p>\n

I passed the trial, which was a great and challenging experience in and of itself, and officially became a Backend Engineer (BEE) at WebDevStudios.<\/p>\n

A Typical Day<\/h3>\n

A typical day involves thinking about solutions and creating tickets, writing\/testing\/reviewing\/discussing\/documenting\/and deploying code, as well as some other odds and ends sprinkled in. That’s probably not much of a surprise to anyone. I’ll go over things in a little more detail below.<\/p>\n

First Things First: Getting Ramped Up for the Day<\/h4>\n

Each day, I go through a little routine to get myself set up for the day’s tasks. The process looks something like this:<\/p>\n