There are many types of jobs in any large organization. Google has many software engineering positions, at many levels. They include coding in all of Google’s projects and products as well as research, data collection, software testing, and more.

Product managers and program managers are part of almost every project, and people management is also important. Administrative assistants, human resources, payroll, and all the other functions of any big enterprise are filled by people with many backgrounds. Other areas of importance include sales, marketing, advertising, customer service, legal, communications, etc. And of course the people who take care of us such as cooks, maintenance workers, technical support, security, etc.

Some offices have engineering centers, but many are sales or business offices.

Go to Bring questions. Build answers. - Google Careers to learn more

Google hires for thousands upon thousands of different job roles, from project management, to executive assistant, to lifeguard at the "infinity pools", to lawyer, to salesperson, to finance person, to machinists, to the person who puts the coyote urine on the fake coyotes on the "Garfield" fake coyotes to keep the ground squirrels from digging up the soccer field.

In other words, it's a major corporation with facilities and many, many job roles.

Figure out what you want to do in life, and work at being good at that. Once you are, there's probably a job at Google where you can apply your skills.

To increase your chances of getting a job at Google, it's important to focus on building a strong foundation in programming and computer science concepts. While Google has a diverse range of roles and technologies, here are some key programming languages and concepts to prioritize:

1. Python: Python is widely used at Google and is considered one of the main programming languages for various projects. It is known for its simplicity, readability, and extensive library support. Learning Python will be valuable for both backend and data-related roles.
2. Java: Java is another important language at Google, particularly for building scalable and robust enterprise-level applications. It is commonly used in Android development and for server-side programming. Having a solid understanding of Java and its ecosystem can open up opportunities in different areas.
3. C++: C++ is a foundational language for systems programming, and it is highly valued at Google, especially for performance-critical applications. If you're interested in working on low-level systems, infrastructure, or performance optimization, learning C++ will be beneficial.
4. JavaScript: JavaScript is essential for web development and frontend engineering. Google relies heavily on JavaScript for building interactive web applications, and proficiency in JavaScript frameworks like React or Angular can be advantageous.
5. Data Structures and Algorithms: Mastering data structures and algorithms is crucial for technical interviews at Google. Focus on understanding common data structures (arrays, linked lists, trees, graphs, etc.) and algorithms (sorting, searching, graph traversal, dynamic programming, etc.). Solve coding problems and practice implementing these concepts efficiently.
6. Distributed Systems: Google operates at a massive scale, and understanding the principles of distributed systems is valuable. Learn about concepts like distributed computing, scalability, fault tolerance, and network protocols.
7. Cloud Technologies: Google Cloud Platform (GCP) is one of the leading cloud service providers. Familiarize yourself with cloud concepts, infrastructure as a service (IaaS), platform as a service (PaaS), and services offered by GCP. Gain practical experience with deploying applications on the cloud.
8. Data Management and Analytics: Google deals with enormous amounts of data, so knowledge of data management and analytics is beneficial. Familiarize yourself with concepts like SQL, relational databases, NoSQL databases, and data processing frameworks like Hadoop or Spark.
9. Problem-Solving and Critical Thinking: Develop strong problem-solving and critical thinking skills. Practice solving algorithmic coding challenges, improve your ability to analyze and optimize code, and think through complex problems efficiently.
10. Open Source Contributions: Contribute to open source projects, whether it's fixing bugs, adding features, or participating in community discussions. This demonstrates your ability to work collaboratively and showcases your coding skills to potential employers.

Remember that technical skills are just one aspect of securing a job at Google. Building a well-rounded profile with relevant projects, internships, research experience, and strong communication skills is also important. Keep up with the latest industry trends, participate in coding competitions, and network with professionals in the field to increase your visibility and chances of getting noticed by Google recruiters.

Definitely you can get the job in Google by this approach.

You can secure the job in Google by doing intership programme, this is one of the simplest way to get your foot in the door of Google.

If you get an opportunity in Google for doing internship then after that you may get the chance to do permanent job because there are many MNC’s companies which offers post intership programme which consist of Parmanent job.

Try your best to get an opportunity to do intership in the Google, at the same time, if your performance is way good then you may get the chance for post internship programme wherein you can secure full time job in the company like Google.

If you are looking for the intership programme, in that case you should log on to intershala portals wherein you may get the best intership.

I hope this will help you a lot!!!

Although a CS degree is a pretty useful precursor to becoming a software engineer at Google, you'd probably be quite surprised to hear how varied the background is of the rest of us who work at Google and other major tech companies :)

I studied Political Science, Communications, Law, and Business (yeah, one of those hopelessly overeducated chaps). A pretty senior and well-respected manager I know at Google majored in, I believe, Ancient Greek. In fact, we have quite a lot of liberal arts majors. And I am fairly sure (but not positive) that we have quite a few math majors.

Again, with significant exceptions (particularly in software engineering), at least at Google, I believe what you majored in is a heck of a lot less important than:

• the perceived challenge of your class load
• the perceived quality of your school and what you majored in there- your grades- your accomplishments outside the classroom (philanthropic, entrepreneurial, leadership-wise, etc.)
• whether you're someone people believe they'd enjoy and be productive working with
• how well and how quickly you can think

As for specific examples of jobs you would potentially be qualified for: check out http://www.google.com/jobs (as well, of course, as the job sections of other companies' web sites!), particularly the "requirements" section of each listing.

You can pretty much divert yourself into anything computer related once you’re in the field. I started out as a developer for a consulting firm for a software company. I then joined the main software company to become the consultant for their various software to the customers (I basically phased out of development). I then joined another company to do infrastructure for a year. The infrastructure piece was not for me so I transitioned to another area within the company to architect their software. I am now returned to my old company where I do more of a Software sales role. As you can see, I’ve gone all over the place within the computer realm.

I have been a software engineer in the true sense since 1983. Aside from coding I can do carpentry, rebuild my Harley Davidson, change the oil in my truck.

If you mean within my company, I perform a range of tasks including but not limited to writing documentation, maintaining our software library and backups, distributing new releases and doing local testing. I train new employees on software I wrote and pass down what knowledge I can via remote desktop software.

In the late 90s I was manager of virtual engineering at Raining Data (formally Pick Systems). I did little coding myself but assigned work to my team and desk checked their work, managed bug reports and enhancement requests.

If you are a Computer Science Engineer, you can’t avoid coding or programming completely.

There are many kinds of career paths in a typical IT Company (the so-called “Software Company”) - Programmer / Coder / Developer, Tester, Architect, Project Manager, Business Analysts or Consultants (who work on functional requirements), Account Management roles (client facing roles), PMO roles (taking care of billing/recovery, Resource and Space Management, etc.)

Except for Account Management and PMO roles, other roles require understanding and experience in technology (some coding or testing background). Business Analyst / Consultant roles also need some knowledge of technology (to know what you can or cannot do with a certain technology platform)

There are also some technology companies like Intel that may give CS Engineers an opportunity to work in hardware (micro-processors etc.) areas. However, in those jobs also, one may be required to do some amount of coding / programming.

I didn't start programming until college and I still got Google full-time offer. As far as I know there are a lot of Googlers who knew nothing about coding before college and I highly suspect that they are majority. What's more, some folks who are working at top companies like Google/Facebook/Twitter etc. are self-taught programmers or had non-computer-science backgrounds in the past.

So I feel like it's never too late to start programming. More about my experiences: I started programming from computer science classes when I was a freshman at college and before that I've no idea differences between C and C++. After the first semester, I just found myself quite into this field and I began to learn coding as much as I can.

School courses are great ways to get me started, however, most of my coding skills are gained from building different projects (I was quite active on Github). Later on, I successfully landed my internship at various companies like Google, which really broadened my horizon (Special thanks to gainlo.co and leetcode.com, they are really helpful for interview preparation).

With that being said, what really matters about programming is not how early, but how hard. Also I'm a strong believer that you won't be a good programmer unless you love programming and if you really love programming, you will be good at it eventually even if you know nothing at this point.

In addition to web development, there are many other jobs that you may be interested in if you want to become a successful internet professional. These include website design and layout, search engine optimization (SEO), digital marketing, social media management, user experience design (UXD), app development, and more.

By doing your research and knowing what skillset is most applicable for the specific job you're looking for, you can find the perfect position for yourself without having to go through multiple interviews. Additionally, keeping up with current industry trends and staying up-to-date on best practices related to online marketing techniques will make you an invaluable asset in any company's workplace.

There are countless jobs that you can consider outside of web development, depending on your interests and skillset. Here are some examples:

1. Software Engineer: You could develop software applications for desktop, mobile, or cloud platforms.
2. Data Scientist: Analyze and interpret complex data to identify patterns and insights that inform business decisions.
3. UX Designer: Design the user experience of products and services across different platforms, from websites to mobile apps.
4. Digital Marketer: Use a variety of online marketing techniques to promote products, services, or ideas.
5. Graphic Designer: Create visual concepts, using computer software or by hand, to communicate ideas that inspire, inform, or captivate consumers.
6. Cybersecurity Analyst: Protect information systems and networks from cyber attacks by implementing security measures and monitoring for potential threats.
7. Project Manager: Organize and oversee projects from start to finish, ensuring that deadlines are met and budgets are maintained.
8. Sales Representative: Sell products and services to customers, from consumer goods to business-to-business solutions.
9. Medical Practitioner: Provide healthcare services to patients, diagnosing and treating illnesses and injuries.
10. Lawyer: Represent clients in legal matters, advocating for their rights and ensuring that justice is served.

These are just a few examples of jobs that you can pursue other than web development. The possibilities are endless, so take the time to explore your interests and passions to find the career path that is right for you.

I’m going to do my best to answer this question constructively and follow BNBR but it’s going to be a struggle. I get asked questions like this all the time and it has become a pet peeve.

First - learn how to ask quality questions.

Your question provides absolutely no details that would allow someone to write a constructive answer.

• What kind of job do you want?
• What is your background?
• What is it about Google that makes you want to work there?
• What have you already done to prepare for getting a job at Google?

The art of asking good questions (and it is an art) is important to almost any job, but is especially critical if you want to get into fields like engineering.

So my first piece of advice would be to work on improving your skills around asking great questions.

Second - Learn how to research topics

Knowing how to figure things out yourself is also an important life skill. There is a ton of information out there on getting jobs at Google. I think that Google itself might even have a product that would help you find such information.

Do your homework. Read every thing you can find. Think about it.

At that point you will either have an answer to your question, or you will have the foundation of knowledge you need to come back and ask a quality question.

Third - Don’t treat it as a game

Understand why you want to work at Google. I think Google is an amazing place to work, but it’s not for every one. Make sure you understand why you want to work for Google, what you want to get out of it and what value you bring to the table. If you’re just thinking about getting a job here as an “achievement” to unlock - you’re most likely just going to end up unhappy and waste a bunch of your time and our time.

If you want to work here, do the work to understand what we do and what we look for. If you want to work here and are willing to do the work to make it happen - great - but make sure you’re doing it because you enjoy it and because you believe that the end result will be growing your skills and value in the general sense.

If you treat the process as something you have to endure to win a “prize” please do yourself (and us) a favor and find something else that you will truly enjoy.

The cliched way of saying what I’m saying is make the journey is something you will enjoy and don’t just focus on the destination.

As a side note, asking questions like “What kind of questions will I get asked for the <insert-job-title> interview at <insert-company-name>” are pointless and are the exactly opposite of what I’m talking about.

I thoroughly enjoyed the time I spent preparing for my Google interviews and at no time did I ever feel like the effort was wasted or that it wasn’t helping me become a better engineer.

BTW - my personal favorite article on this topic is still Steve Yegge’s post - Get that job at Google. It’s from 2008 but it’s still - IMO - completely relevant, because it talks about the kinds of general knowledge that we look for instead of focusing on anything trendy or talking about how to “beat” the Google interview.

Just because you don’t like coding doesn’t mean you can’t have a job in big tech companies like Google. There are more jobs which needs thinking , fluent in communication, managing tasks and so on. Here i list some of the domains where no/less coding is done.

Designer : The graphic designer is a person who assembles images, motion graphics into his design and brings his creativity into real life. Google Doodle are designed by the Google Doodle team which has artists, designers, creative thinkers. Note that Doodle are designed for more number of events and also based on the locations. So creativity is enough to survive (in my perspective).

User interface specialist: There are number of roles falls under this category. Everything is done for user interactions , how they interact with the app, website or program. This job need skills like design, Human computer interaction. You use your creativity and diverse range of engineering experience to explore solutions to a variety of engineering problems.

Business Analyst : The Business Analyst works across all internal Sales teams to help them achieve their business objectives by striving for streamlined project completion and overall process improvement. It seems like a customer tells developers their needs and developer creates it, but there are lot to do in this. Their requirements should be understood as a solid pattern and then developers did their tedious part . Some analyzing and talkative people is needed for this position.

Project Manager : In this position, one has to deal the responsibilities similar to Business analyst along with managing the tasks, completing within deadlines and so on. Surfing in net can give more detail than this, as i rarely research in this field.

Technical Writer : As a technical writer working on developer products, you will write conceptual documentation, detailed developer and integration guides, code samples, API references, and tutorials for internal developers. So if you are good in your writing skills and telling the content in a way how people can easily understand about that particular project, then you may get a job.

And finally, having at least a basic understanding of the principles of programming can be very helpful, but for most of these jobs, you won’t need to know more than the basics. This answer is fully based on the analysis done. You can find more than this in internet.

If you spent your precious time in reading my answer and you really find it useful, just press the Upvote button somewhere down to this answer.

My,my. What a question, in fact there are more fields for using computers than you can think of. In manufacturing, there are computers to drive Computer Numerical Controlled machines, for all machine tools, in glass melting computers control the raw material, the fuel you feed. Your dish washer, washing machine, driers all controlled by computers. In your shops the Point Of Sale apart from checking the money, they also manage the stock levels and make orders for more stocks. Soon computers will control what you need in your fridge etc….

OK. What about producing all the hardware, smart phones, smart tablets, smart TVs and self driven cars……

in all these fields you need designers, installers, maintenance technicians and marketing staff.

50% of Google hires come from referrals.

Google gets millions of resumes each year, and overall 1% of these resumes eventually lead to hires. The recruiting organization has a really tough job to identify those 1% in an efficient way. Therefore, like any other efficiency focused organization, they use channel assessment and focus more on known effective channels.

And the most effective channel is internal referrals. The Google internal referral tool will ask the referrer:

• How well do you know this person?
• If the answer to above question is well enough, it will then ask, How good is this person? Select from Top 5%, Top 10%, Top 25%, Top 50%, or Not in Top 50%.
• The referrer can also add text to describe the person.

The top selections with detailed description will get an email from recruiter very quickly, and effectively get ahead of the long line.

But if the selection isn't top, or there's not much referrer notes, it's not much more than self-submission, except for the guarantee that the resume is at least examined by a recruiter.

In short, here's what I would suggest, in order of preference:

1. If you know someone senior at Google and that person knows you well to say good things about you, ask that person to refer you. That's the top option.
2. If you know someone not that senior at Google but the person knows you well to say good things about you, ask that person to refer you. That's the 2nd best option.
3. If you don't know anyone at Google that knows you well and can say good things about you, but you know purely socially someone senior at Google, ask that person to refer you.
4. If you only know purely socially someone junior at Google, still ask that person to refer you. Better than nothing.
5. If you really don't know anyone at Google at all, good luck to try self-submission. Just set the expectation low, since there is a chance that the resume is never looked at.

We know this is really a challenging process for many good candidates but only have #5 or #4 option. For these people, we believe they deserve a better chance and companies like Google also want to give them a better chance. We are building a system that aims to reach the effectiveness of #2 for people who otherwise would be at #5 or #4.

It can be. It can be a slog too, like any other job.

Let’s see, last week I was poking holes in ceilings. This week I’m colouring doors. Before then I was pulling price lists from an asynchronous API and learned about async/await.

Never a dull moment sometimes!

I’ve been doing this for forty years now. When I started, it was machine code and 8/16 bit machines. Now’s its 64 bit, high level languages, double screens etc.

This is my list of jobs I’ve had so far:

• military
• computing
• audio
• games
• oil
• medical
• telecommunications
• CAD (current)

Quite a wide range of jobs. Programming is now everywhere!

Audio and games were the most fun jobs, especially as I played a lot of games. To test the sound cards I worked on, I played games!

I still remember trying to get a 6 channel sound card to work. I was testing a warm reset command and it would keep slipping the channels around. So there I am, in the middle of an open plan office, playing the film Jumangi - where the sound swirls around you, and the MD interrupts me.

“Are you playing that sound for work or for your own amusement?”

“Oh, for work, it helps me test this 6 channel system I’m working on”

“Oh, OK”.

So I carried on playing the swirly sound and decided I had to use cold reset as warm reset didn’t work.

Evil cackle.

Then there was the time when I had to crash a racing car into a wall to test the audio…

While the primary role of a computer programmer is coding, there are several related positions where individuals work in the field of computer programming without extensive hands-on coding. Here are some examples:

1. Technical Project Manager:

Technical project managers coordinate and oversee software development projects. They work closely with development teams, stakeholders, and clients to ensure that projects are completed successfully. While coding knowledge is beneficial, the focus is on project management and communication skills.

2. Business Analyst:

Business analysts bridge the gap between technical teams and non-technical stakeholders. They analyze business processes, gather requirements, and create documentation to guide development projects. While some understanding of coding is helpful, the emphasis is on business acumen and communication skills.

3. Systems Analyst:

Systems analysts evaluate and optimize existing computer systems. They assess business needs, recommend improvements, and collaborate with developers to implement changes. Coding knowledge is useful but not always the primary focus of the role.

4. Technical Writer:

Technical writers create documentation, manuals, and guides for software applications. They translate technical information into user-friendly content. While an understanding of programming concepts is valuable, the main skills needed are writing and communication.

5. Quality Assurance (QA) Analyst:

QA analysts are responsible for testing software to ensure it meets quality standards. They design test cases, execute testing procedures, and report bugs. While coding knowledge can be helpful, QA roles often focus more on testing methodologies and attention to detail.

6. Product Manager:

Product managers are responsible for the overall success of a product, from conception to launch. They collaborate with development teams, prioritize features, and communicate with stakeholders. While technical understanding is beneficial, the role emphasizes strategic thinking and communication.

7. Data Analyst:

Data analysts analyze and interpret data to help organizations make informed decisions. They may work with databases, perform statistical analysis, and create visualizations. While some scripting or coding may be involved, the emphasis is on data analysis skills.

8. Sales Engineer:

Sales engineers help sell complex technical products by explaining their features and benefits to potential clients. They bridge the gap between sales and technical teams. While not directly involved in coding, they need a strong technical understanding of the products they are selling.

9. UX/UI Designer:

User experience (UX) and user interface (UI) designers focus on creating engaging and user-friendly interfaces. While coding skills can be beneficial, the primary emphasis is on design principles, user research, and creating a positive user experience.

10. IT Consultant:

IT consultants provide advice on technology solutions to meet the business needs of clients. While they may have technical expertise, the role involves more consulting, problem-solving, and communication than hands-on coding.

In these roles, while coding knowledge may be helpful, the emphasis shifts toward other skills such as project management, communication, analysis, and strategic thinking. Individuals who enjoy the technical aspects of programming but prefer roles with broader responsibilities may find these positions rewarding.

Originally Answered: What is the least stressful job for a software engineer? I don't want to code all my life. Is there any other specialty that I can do a master’s in and become some sort of manager and not do programming at all?

Note, I can understand the desire not to be a programmer. Programming is finding a solution to a problem and expressing it flawlessly in simple terms that a machine can follow mindlessly and that your fellow programmers can easily comprehend the same. It can be very hard. It is particularly stressful, when the task seems easy to outsiders but actually isn’t for one reason or another. xkcd: Tasks

On becoming a programming manager (project manager) to escape programming:

My apologies. Warning: Note the tone of this section is somewhat strident, because I have worked for managers who didn’t want to program and who probably couldn’t. They tended to be terrible because the didn’t understand why some things took so long and made unreasonable demands. They tended to see all tasks as equal and had no comprehension of what is easy or not.

Yes, you might be able to become a programming manager, but perhaps software engineering is not what you want at all. If you don’t want to program, why would you pick a field based upon programming? You could try becoming a manager, but I will tell you straight out, if you manage programmers and don’t like programming, the programmers will figure it out and make your life hell as a manager, at least as much as they are able.

Stay away from our field if you don’t want to program. We don’t need you [especially not as our boss]. We don’t want you. We don’t want to work for you.

There are, of course, fields in computers that don’t require programming.

• help desk — you need some minimal understanding of the system, but the main thing one needs is the ability to empathize with the customer and remove the emotional content from the complaint, so that the details which can get solved get isolated from the frustration that will hopefully go away when the problem is fixed.
• documentation — more understanding is needed for this as you are likely given some documentation from a programmer that explains some feature in a technically correct but fundamentally unhelpful manner and you need to translate that into how the feature is used to solve a problem in a way that users will understand. Writing skill are the most important here.
• marketing — gathering customer requirements and deciding which ones will gain the largest market share. This requires the least knowledge of the details of programming and most knowledge of the application area. This job moves one into the realm of “business” degrees.
• program management — again, even more understanding is needed, because you will be dealing with schedules. This job is prioritizing and deciding what features are most important to be implemented next. You need understanding of the customers needs and want and to be able to balance that against what the team can deliver. Note that this is different than “project management” (which I talked about first) in that you don’t actually run the team.

There are also fields that aren’t programming “exactly”, but are very much like programming.

• testing/QA — this actually IS programming. It’s just programming to describe how a program should work. It can be simpler than “normal” programming, in that you are often given the parts of the solution and how they fit together. But the assumption that is simpler if often actually wrong. Writing good tests is in some ways often harder than programming, just people don’t want to admit it, because writing simple tests is like simple programming and nearly everyone can “do it”. But often simple tests are like buggy programs, close to useless or worse negative. Good tests, however, are worth their weight in “gold-pressed latinum”.
• SREs — site reliability engineers. The people who keep the production systems running. In the old days, these would often be called System Administrators. It is a whole field in itself. It can be very high stress when something bad happens. It also has huge boring tasks like provisioning systems. Good people in this field actually program and automate their jobs (see automators below). However, they often do it with terrible tools like “bash” (no offense to bash lovers, but it isn’t a good programming language and I wouldn’t wish it on anyone).
• security engineers — people who try to keep hackers out of the system and repair the damage when the hackers get in. This is often a very high stress job, because you don’t know whether something bad has happened or not until it is too late.
• tool builders/automators — people who build tools to make programmers/testers/SREs etc. more productive. This is definitely programming, but your arget audience is people who understand programming (not customers who think it is magic). At one end of the spectrum, people who write compilers/OSes and related fields are simply very specialized programmers.
• database administrators (and related fields) — I haven’t worked
• software architects — programmers who have mastered the craft to the point that they aren’t allowed to program any more. Just kidding, but only slightly. Lay out the overall design of a system (and sometimes programs the critical part).
• technical leads — programmers who run projects but still program (some, perhaps only little). Note this is slightly different from programming managers who may be more on the administrative side. A good management team has a “people manager” who deals with people and administrative issues but not schedules and a technical lead who guides the team and keeps it on track and is responsible in the end for the schedule and overall success of the product technically. When the technical lead says the project will be late, people need to trust their judgement, as they are the only ones who understand how hard the different parts are. The only questions should be, “Is there something that can be done?” (and if no, accept it) and if yes, “What do you need?” A good technical lead is usually a very good programmer, but not a micro-manager. As in, they understand what the team members are doing, but know when to trust them to do it.