Skip to main content

Interviewing Tips

 Here are a few tips I recommend.

1. Practice your pitch.  Start with what you want to accomplish in your next role.  Then, highlight your career and accomplishments that build your career testimony to today.  This will be in every interview.  You should even right it down for practice.  The higher the role the better the pitch needs to be.  

2.  Research the company and ask questions about them.  Hard questions.  Make them squirm and show they need you.  I asked one panel of senior leaders, can you tell me about your financial stability and budgets for the next year.   In a more technical panel, I asked how they were managing and deploying their containers in the cloud.  They weren't.  There are plenty of jobs out there and you have to find the right fit for you.

3.  Don't talk about what you did or do.  Talk about what you will do.  Don't say "We" do this or "We" use this tool.  Say, "I am a big fan of .... because .... but I am familiar with ...."   

4. Apply for jobs on LinkedIn, Indeed, and the Ladders.  Ladders is my favorite because they make it easy.  After you apply, try to find the recruiter and connect with them on LinkedIn.  Try to find the hiring manager and view his profile.  He might get notified and remember your name.  See if you have other connections to the company and ask them to refer you.  

5. Say things that will wow them.  Once company asked me to tell them my perfect DevOps pipeline.  This is a trap for a Director or above position.  If you just start off, Git, jenkins, artifactory..... security... Puppet, they are going to remember your tools and judge that against their tools.  The right answer is there is no "Perfect" pipeline or solution.  It depends on the team, process, and the technologies right?  First, thing I said, "There is no perfect DevOps tool set" and I gave them an example where I convienced a leader to consider another tool because it aligned with another department.  This allowed us all to learn and scale the solution faster versus adding another tool to the company's "tool soup".

6. If it is a leadership role, you should be talking about your core principles throughout the discussion.  Growth Mindset, Fail Fast and Learn, Empathy, Continuous Improvement,...  DevOps is about maturing to a great culture and they need to see your passion for that kind of culture.  Then, if you don't get hired, you know they didn't align with your values. 

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...
Post a Comment
Read more

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more