Google has opened an early-consideration application window for its Summer 2027 Software Engineering Internships in the United States. Separate applications exist for bachelor's and master's students, and the anticipated deadline is July 24, 2026 — but Google reviews applications on a rolling basis and may close postings earlier if projects fill.
Direct application links
- Bachelor's: Software Engineering Intern, BS, Summer 2027
- Master's: Software Engineering Intern, MS, Summer 2027
Use the application that matches the degree you'll be pursuing during the internship recruiting process.
The most important thing to know
This is an early-consideration window, not necessarily your only opportunity to apply for Google's Summer 2027 internships. Google states that the same applications will reopen during its regular fall recruiting cycle. Students who can submit a strong application now should do so immediately — but students who are genuinely unprepared may have another opportunity later.
Do not use the fall reopening as a reason to procrastinate. Early consideration may give you access to projects before more positions fill.
Deadline
Google lists an anticipated application deadline of July 24, 2026. However, Google explicitly warns that postings may close earlier if all available projects become full. Do not assume you can safely wait until the evening of July 24.
Who can apply?
Bachelor's internship
Intended for students in all academic years pursuing a bachelor's degree in computer science or a related field.
Minimum qualifications:
- Pursuing a bachelor's degree, postsecondary program, or technical training focused on software development or another technical field
- Experience coding in at least two general-purpose programming languages
- Experience with data structures or algorithms through school, work, projects, or another setting
Google lists C, C++, Java, JavaScript, and Python as examples of qualifying programming languages.
Freshmen and sophomores should not automatically disqualify themselves. The posting specifically says students from all academic years may be considered.
Master's internship
Intended for students in all academic years pursuing a master's degree in computer science or a related field. Minimum qualifications are similar to the BS role, with a preference for candidates returning to a degree program after the internship.
Preferred qualifications
Google prefers candidates who can work full time for approximately 12 weeks outside their university term, with experience in areas like:
- Artificial intelligence and machine learning
- Infrastructure
- Web application development
- Unix or Linux
- Mobile application development
- Distributed and parallel systems
- Information retrieval
- Natural language processing
- Networking
- Large software systems
- Security software development
These are preferred, not required. Meaningful experience in one or two areas can still strengthen your application.
What you need to apply
- An updated résumé or CV (PDF preferred)
- A current official or unofficial transcript in English (PDF preferred)
Attach your transcript in the education section. Google instructs applicants to select "Now attending" under degree status to upload it. A cover letter is not required.
What the internship involves
A paid internship lasting approximately 12–14 weeks. Interns may be considered for either Software Engineering or Site Reliability Engineering work, based partly on résumé fit.
Software engineering interns may:
- Design, test, deploy, and maintain software
- Work on a project connected to an active Google engineering need
- Apply CS concepts to real-world problems
- Develop scripts that automate routine tasks
- Analyze technical information and evaluate solutions
- Collaborate with engineers, managers, and other teams
SRE interns may work on reliability, performance, automation, monitoring, troubleshooting, and infrastructure that keeps large systems operational.
Available locations
Postings include 30+ U.S. locations, including:
Mountain View, Atlanta, Austin, Boulder, Cambridge, Bellevue, Chicago, Houston, Irvine, Kirkland, Los Angeles, Madison, New York, Palo Alto, Portland, Pittsburgh, Raleigh, Durham, Reston, Redmond, Redwood City, San Diego, Goleta, San Bruno, Seattle, San Francisco, San Jose, Santa Cruz, South San Francisco, and Sunnyvale. The role may also be located at Playa Vista, California.
Applicants must be located in the U.S. for the duration of the internship. Only select locations you'd realistically work in, but staying flexible increases your chance of a project match.
How to optimize your résumé
1. Clearly list at least two programming languages
Do not bury languages inside project descriptions. Include a technical skills section:
Languages: Python, Java, C++, JavaScript
Frameworks: React, Node.js, Flask
Tools: Git, Linux, Docker, Google Cloud
Only list technologies you could comfortably discuss in an interview.
2. Show evidence of data structures and algorithms
Demonstrate this through relevant coursework, competitive programming, technical projects, research, TA experience, internships, open-source contributions, or independent work.
Relevant coursework may include: Data Structures and Algorithms, Object-Oriented Programming, Operating Systems, Computer Architecture, Database Systems, Discrete Mathematics, Machine Learning, and Computer Networks.
3. Prioritize projects with technical depth
Weak:
Built a web application using Python and React.
Stronger:
Built a full-stack scheduling platform using React, Python, and PostgreSQL, implementing role-based authentication and reducing average database response time by 35% through query optimization.
Use numbers when they're accurate and meaningful — users, latency, requests processed, test coverage, model accuracy, runtime improvements, data volume, or time saved.
4. Match Google's preferred technical areas
Don't stuff keywords. Instead, make legitimate experiences explicit:
- ML project → model, dataset, evaluation method, result
- Web project → architecture, backend, database, deployment, performance
- Systems project → concurrency, networking, OS, scalability, reliability
- Mobile project → platform, framework, users, functionality
- Infrastructure project → automation, deployment, monitoring, containers, cloud, tooling
5. Put your strongest technical evidence near the top
Typical order: Education → Technical Skills → Experience → Projects → Leadership/Activities. Students with substantial technical work experience may place experience above education.
6. Keep the formatting simple
Use: one-column layout, standard section headings, consistent dates, readable typography, concise bullets, PDF format, active verbs, clear technical terminology.
Avoid: skill-rating bars, headshots, excessive colors, dense paragraphs, decorative graphics, multi-column layouts, generic objective statements.
One page is generally appropriate for undergrads. Master's students with substantial research may reasonably need more space — but every line should still be relevant.
What if you don't have a previous internship?
Apply anyway. Previous internship experience is not a minimum qualification. Your projects will carry more weight if they show independent decision-making, technical complexity, real users, collaboration, testing, deployment, and measurable improvements. Two substantial projects are more persuasive than six tutorial projects.
Should you wait for a referral?
Do not miss the application window waiting for a referral. A referral can help but can't compensate for a weak résumé or guarantee an interview. If you know a Google employee who can credibly speak about your work, contact them promptly. Regardless of the response, submit before the role closes.
Application best practices
Apply before making endless revisions. Because Google reviews applications on a rolling basis and may close roles early, minor wording changes are counterproductive. Complete one focused review, correct substantive issues, and submit.
Use professional filenames:
FirstName_LastName_Resume.pdfFirstName_LastName_Transcript.pdf
Avoid resume-final-final2.pdf, google_resume_NEW.pdf, or screenshot1234.pdf.
Review before submitting: graduation date, degree level, contact info, résumé version, transcript readability, location preferences, working links, employment dates, and accurate skills.
Do not exaggerate your skills. Every technology, language, or project on your résumé may become an interview topic. Meaningful experience with three or four languages is more credible than "advanced" in ten.
How to prepare if you receive an interview
Start technical prep immediately rather than waiting for an invitation.
Core data structures
Arrays and strings, hash maps and sets, linked lists, stacks and queues, trees, heaps, graphs.
Core algorithms
Sorting and searching, BFS, DFS, recursion, binary search, sliding window, two-pointer, dynamic programming, greedy algorithms, basic graph algorithms.
During practice
Train yourself to:
- Restate the problem
- Ask clarifying questions
- Discuss a basic solution
- Improve the solution
- Explain your chosen data structure
- Write clean code
- Test normal and edge cases
- Analyze time and space complexity
- Correct mistakes without becoming flustered
Interviewers need to understand how you reason — solving silently isn't enough.
A practical seven-day preparation plan
- Day 1: Submit the application. Finalize résumé, download transcript, save the JD.
- Day 2: Assess your current level with easy and medium algorithm problems. Record weak topics.
- Day 3: Arrays, strings, and hash maps. Practice explaining reasoning aloud.
- Day 4: Trees and graphs. Practice traversal, recursion, BFS, DFS.
- Day 5: For every problem, state time complexity, space complexity, edge cases, and alternative approaches.
- Day 6: Complete at least one timed mock interview without AI assistance.
- Day 7: Behavioral prep — a difficult technical problem, a project failure, a disagreement, a fast-learn moment, a system improvement, a decision with incomplete information.
Common application mistakes
- Waiting until the deadline. July 24 is anticipated, not guaranteed.
- Applying to the wrong degree-level posting.
- Forgetting the transcript.
- Listing technologies without proof.
- Vague bullets. "Worked on," "helped with," and "responsible for" conceal your contribution.
- Assuming freshmen are unqualified. All academic years may be considered.
- Treating preferred qualifications as mandatory.
- Submitting an unreadable transcript. Open the PDF first.
Frequently asked questions
Is this only for juniors? No. Both postings are intended for students in all academic years.
Do I need to be a CS major? Computer science or a related technical field. Coursework and experience should clearly demonstrate software-engineering preparation.
Do I need to know multiple programming languages? Yes — at least two general-purpose languages.
Is there a GPA requirement? Not listed.
Do I need a previous internship? No.
Official transcript required? No. Official or unofficial in English is accepted.
How long to hear back? May take more than 90 days. After three months without a response, Google says it likely proceeded with other candidates — though a recruiter may still reach out about a different match.
What if I miss this window? Applications reopen during Google's regular fall recruiting cycle.
Final application checklist
- Selected the correct BS or MS application
- Updated résumé
- At least two programming languages you genuinely know
- Data structure or algorithm experience shown
- Strongest technical projects included
- Results quantified where possible
- Readable transcript downloaded
- Both documents converted to PDF
- Realistic location preferences selected
- Graduation date checked
- Portfolio, GitHub, and LinkedIn links tested
- Application proofread
- Submitted before the position closes
Final advice
Do not reject yourself before Google reviews your application. You don't need to satisfy every preferred qualification, attend a particular university, or have a major technology internship. You do need credible evidence that you can write software, understand foundational CS concepts, learn quickly, and contribute to a team. Prepare a focused application, submit it early, and begin interview preparation immediately.