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

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.  

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...