1. LandOffer
  2. Blog
  3. All articles
  4. Google US IT Apprenticeship: Check Degree Eligibility and the Application Window

Job search

Google US IT Apprenticeship: Check Degree Eligibility and the Application Window

Check the closed US IT cohort, compare degree and practical-experience guidance, and separate indexed role text from the current application route.

10 min readLandOffer team

Google's US Information Technology apprenticeship is currently a program to monitor, not an open application to prepare for immediate submission. On October 13, 2026, its official overview marked the 2027 cohort closed, and the linked role showed “Job not found.” Before a future opening, compare your degree field, enrollment and relevant practical experience with the current guidance, including the separate condition for Associate's degrees.

LandOffer publishes this guide and offers recent job discovery. We inspected Google's public overview, its US degree FAQ and the linked job route. We also compared a search-indexed copy of the previous role with the actual page. We did not apply, upload documents, contact recruiting or determine anyone's eligibility. The people and records below are fictional teaching examples.

Save an accurate background record and mark this lead as a closed cohort to monitor. A future start date in an indexed title does not keep the application window open. Equally, “no degree required” would not mean every degree and amount of prior experience fits this particular route.

Conceptual IT learning workbench beside a closed intake window; equipment and a work record represent preparation while the application period is closed, not an available Google position.

Separate the cohort's start from its application deadline

The current apprenticeship overview labels the US IT track as eighteen months and says applications for the 2027 cohort are closed. Following its role link led to a missing-job message. That combination is a concrete reason not to describe this as a current application opportunity.

A search-indexed official copy still displayed the title Information Technology Apprenticeship, February 2027 Start, alongside a September 21, 2026 application deadline and an Apply label. That indexed material concerns a previous application window. Its apparent availability differed from the page we actually opened. We do not know the reason the individual role was taken down.

Leo is a fictional reader who saved that indexed result because February 2027 sounded comfortably far away. His completed check separates the cohort start, application deadline and current destination.

Field in Leo's completed record Evidence he preserves Classification
Cohort identifier February 2027 in the indexed role title Intended start, not an application deadline
Listed deadline Before September 21, 2026 in the indexed copy Already past when checked October 13
Current program card 2027 applications closed Closed cohort to monitor
Linked role Job not found on the actual destination No verified live application route
Following cohort No verified date in the reviewed information Unknown; do not invent a reopening month

Leo's original note, “Prepare application before February,” uses the start as the deadline. He replaces it with, “Closed 2027 IT cohort; monitor the official overview for a new role and window.” He keeps the role outside his application-ready list and continues looking for open opportunities. The saved lead does not establish a submission or rejection.

The title also preserves the country and profession. A Google apprenticeship elsewhere, or in a different track, does not reopen this US IT cohort. Keep those identifiers attached when looking at future announcements so a different country's education model does not silently replace the opportunity you were researching.

Read the degree field and degree level together

The current US apprenticeship FAQ distinguishes same-field bachelor's study from a degree in another subject. It says people enrolled in or graduated from a bachelor's program in the apprenticeship field would not be eligible under that guidance. A different subject can be considered with fewer than twelve months of practical experience in the field.

The same answer gives an Associate's-degree branch: enrolled students or graduates may apply with fewer than six months of practical experience in that field. That narrower condition matters. Do not flatten both branches into “under a year of experience” when assessing which questions you need to resolve.

Keep the exact qualification visible. Bachelor's, Associate's, certificate, incomplete study and independent learning are different records. The subject matters as well as the level. An unrelated degree is not automatically an exclusion, while calling every qualification simply a degree can conceal the distinction the FAQ asks you to make.

The indexed IT posting gave additional past-role wording: it excluded current or completed bachelor's, master's or PhD programs in an IT-related field, named examples including Information Systems and System Administration, and required less than one year of relevant IT experience. These are useful historical details, not verified requirements for a new cohort.

The current Associate-specific FAQ should not be overridden by a broader condition in an indexed old role. If a new requisition presents inconsistent wording, preserve both passages and ask which condition applies to that particular role. An attractive general sentence is not an exception you can award yourself.

Five fictional backgrounds expose the important differences

Ren has a completed history bachelor's degree and five months of practical IT work. He keeps both facts in his record. The unrelated subject is a reason to investigate further under the FAQ, rather than conclude that every bachelor's holder is excluded. He still has no open cohort to apply to and no employer determination that all requirements are met.

Jules is currently pursuing an Information Systems bachelor's degree. She should not read “no college experience necessary” as permission to ignore current same-field study. Under the reviewed guidance, her starting record points her toward other suitable routes, including relevant internship or graduate opportunities when their actual conditions fit.

Cal completed an IT Associate's degree and has seven months of practical experience in the same field. A casual reading of the indexed role's one-year condition might look favorable. The Associate-specific FAQ changes that reading: seven months does not sit below six. Cal records the conflict instead of marking himself eligible. Exactly six months would also fail a strictly fewer-than-six-month comparison; it is not an inclusive maximum.

Nadi has an IT Associate's degree and four months of relevant practical experience in this simplified case. Four is below six, so that one comparison does not create the obstacle present in Cal's record. It does not prove Nadi satisfies all conditions, establish how Google would count her activities or make the closed cohort open.

Bo holds an economics bachelor's degree and has fourteen months of relevant IT experience. The unrelated degree does not remove the separate experience condition. He keeps his work accurately described and investigates roles that fit his current experience. More experience can support a different search even when this particular entry route no longer fits.

Fictional record Completed preparation judgment What remains unresolved
Ren: history bachelor's, five IT months Unrelated degree is not itself a blanket exclusion Actual next-role requirements and counting
Jules: current Information Systems bachelor's Same-field degree study is a material obstacle under reviewed guidance Which alternative opening fits her enrollment
Cal: IT Associate's, seven practical months Does not meet the narrower FAQ's under-six-month condition Any new role's authoritative clarification
Nadi: IT Associate's, four practical months Worth checking further; that count is below six Full requirements, counting method and open window
Bo: economics bachelor's, fourteen IT months Experience exceeds the reviewed general boundary Other roles matching his actual experience

The table is deliberately simplified. Part-time work, mixed responsibilities, overlapping activities and volunteer experience can raise counting questions. Save the dates, duties and arrangement; do not manufacture full-time-equivalent months from a formula the employer has not supplied. A precise uncertainty is more useful than an unsupported total.

If your subject is adjacent to IT, keep its actual title and enough context to explain the curriculum. Do not assume this article can classify every Computer Science, engineering or interdisciplinary qualification. A future role's field definition and the employer's clarification are the relevant sources for that decision.

Illustrative open reference book labeled Associate Branch compares four months below six with seven months above six; these examples explain one FAQ condition, not an overall eligibility decision.

Decide whether the IT work fits the career you want

The indexed IT role described device setup, hardware and software troubleshooting, network or cloud systems and end-user support. That is a useful picture of the track being discussed. It should not be repackaged as a software-engineering apprenticeship merely because some process improvement can involve automation.

A reader whose goal is product software development should compare the actual tasks with that goal. Enjoying coding does not establish that user support, operating systems and device troubleshooting are the work you want to do every day. Conversely, someone who enjoys diagnosing practical problems and helping users may find the direction attractive.

Use your existing evidence to make that preference concrete. In a personal learning record, distinguish what you observed, what you changed and whether the issue was resolved. Describe any boundary or help you needed. That gives you something substantive to discuss if a later role asks about problem solving.

Keep private information out of a shareable example. An employer's internal support ticket is not automatically portfolio material. You can explain your contribution using a permitted summary or a clearly identified fictional exercise. This guide does not ask you to publish customer records or claim access to Google's internal systems.

Eighteen months and forty hours need a practical plan

The current US program description combines paid on-the-job training, related instruction and career development, with a forty-hour weekly commitment. It describes a Registered Apprenticeship and a completion credential. These features explain the work-and-learning attraction; they do not establish a permanent Google job afterward.

A prospective applicant should compare the commitment with existing obligations before relying on the program as a casual side course. Forty program hours plus an existing twenty-hour job would total sixty scheduled hours in a simple example, before travel or other obligations. That arithmetic does not establish permission for a second job or a realistic schedule.

The search-indexed IT copy named Austin and New York and required US presence during the program. We could not verify those details in a currently available role. The current overview's general US office list does not establish that every track is offered at every site, or that a future IT cohort will use the same locations.

Work authorization is another separate check in Google's program guidance. Being physically in the United States is not the same fact as having authorization to do the work. Review the actual role and relevant authorization requirements; do not infer sponsorship, citizenship requirements or remote-anywhere permission from a general program article.

Pay, exact attendance, relocation terms and the applicable offer conditions need current evidence if an opening and offer become available. Do not budget a future move using an indexed salary or a general statement that eligible candidates may receive relocation help. The individual terms are what would make that commitment reviewable.

Reconcile the materials guidance before building a packet

The overview's Application materials tab lists an updated resume. It places examples of additional materials under countries other than the US. A general FAQ elsewhere on the same page describes a resume and accompanying cover letter, with track-specific requirements possible. The indexed IT role had instructed applicants to attach one updated English resume document, with PDFs preferred.

These descriptions have different scopes. They are not a reason to combine a resume, letter and unrelated certificates into one file or to omit a document explicitly requested by a new opening. Preserve the actual track's instructions when applications reopen and resolve a genuine conflict for that requisition.

Leo's completed materials note therefore has a bounded result: updated resume ready to review; additional-document requirements unverified for a future IT opening. He has not marked a packet complete or claimed an application receipt. If the next role specifies a letter or questions, he will prepare those in their designated place.

Google's program FAQ also says completion can lead to exploring and applying for full-time opportunities, depending on availability and profile. It does not promise a role at Google. Treat the apprenticeship's defined work and learning separately from whatever job search follows it.

For now, keep the closed cohort in a monitoring list and continue examining current roles on LandOffer and employer sites. Save your exact degree subject, enrollment and practical-experience record beside the official program link. When a new IT opening appears, verify its cohort, application window, degree branch and experience wording. Check its location, schedule, authorization and materials instructions before moving from monitoring to application preparation.

Sources and Further Reading