Next time you're asked to do a take-home coding assignment for a job application, push back a little.

Most job applicants are rejected, including many good ones. Stick in there.

This is my list of red flags when applying for jobs to serve as food for thought when creating your own list.

Most important: Ask anything that could help answer the question "Do I want to work here?"

I’ve said before that “DevOps engineer” is a bit of an oxymoron. I want to explore this idea a bit, by looking at what “DevOps engineers” do. When I do a job search for “DevOps engineer” on LinkedIn, here are some of the commonly required skills and experience: CI/CD pipelines Build automation Cloud providers (AWS, Google, Azure) Configuration management (Ansible, Chef, Puppet, etc) Containerization (Docker, Kubernetes) When we plot these skills and activities against the DevOps lifecycle, we see something like this:

A question I hear a lot is “How do I become a DevOps engineer?” I have two answers to this question. The first probably isn’t very satisfying: “DevOps Engineer” is an oxymoron. DevOps, as a philosophy, is the idea that Development and Operations should work together, in cooperation. My second answer addresses what I expect most people mean by the question: How can a developer adopt a more DevOps mindset, and possibly even move into operations?

Your GitHub profile is the centerpiece of any modern engineering CV. Here are some tips to help make yours stand out.