The document provides tips and guidance for preparing for a software engineering interview at Google. It outlines the types of interviews one may expect, including phone interviews focusing on data structures and algorithms and on-site interviews involving coding, algorithms, system design, and more. Candidates are advised to study various programming languages, data structures, algorithms, and computer science topics in-depth to perform well at the technical interviews.
ChatGPT is a powerful language model developed by OpenAI. It is designed to generate human-like text based on given prompts. As a prompt engineer, you can utilize ChatGPT to create engaging conversations, provide information, answer questions, and assist users. It's a versatile tool for natural language processing tasks, enabling more interactive and intelligent interactions.
Google's Official Note to Product Management CandidatesLewis Lin 🦊
Google's official note to product management candidates
Updated October 2016
Uploader's Note
Google's Text Borrows Heavily from my Google PM prep blog post from 2013: http://www.impactinterview.com/2013/09/google-product-manager-interview/
Excerpt: Lewis C. Lin's The Product Manager Interview https://amzn.to/2X56Q8O
Includes instructions on how to modify the 30-day guide for Uber & LinkedIn PM interviews
This presentation was given at a Design Thinking workshop as part of Philly Tech Week 2017. Topics covered include an intro to design thinking, a User Journey mapping activity, and a Team Design Challenge.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
ChatGPT is a powerful language model developed by OpenAI. It is designed to generate human-like text based on given prompts. As a prompt engineer, you can utilize ChatGPT to create engaging conversations, provide information, answer questions, and assist users. It's a versatile tool for natural language processing tasks, enabling more interactive and intelligent interactions.
Google's Official Note to Product Management CandidatesLewis Lin 🦊
Google's official note to product management candidates
Updated October 2016
Uploader's Note
Google's Text Borrows Heavily from my Google PM prep blog post from 2013: http://www.impactinterview.com/2013/09/google-product-manager-interview/
Excerpt: Lewis C. Lin's The Product Manager Interview https://amzn.to/2X56Q8O
Includes instructions on how to modify the 30-day guide for Uber & LinkedIn PM interviews
This presentation was given at a Design Thinking workshop as part of Philly Tech Week 2017. Topics covered include an intro to design thinking, a User Journey mapping activity, and a Team Design Challenge.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
Holland & Barrett: Gen AI Prompt Engineering for Tech teamsDobo Radichkov
Discover Holland & Barrett's Journey into Gen AI: Prompt Engineering and Beyond"
Join us on a captivating journey into the world of Generative AI as Holland & Barrett's Data Team leads a deep dive into the OpenAI ecosystem and the art of prompt engineering. This SlideShare presentation captures the essence of our recent session dedicated to evangelizing the adoption of Gen AI across business and tech within Holland & Barrett. Delve into the nuances of prompt engineering, the comparative analysis of gpt-3.5-turbo and gpt-4, and our recommendations for starting with Prompt Engineering and Retrieval Augmented Generation (RAG). Whether you're a tech enthusiast, a business leader, or an AI aficionado, this presentation offers valuable insights and practical tips to harness the power of AI in your domain.
If you are not an IT related person, you might be amazing what ODOO is . ?
Odoo is nothing but a suite of open-source business apps written in Python programming language and was released under the AGPL license . Odoo is the leading open source solution . The previous name of Odoo is Open ERP ( until May 2014 ) . The main Odoo components are the server , 260 core modules and around 4000 + community modules it does possess . Odoo has no licensing cost .
Would you like to be able to increase the adoption rate of your product? In this session, we will introduce you to cutting edge concepts and techniques to shift your product development process from output to outcome driven. We will combine elements of Lean Startup, Product Discovery, and Experiment Driven Development to accelerate learning to quickly build products customer love.
Is Agile Data Science just two buzzwords put together? I argue that agile is a very practical and applicable methodology, that does work well in the real world for all sorts of Analytics and Data Science workflows.
http://theinnovationenterprise.com/summits/digital-web-analytics-summit-london-2015/schedule
Effective requirement gathering using Design Thinking techniqueAgile Chandigarh
Deck used by Mr Arjun.B.Ghosh, Agile Coach, Accenture for the session "Effective requirement gathering using Design Thinking technique" at INSPIRE 2018, Agile Chandigarh's Annual Conference.
From Product Vision to Story Map - Lean / Agile Product shapingJérôme Kehrli
A lot of Software Engineering projects fail for a lack of shared vision due to poor communication among people involved in the project.
A sound maintenance of the product backlog can only be achieved if all the people have a good understanding of what they have to do (common vision).
Roman Pichler, in a post originally written in Jul 16 2012, has proposed a really interesting approach: use various canvas to create and share product vision and product backlog creation and refinement.
This presentation is a drive through these various boards and canvas that should be designed in prior to any product development: the Product Vision, the Lean Canvas, The Product Definition and the Story Map.
The second lecture in the HIT Lab NZ Design Thinking class on understanding and empathising with end users.
Taught by Mark Billinghurst at the University of Canterbury on December 10th 2013.
Product roadmaps are an important product management tool. But traditionally, they map features onto a timeline that often extends many months into the future. This makes them hard to apply in an agile context where change and uncertainty are present. My talk shows how you can use agile product roadmaps, roadmaps that describe the value the product should create, align the stakeholders and development teams, and unburden the product backlog while avoiding premature commitments and preserving the ability to inspect and adapt.
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
If you are not confident about the fundamentals I would recommend you to take up Data structures and algorithms training in Bangalore, the institute which I found to be the best one is Tutort Academy.
Top 10 Interview Questions for Coding Job.docxSurendra Gusain
Hello everyone!! Today’s blog topic is ‘Top 10 Interview Questions for Coding Job.’ Questions related to programming and coding are a crucial part of a developer’s position interview. If you want to succeed, you need to be familiar with the fundamental concepts of coding and programming. Your coding skills play a huge factor in increasing your chances of hiring in the interview process. Coding is an excellent field with various career opportunities within the country or even abroad but it also means it has lots of competition which makes the whole interview process quite challenging.
Holland & Barrett: Gen AI Prompt Engineering for Tech teamsDobo Radichkov
Discover Holland & Barrett's Journey into Gen AI: Prompt Engineering and Beyond"
Join us on a captivating journey into the world of Generative AI as Holland & Barrett's Data Team leads a deep dive into the OpenAI ecosystem and the art of prompt engineering. This SlideShare presentation captures the essence of our recent session dedicated to evangelizing the adoption of Gen AI across business and tech within Holland & Barrett. Delve into the nuances of prompt engineering, the comparative analysis of gpt-3.5-turbo and gpt-4, and our recommendations for starting with Prompt Engineering and Retrieval Augmented Generation (RAG). Whether you're a tech enthusiast, a business leader, or an AI aficionado, this presentation offers valuable insights and practical tips to harness the power of AI in your domain.
If you are not an IT related person, you might be amazing what ODOO is . ?
Odoo is nothing but a suite of open-source business apps written in Python programming language and was released under the AGPL license . Odoo is the leading open source solution . The previous name of Odoo is Open ERP ( until May 2014 ) . The main Odoo components are the server , 260 core modules and around 4000 + community modules it does possess . Odoo has no licensing cost .
Would you like to be able to increase the adoption rate of your product? In this session, we will introduce you to cutting edge concepts and techniques to shift your product development process from output to outcome driven. We will combine elements of Lean Startup, Product Discovery, and Experiment Driven Development to accelerate learning to quickly build products customer love.
Is Agile Data Science just two buzzwords put together? I argue that agile is a very practical and applicable methodology, that does work well in the real world for all sorts of Analytics and Data Science workflows.
http://theinnovationenterprise.com/summits/digital-web-analytics-summit-london-2015/schedule
Effective requirement gathering using Design Thinking techniqueAgile Chandigarh
Deck used by Mr Arjun.B.Ghosh, Agile Coach, Accenture for the session "Effective requirement gathering using Design Thinking technique" at INSPIRE 2018, Agile Chandigarh's Annual Conference.
From Product Vision to Story Map - Lean / Agile Product shapingJérôme Kehrli
A lot of Software Engineering projects fail for a lack of shared vision due to poor communication among people involved in the project.
A sound maintenance of the product backlog can only be achieved if all the people have a good understanding of what they have to do (common vision).
Roman Pichler, in a post originally written in Jul 16 2012, has proposed a really interesting approach: use various canvas to create and share product vision and product backlog creation and refinement.
This presentation is a drive through these various boards and canvas that should be designed in prior to any product development: the Product Vision, the Lean Canvas, The Product Definition and the Story Map.
The second lecture in the HIT Lab NZ Design Thinking class on understanding and empathising with end users.
Taught by Mark Billinghurst at the University of Canterbury on December 10th 2013.
Product roadmaps are an important product management tool. But traditionally, they map features onto a timeline that often extends many months into the future. This makes them hard to apply in an agile context where change and uncertainty are present. My talk shows how you can use agile product roadmaps, roadmaps that describe the value the product should create, align the stakeholders and development teams, and unburden the product backlog while avoiding premature commitments and preserving the ability to inspect and adapt.
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
If you are not confident about the fundamentals I would recommend you to take up Data structures and algorithms training in Bangalore, the institute which I found to be the best one is Tutort Academy.
Top 10 Interview Questions for Coding Job.docxSurendra Gusain
Hello everyone!! Today’s blog topic is ‘Top 10 Interview Questions for Coding Job.’ Questions related to programming and coding are a crucial part of a developer’s position interview. If you want to succeed, you need to be familiar with the fundamental concepts of coding and programming. Your coding skills play a huge factor in increasing your chances of hiring in the interview process. Coding is an excellent field with various career opportunities within the country or even abroad but it also means it has lots of competition which makes the whole interview process quite challenging.
Top 10 Interview Questions for Coding Job.docxSurendra Gusain
Hello everyone!! Today’s blog topic is ‘Top 10 Interview Questions for Coding Job.’ Questions related to programming and coding are a crucial part of a developer’s position interview. If you want to succeed, you need to be familiar with the fundamental concepts of coding and programming. Your coding skills play a huge factor in increasing your chances of hiring in the interview process. Coding is an excellent field with various career opportunities within the country or even abroad but it also means it has lots of competition which makes the whole interview process quite challenging.
Google Interview Questions Divided In Following EIGHT
Areas ?
[1]. General Areas Questions
[2]. PAST EXPERIENCE AREAS Questions
[3]. Algorithms Questions
[4]. Coding Questions
[5]. TECHNICAL AREAS Questions
[6]. TEST AREAS Questions
[7]. THOUGHT PROCESS Questions
[8]. PROFESSIONAL’S DEFINITION
In a whiteboard interview, your goal should be to convince the manager that you will be a positive influence on the team and contribute to the team's success. This guide will help you set the right mindset, ask the right questions, and showcase your strengths.
Cloudera Data Science Challenge 3 Solution by Doug NeedhamDoug Needham
This is my solution for the Cloudera Data Science Challenge 3. I use Spark MLLib for problem1, and Spark GraphX for problem3. Problem2 is "simple" streaming map-reduce.
Applying AI to software engineering problems: Do not forget the human!University of Córdoba
The application of artificial intelligence (AI) to software engineering (SE)-problem-solving has been around since the 80s when expert systems were first used. However, it is during the last 10 years that there has been a peak in the use of these techniques, first based on search and optimisation algorithms such as metaheuristics, and later based on machine learning algorithms. The aim is to help the software engineer to automate and optimise tasks of the software development process, and to use valuable information hidden in multiple data sources such as software repositories to execute insightful actions that generate improvements in the performance of the overall process. Today, the use of AI is trendy, and often overused as it could generate artificial results since it does not consider the subjective nature of the software development process requiring the experience and know-how of the engineer. With this Invited Talk, we will discuss different proposals to incorporate the human into the decision-making process in the application of AI for SE (AI4SE), from interactive algorithms to the generation of interpretable models or explanations.
The I in PRIMM - Code Comprehension and QuestioningSue Sentance
Slides from a talk given at the CAS London conference on 29th February 2020. Discusses the teaching of computer programming using PRIMM and in particular, the Investigate stage. Looks at the Block Model and how we can explore students' understanding by asking a range of different questions.
Microsoft interview questions Microsoft sde sdet jobs Microsoft CareersSumit Arora
Microsoft Interview Questions for SDET/SDE jobs divided In following eight areas ?
[1]. General Areas Questions
[2]. PAST EXPERIENCE AREAS Questions
[3]. Algorithms Questions
[4]. Coding Questions
[5]. TECHNICAL AREAS Questions
[6]. TEST AREAS Questions
[7]. THOUGHT PROCESS Questions
[8]. PROFESSIONAL’S DEFINITION
Microsoft SDET
We are working on many interesting changes to our services and building a next generation of test infrastructure to take quality assurance of our offering to a new level. You will work on defining test strategy for your owned areas, write automation and run tests. In addition, you will work on the product code base to improve its test-ability, diagnostic-ability, debug-ability and overall product health for the storage system. You will get hands-on experience with Performance, Scalability and Service Diagnostic of a distributed system.
Microsoft SDE
Our software engineering profession is a collection of disciplines responsible for designing, developing, and delivering our products. Work here and you’re on top of the world of technology, collaborating with brilliant people on projects with the potential for a lasting legacy. Developers (Software Development Engineers – SDEs) write the code—C, C++, C#, and other programming languages—that turns concepts into new technologies and services. We are experts in feature design and feasibility, and we collaborate with program managers and test engineers to define features and ensure quality.
Salesforce Architect Group, Frederick, United States July 2023 - Generative A...NadinaLisbon1
Joined our community-led event to dive into the world of Artificial Intelligence (AI)! Whether you were just starting your AI journey or already familiar with its concepts, one thing was certain: AI was reshaping the future of work. This enablement session was your chance to level up your skills and stay ahead in that rapidly evolving landscape.
As AI news continues to dominate headlines, it's natural to have questions and concerns about its impact on our lives. Will AI take over human jobs? Will it render us obsolete? Rest assured, the outlook is far brighter than you may think. Rather than replacing humans, AI is designed to enhance our capabilities and work alongside us. It won't be replacing marketers, service representatives, or salespeople—it will be empowering them to achieve even greater results. Companies across industries recognize this potential and are embracing AI to unlock new levels of performance.
During this enablement session, you'll have the opportunity to explore how AI advancements can positively influence your professional journey and daily life. We'll debunk common misconceptions, address fears, and showcase real-world examples of how successful AI implementation leads to workforce augmentation rather than replacement. Be prepared to gain valuable insights and practical knowledge that will help you navigate the AI landscape with confidence.
Mastering Data Engineering: Common Data Engineer Interview Questions You Shou...FredReynolds2
Whether you’re a beginner to big data looking for a Data Engineering employment or an experienced Data Engineer looking for new options, preparing for an upcoming interview can be frightening. Given the market’s competitiveness, you must be well-prepared for your interview. Moreover, Interviewing for any position can be nerve-wracking. Data engineer positions in the technology industry can be highly competitive. Numerous individuals are drawn to these professions because they are in high demand, pay well, and have positive long-term job growth.
A slide about Pragmatic Approaches, such as, Evils of Duplication, Orthogonality, Reversibility, Tracer Bullets, Prototypes and Post-it Notes, Domain Languages and Estimating.
Source : A Pragmatic Programmer, written by Andrew Hunt and David Thomas.
Large software projects cannot be built without some amount of analysis and design. But not all parts of the system require the same amount of design. Some may not require any upfront design at all. Others require a few minutes of architecture discussion; some require weeks of analysis, documents and review. A balance is necessary: too much design and you're delaying the project; too little and you will add technical debt which you'll have to pay in future rewrites and painful maintaining.
How do we decide when design is needed and how much of it is needed? How do other Agile projects do it?
In this talk I discuss what the Agile literature has to say about architecture and how we can answer this question.
Similar to Google Interview Prep Guide Software Engineer (20)
P&G Memo: Creating Modern Day Brand ManagementLewis Lin 🦊
Neil H. McElroy's memo on dedicated brand departments at P&G McElory's famous memo which lead to dedicated brand teams at P&G. Also famous for breaking P&G's "one page memo" rule!
30-Day Facebook PM Interview Study GuideLewis Lin 🦊
Excerpt from Lewis C. Lin's The Product Manager Interview https://interviewsteps.com/products/the-product-manager-interview-167-actual-questions-and-answers
Want to move your career forward? Looking to build your leadership skills while helping others learn, grow, and improve their skills? Seeking someone who can guide you in achieving these goals?
You can accomplish this through a mentoring partnership. Learn more about the PMISSC Mentoring Program, where you’ll discover the incredible benefits of becoming a mentor or mentee. This program is designed to foster professional growth, enhance skills, and build a strong network within the project management community. Whether you're looking to share your expertise or seeking guidance to advance your career, the PMI Mentoring Program offers valuable opportunities for personal and professional development.
Watch this to learn:
* Overview of the PMISSC Mentoring Program: Mission, vision, and objectives.
* Benefits for Volunteer Mentors: Professional development, networking, personal satisfaction, and recognition.
* Advantages for Mentees: Career advancement, skill development, networking, and confidence building.
* Program Structure and Expectations: Mentor-mentee matching process, program phases, and time commitment.
* Success Stories and Testimonials: Inspiring examples from past participants.
* How to Get Involved: Steps to participate and resources available for support throughout the program.
Learn how you can make a difference in the project management community and take the next step in your professional journey.
About Hector Del Castillo
Hector is VP of Professional Development at the PMI Silver Spring Chapter, and CEO of Bold PM. He's a mid-market growth product executive and changemaker. He works with mid-market product-driven software executives to solve their biggest growth problems. He scales product growth, optimizes ops and builds loyal customers. He has reduced customer churn 33%, and boosted sales 47% for clients. He makes a significant impact by building and launching world-changing AI-powered products. If you're looking for an engaging and inspiring speaker to spark creativity and innovation within your organization, set up an appointment to discuss your specific needs and identify a suitable topic to inspire your audience at your next corporate conference, symposium, executive summit, or planning retreat.
About PMI Silver Spring Chapter
We are a branch of the Project Management Institute. We offer a platform for project management professionals in Silver Spring, MD, and the DC/Baltimore metro area. Monthly meetings facilitate networking, knowledge sharing, and professional development. For event details, visit pmissc.org.
The Impact of Artificial Intelligence on Modern Society.pdfssuser3e63fc
Just a game Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?
Exploring Career Paths in Cybersecurity for Technical CommunicatorsBen Woelk, CISSP, CPTC
Brief overview of career options in cybersecurity for technical communicators. Includes discussion of my career path, certification options, NICE and NIST resources.
New Explore Careers and College Majors 2024.pdfDr. Mary Askew
Explore Careers and College Majors is a new online, interactive, self-guided career, major and college planning system.
The career system works on all devices!
For more Information, go to https://bit.ly/3SW5w8W
1.
Google Interview Prep Guide
Software Engineer
What’s a Software Engineer (SWE)?
Software Engineers (referred to as “SWEs”) at Google develop the next-generation technologies that change
how millions of users connect, explore and interact with information and one another. As a SWE, you’ll be
responsible for the whole lifecycle of a project critical to Google’s needs, with opportunities to switch teams
and projects as you and our fast-paced business grow and evolve. Depending upon the project you join, you
could be involved in research, design, planning, architecture, development, test, implementation and release
phases. You'll be working on products that handle information at a massive scale, bringing fresh ideas from
all areas and tackling new problems across the full-stack as we continue to push technology forward.
Why Google? Impact.
Google is and always will be an engineering company. We hire people with a broad set of technical skills
who are ready to tackle some of technology's greatest challenges and make an impact on millions, if not
billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive
scalability and storage solutions, large-scale applications and develop entirely new platforms around the
world. From AdWords to Chrome, Android to YouTube, Cloud to Maps, Google engineers are changing the
world one technological achievement after another.
2.
General Interview Tips
Explain: We want to understand how you think, so explain your thought process and decision making
throughout the interview. Remember we’re not only evaluating your technical ability, but also how you
approach problems and try to solve them. Explicitly state and check assumptions with your interviewer to
ensure they are reasonable.
Clarify: Many of the questions will be deliberately open-ended to provide insight into what categories and
information you value within the technological puzzle. We’re looking to see how you engage with the
problem and your primary method for solving it. Be sure to talk through your thought process and feel free to
ask specific questions if you need clarification.
Improve: Think about ways to improve the solution you present.It’s worthwhile to think out loud about your
initial thoughts to a question. In many cases, your first answer may need some refining and further
explanation. If necessary, start with the brute force solution and improve on it — just let the interviewer know
that's what you're doing and why.
Practice: You won’t have access to an IDE or compiler during the interview so practice writing code on paper
or a whiteboard. Be sure to test your code and ensure it’s easily readable without bugs. Don’t stress about
small syntactical errors like which substring to use for a given method (e.g. start, end or start, length) — just
pick one and let your interviewer know.
The Technical Phone Interviews
Your phone interview will cover data structures and algorithms. Be prepared to write around 20-30 lines of
code in your strongest language. Approach all scripting as a coding exercise — this should be clean, rich,
robust code.
1. You will be asked an open ended question. Ask clarifying questions, devise requirements.
2. You will be asked to explain it in an algorithm.
3. Convert it to a workable code.(Hint: Don't worry about getting it perfect because time is limited.
Write what comes but then refine it later. Also make sure you consider corner cases and edge
cases, production ready.)
4. Optimize the code, follow it with test cases and find any bugs.
google.com/careers
3.
The Coding & Algorithm Interviews
Coding: You should know at least one programming language really well, preferably C++, Java, Python, Go,
or C. You will be expected to know APIs, Object Orientated Design and Programming, how to test your code,
as well as come up with corner cases and edge cases for code. Note that we focus on conceptual
understanding rather than memorization.
Algorithms: Approach the problem with both bottom-up and top-down algorithms. You will be expected to
know the complexity of an algorithm and how you can improve/change it. Algorithms that are used to solve
Google problems include sorting (plus searching and binary search), divide-and-conquer, dynamic
programming/memoization, greediness, recursion or algorithms linked to a specific data structure. Know
Big-O notations (e.g. run time) and be ready to discuss complex algorithms like Dijkstra and A*. We
recommend discussing or outlining the algorithm you have in mind before writing code.
Sorting: Be familiar with common sorting functions and on what kind of input data they efficient or not.
Think about efficiency means in terms of runtime and space used. For example, in exceptional cases
insertion-sort or radix-sort are much better than the generic QuickSort/MergeSort/HeapSort answers.
Data Structures: You should study up on as many data structures as possible. Data structures most
frequently used are arrays, linked lists, stacks, queues, hash-sets, hash-maps, hash-tables, dictionary, trees
and binary trees, heaps and graphs. You should know the data structure inside out, and what algorithms
tend to go along with each data structure.
Mathematics: Some interviewers ask basic discrete math questions. This is more prevalent at Google than
at other companies because counting problems, probability problems and other Discrete Math 101
situations surround us. Spend some time before the interview refreshing your memory on (or teaching
yourself) the essentials of elementary probability theory and combinatorics. You should be familiar with
n-choose-k problems and their ilk.
Graphs: Consider if a problem can be applied with graph algorithms like distance, search, connectivity,
cycle-detection, etc. There are three basic ways to represent a graph in memory (objects and pointers,
matrix, and adjacency list) — familiarize yourself with each representation and its pros and cons. You should
know the basic graph traversal algorithms, breadth-first search and depth-first search. Know their
computational complexity, their tradeoffs and how to implement them in real code.
Recursion: Many coding problems involve thinking recursively and potentially coding a recursive solution.
Use recursion to find more elegant solutions to problems that can be solved iteratively.
google.com/careers
4.
The System Design Interviews
Operating Systems: You should understand processes, threads, concurrency issues, locks, mutexes,
semaphores, monitors and how they all work. Understand deadlock, livelock and how to avoid them. Know
what resources a process needs and a thread needs. Understand how context switching works, how it's
initiated by the operating system and underlying hardware. Know a little about scheduling. We are rapidly
moving towards multi-core, so know the fundamentals of "modern" concurrency constructs.
System Design: System design questions are used to assess a candidate's ability to combine knowledge,
theory, experience and judgement toward solving a real-world engineering problem. Sample topics include
features sets, interfaces, class hierarchies, distributed systems, designing a system under certain
constraints, simplicity, limitations, robustness and tradeoffs. You should also have an understanding of how
the internet actually works and be familiar with the various pieces (routers, domain name servers, load
balancers, firewalls, etc.). For information on system design, check out our research on distributed systems
and parallel computing.
Resources
Books
Cracking the Coding Interview
Gayle Laakmann McDowell
Programming Interviews Exposed: Secrets to Landing Your Next Job
John Mongan, Eric Giguere, Noah Suojanen, Noah Kindler
Programming Pearls
Jon Bentley
Introduction to Algorithms
Thomas Cormen, Charles Leiserson, Ronald Rivest, Clifford Stein
Interview Prep
How we hire
Interviewing @ Google
Candidate Coaching Session:Tech Interviewing
CodeJam: Practice & Learn
Technical Development Guide
About Google
Company - Google
The Google story
Life @ Google
Google Developers
Open Source Projects
Github: Google Style Guide
Google Publications
The Google File System
Bigtable
MapReduce
Google Spanner
Google Chubby
google.com/careers