Recommended
More Related Content
What's hot
What's hot (20)
Similar to DevOps overview and tech interview tips
Similar to DevOps overview and tech interview tips (20)
Recently uploaded
Recently uploaded (20)
DevOps overview and tech interview tips
- 1. HOW TO PREPARE FOR A TECH INTERVIEW DevOps
- 3. In this video Culture, process or role? DevOps history DevOps concepts State of DevOps Common IT disfunctions Main DevOps goals DevOps Tools Tech interview questions
- 5. With a growing constituency, a Devopsdays conference is held for the first time in the United States in Mountain View, California, on the heels of the Velocity annual conference. “The Phoenix Project” written by Gene Kim, Kevin Behr and George Spafford, is a fictional novel that tells the story of an IT manager thrust into a seemingly hopeless situation, as he’s charged with salvaging a mission-critical e- commerce development project that’s gone off the rails. His mentor, guides him into new ways of thinking about IT and application development, introducing the concept of DevOps along the way. At the O’Reilly Velocity Conference, two Flickr employees —John Allspawand and Paul Hammond — gave a now-famous presentation titled, “10+ Deploys per Day: Dev and Ops Cooperation at Flickr”. Debois watched this presentation and was inspired. He formed his own conference called Devopsdays in Ghent, Belgium. Timeline < 1997 “Lean manufacturing” (Toyota) was already well-established as a set of best practices for manufacturing. In IT, traditional waterfall methods of application development were already giving way to rapid, iterative methods, such as agile. 2008 In 2008, at the Agile Conference in Toronto, Andrew Schafer met unsatisfied Belgian consultant Patrick Debois to discuss “Agile Infrastructure”. 2009 2010 2013 The Future It’s reasonable to describe DevOps as a journey, rather than defined destination. “Besides repeating the devops stories, we also need to seek diversity and make sure we keep adapting to situations”. – Patrick Debois.
- 7. “DevOps is the union of people, process, and technology to enable continuous delivery of value to customers.” https://azure.microsoft.com/en-us/overview/what-is-devops/
- 8. Culture is a key component of DevOps and technology transformations Somethings are important to DevOps teams: cooperation, surfacing problems (training messengers to bring us bad news so we can find and fix errors – don’t hide mistakes), breaking down silos (bridging encouraged), postmortems (failure leads to inquiry to find the root cause, not guilty), and continually experimenting to drive improvement (novelty implemented).
- 9. Pathological (power-oriented) Bureaucratic (rule-oriented) Generative (performance-oriented) Low cooperation Modest cooperation High cooperation Messengers “shot” Messengers neglected Messengers trained Responsibilities shirked Narrow responsibilities Risks are shared Bridging discouraged Bridging tolerated Bridging encouraged Failure leads to scapegoating Failure leads to justice Failure leads to inquiry Novelty crushed Novelty leads to problems Novelty implemented Model of organizations culture Westrum, Ron. “A Typology of Organisational Cultures.” Quality and Safety in Health Care 13, no. suppl 2 (2004): ii22–ii27.
- 10. Letting the team prioritise good outcomes for customers, even if it means bending the rules. Customer driven Allowing the team to change rules if the rules are obstacles to achieving the goals. Rules Establishing and communicating goals, but letting the team decide how the work will be done. Communication Removing roadblocks by keeping rules simple. Impediments Leaders job
- 11. Not a role Not just an interface!!!
- 15. “IT is a bottleneck to deliver value to customers.” Daniel Bezerra
- 17. “The main goal is to increase collaboration among those involved in the software development process, in order to deliver value faster and more reliably”. Daniel Bezerra
- 18. Decrease Lead Time (time to market) Increase software quality Increase resilience DevOps goals
- 19. DevOps tools IaC •Ansible •Terraform •Puppet •Chef • Cloudformation Pipeline/CI •Jenkins •Azure Devops •Travis CI •GitLab •Bamboo •Teamcity Container/VM •Docker •Vagrant Orquestration •Swarm •Kubernets
- 20. DevOps tools Code •Python (#3) •Ruby (#4) •Go (#9) SCM •Git •SVN •Bitbucket Cloud •AWS •GCP •Azure Tests/QA •SonarQube •Selenium
- 22. Tips for a good answer Before the interview Skills to have in order to be better prepared 1.Preparation 1.Do a company research, official website, articles, feedback about the company, company’s requirements 2.Write notes (identify key players, history, services, products, competitors), linkedin page, linkedin pages (recruiters), study a lot, be prepared 10 minutes before. 3.Do everything the day before 4.Future projects of the company 5.Predict questions 6.Study your own history to be more confident 2.Punctuality 3.Thinking before opening your mouth 1.Repeat the question when you answer! 2.better preparation, minimize this issue 3.just do your best, regardless 4.be more attentive 5.good for bullet points 6.not for too long (2-3sec) 4.Speaking clearly and calmly
- 23. Tips for a good answer A great approach to answering behavioural and technical questions is to use the STAR method: • Begin by outlining the Situation you were facing • Move on to identifying the Task, or goal, you had to achieve • Then discuss the Actions you took to help achieve your goal • And finish with the end Result OR CAR (Context, Actions, Result)
- 24. How is Ansible used as a CM tool?
- 25. How would you improve the performance of an application?
- 26. How do you deploy software?
- 27. How have you handled failed deployments?
- 31. Thank You!
Editor's Notes
- Hello guys! How are you doing? My name is Daniel. Today we’re going to have a friendly talk about DevOps. We will discuss some technical topics and a few tips to help us all for a tech interview.
- I work at a governmental bank and I am consultant as well. I have 20+ years of experience working with IT. Since 2014 I work with Agile and DevOps.
- The purpose of this video is to cover some topics, as you can see:
- In 1997 we began to apply agile methods instead of the traditional waterfall. 2008 was the year of the famous meeting of Patrick Debois and Andrew Schafer at the agile conference. They discussed “Agile Infrastructure”. In 2009 another famous presentation occurred. Two Flicker guys presented the "10+ Deploys per Day”. Parick Debois also formed the Devopsdays conference. In 2010 Devops days went to Mountain View, California, the home of many high technology companies. In 2013 “The Phoenix Project” was written. It’s a novel in witch an IT manager has a mentor that guides him into new ways of thinking about IT and application development, introducing the concept of DevOps along the way. The future of DevOps is to keep adapting and continue to evolve throughout the world.
- Cooperation, surfacing problems (don’t hide mistakes), breaking down silos (bridging encouraged), postmortems (failure leads to inquiry to find the root cause, not guilty), and continually experimenting to drive improvement.
- Responsibilities shirked – Responsabilidades evitadas Failure leads to scapegoating - Fracasso leva ao bode expiatório Messengers neglected – Mensageiros negligenciados
- Devops is the link that keeps then at the same pace!
- Has anyone seen this picture before? Pretty famous, right?
- And this one? Ops team helping dev to find a performance issue or something…
- I really don’t wanna be pretentious, but this is the truth for many many companies! I’ve been seen IT like working not that in favor of the core business a thousand times!
- Directly related to its concept.
- - Lead time clock starts when the request is made and ends at delivery. Cycle time clock starts when work begins on the request and ends when the item is ready for delivery. - Quality because of the process automation - Resiliency is the property of getting back to the a previous condition. IT resilience is the ability to quickly recover and continue to operate in the event of a disruption.
- Docker is a container platform. A container is a standardized unit of software. It’s like a single process that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another. It’s a single encapsulated process running into a host. Vagrant is a tool for building and managing virtual machine environments. It provides easy configure, reproducible and portable work environments built on top of VirtualBoxes. Swarm orchestrates Docker containers (from Docker company) and Kubernets does the same, is more robust and was originally designed by Google.
- Programing Languages Octoverse.GitHub Frequency: Annually. Methodology: Based on the number of opened GitHub pull requests in the past 12 months.
- Ansible is a configuration management tool that implements infrastructure as a code. Because of that, you can use any version control system to manage the servers and environment configurations together with the application’s source code. So, it’s easier to ensure that application and infrastructure get synched. When used together with an SCM tool, it guarantees a robust traceability. It’s possible to restore infra scenario to previous states just running a simple “playbook”.
- I can take some solution paths. I’ll take two: Application code side - SQL statements (cursors) Using performance monitor tools Look at the execution plan and look for full table scans Build indexes Run some tools that search for bad code like SonarQube Infrastructure side Scale vertically and horizontally Application server and database server - Update Software Versions - Cache Static and Dynamic Content - Add a Load Balancer Review the whole architecture of the app (use serverless processing)
- I would talk about de deployment processes and CI/CD tools and how they fit together.
- Tell the story of a failed deployment and how it was handled. Can include: “How do you know there was a deployment failure?” “Do you roll back automatically?” and “What criteria do you use?”