Google Is Offering Buyouts to US Employees Throughout the Company
Google is offering buyouts to U.S. employees across multiple divisions of the company, including within its search division.
The company's knowledge and information division, which includes Google's search, advertising, and commerce teams, announced its "voluntary exit program" today, the company told Investopedia. Buyouts have also been offered to the tech titan's central engineering teams, the company confirmed.
'Earlier this year, some of our teams introduced a voluntary exit program with severance for U.S.-based Googlers, and several more are now offering the program to support our important work ahead,' Google spokesperson Courtenay Mencini wrote in a statement.
"A number of teams are also asking remote employees who live near an office to return to a hybrid work schedule in order to bring folks more together in-person," Mencini added.
Google's latest move to reduce headcount comes after multiple rounds of layoffs in 2024, and a major push at the start of 2023 that laid off approximately 12,000 workers, or about 6% of its workforce.
Shares of Google parent Alphabet (GOOGL) climbed about 1% Tuesday, leaving them down over 5% for 2025 so far. They were little changed in after-hours trading.
Read the original article on Investopedia
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Android Authority
an hour ago
- Android Authority
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Mishaal Rahman / Android Authority TL;DR Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release. The company says this is because it's shifting its AOSP reference target from Pixel hardware to a virtual device called 'Cuttlefish' to be more neutral. While Google insists AOSP isn't going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult. Earlier this year, Google announced it would develop the Android OS fully in private to simplify its development process. By focusing its efforts on a single internal branch, Google aimed to streamline work that was previously split. The news initially spooked some in the Android development community, but the controversy quickly subsided. The impact was minimal, as Google was already developing most of Android behind closed doors and promised that source code releases would continue. Now, however, a recent omission from Google has rekindled fears that the company might stop sharing source code for new Android releases, though Google has stated these concerns are unfounded. As promised, Google published the source code for Android 16 this week, allowing independent developers to compile their own builds of the new operating system. This source code was uploaded to the Android Open Source Project (AOSP), as usual, under the permissive Apache 2.0 license. However, multiple developers quickly noticed a glaring omission from the Android 16 source code release: the device trees for Pixel devices were missing. Google also failed to upload new driver binaries for each Pixel device and released the kernel source code with a squashed commit history. Since Google has shared the device trees, driver binaries, and full kernel source code commit history for years, its omission in this week's release was concerning. These omissions led some to speculate this week that Google was taking the first step in a plan to discontinue AOSP. In response, Google's VP and GM of Android Platform, Seang Chau, refuted these claims. In a post on X, he addressed the speculation, stating that 'AOSP is NOT going away.' Mishaal Rahman / Android Authority He also confirmed the omission of Pixel device trees is intentional, stating that 'AOSP needs a reference target that is flexible, configurable, and affordable — independent of any particular hardware, including those from Google.' Instead of supporting AOSP builds on Pixel devices, Google will support the virtual Android device 'Cuttlefish' as its reference target. Cuttlefish runs on PCs, allowing Google and platform developers to test new hardware features. Google will also continue to support GSI targets, which are generic system images that can be installed on nearly any Android device. On one hand, this logic is sound. Google wants to move away from using Pixels as the AOSP reference device and is making changes to that effect. As Seang Chau notes, 'AOSP was built on the foundation of being an open platform for device implementations, SoC vendors, and instruction set architectures.' In that regard, Cuttlefish is a more appropriate reference target because it isn't a heavily customized piece of consumer hardware like a Pixel phone. However, since Cuttlefish is a virtual device, it can only simulate how hardware features behave, making it an imperfect reference in some ways. The more significant issue, however, is the impact this decision will have on developers who build custom ROMs — the community term for hobbyist forks of AOSP. Nolen Johnson, a long-time contributor and reviewer for the LineageOS project, says the process of building these ROMs for Pixel phones will become 'painful' moving forward. Previously, Google made it simple for developers to build AOSP for Pixel devices, but that support is now gone. Developers simply had to 'pull the configurations [that] Google created,' add their customizations, and then build. Now, however, they will need to take the old device trees that Google released for Android 15 and 'blindly guess and reverse engineer from the prebuilt [binaries] what changes are needed each month.' This is because making a full Android build for a device — not just a GSI — requires a device tree. This is a 'collection of configuration files that define the hardware layout, peripherals, proprietary file listings, and other details for a specific device, allowing the build system to build a proper image for that device.' While Google previously handled this work, developers must now create their own device trees without access to the necessary proprietary source code. Furthermore, Google's decision to squash the kernel source code's commit history also hinders custom development. The Pixel's kernel source code was often used as a 'reference point for other devices to take features, bug fixes, and security patches from,' but with the history now reduced to a single commit, this is no longer feasible. While Google is under no obligation to release device trees, provide driver binaries, or share the full kernel commit history (in fact, it's one of the few device makers to do these things), it has done so for years. The company's reason for doing so was because the Pixel was treated as a reference platform for AOSP, so developers needed an easy way to build for it. Google's decision to now discontinue the Pixel as an AOSP reference device is unfortunate, as it has pulled the rug from under developers like the teams at LineageOS and GrapheneOS who build Android for Pixel devices. These developers will still be able to build AOSP for Pixel devices, but it will now be more difficult and painful to do so than before. Got a tip? Talk to us! Email our staff at Email our staff at news@ . You can stay anonymous or get credit for the info, it's your choice.
Hamilton Spectator
an hour ago
- Hamilton Spectator
Oman foreign minister says there will be sixth round of negotiations between Iran and US on Sunday
DUBAI, United Arab Emirates (AP) — Iran and the United States will hold a sixth round of negotiations over Tehran's rapidly advancing nuclear program this Sunday in Oman, the sultanate's foreign minister said Thursday, as regional tensions have spiked in recent days. The announcement by Oman's Foreign Minister Badr al-Busaidi comes as the U.S. is drawing down the presence of staffers who are not deemed essential to operations in the Middle East and their loved ones due to the potential for regional unrest. Meanwhile, there have been warnings that ships could be targeted in regional waters over the tensions. Al-Busaidi made the announcement on the social platform X. 'I am pleased to confirm the 6th round of Iran US talks will be held in Muscat this Sunday the 15th,' he wrote. Iran for days had been saying there would be talks, but Oman, which is serving as the mediator, had not confirmed them until now. There was no immediate comment from the U.S. Reaching a deal is one of the several diplomatic priorities being juggled by U.S. President Donald Trump and his trusted friend and Middle East envoy Steve Witkoff . An accord could see the U.S. lift some of its crushing economic sanctions on Iran in exchange for it drastically limiting or ending its enrichment of uranium. But a failure to get a deal could see tensions further spike in a Middle East on edge over the Israel-Hamas war in the Gaza Strip . Iran's economy , long ailing, could enter a free fall that could worsen the simmering unrest at home. Israel or the U.S. might carry out long-threatened airstrikes targeting Iranian nuclear facilities. And Tehran may decide to fully end its cooperation with the United Nations' nuclear watchdog and rush toward a bomb. Iran and the U.S. have held previous talks in Muscat and Rome. Error! Sorry, there was an error processing your request. There was a problem with the recaptcha. Please try again. You may unsubscribe at any time. By signing up, you agree to our terms of use and privacy policy . This site is protected by reCAPTCHA and the Google privacy policy and terms of service apply. Want more of the latest from us? Sign up for more at our newsletter page .
Tom's Guide
2 hours ago
- Tom's Guide
Claude 4 is one of the best chatbots yet — here's the only prompt you'll ever need for it
There is an art to prompting AI. While a chatbot will answer almost any kind of question, no matter how you phrase it, they are designed to operate best with incredibly specific instructions. This can be hard to work out yourself, needing a bit of understanding about how the models work. Most of the large companies in AI now have prompting guides, explaining how best to use them, but Anthropic's Claude goes a step further. Load up the chatbot and you'll be given free rein to ask any question or request that comes to mind. Or, for a simplified and more effective approach, Claude offers five pre-made options that will set you up for the best answer. These aren't necessary for a quick question or an easy request, but if you're looking for a detailed and well-thought-out answer, try these options out — all listed just below the search bar. Claude currently offers five different pre-made options. These are: write, learn, code, life stuff, and Claude's choice. For each one that you click on, a host of options will appear. These change each time you open Claude, giving a wealth of options. Write As the name suggests, this is all tasks that involve writing. In this option, you'll find templates including writing case studies, developing content calendars, and creating social media posts. Learn The Learn category is one of the more varied ones. This can be for anything from developing discussion prompts on a given topic, creating feedback for students, or creating a knowledge map with surprising patterns in topics you know well. The Learn category can be either incredibly specific or unbelievably vague, joined only by the idea that you'll learn something new here. Code Claude 4 has built up a reputation for its coding ability. However, it can be hard to get going with this. Vibe coding (the ability to write code by prompting AI) has seen a jump in popularity, but it does take a bit of skill. This mode helps get you started, offering templates such as vibe code with me where it will start with a back-and-forth conversation about what you're making, or simply a clear request like help me turn a screenshot into working code. Life Stuff The vaguest sounding prompt here, Life Stuff, is anything in your personal life. Use this mode to organize your living space, improve your sleep habits or develop exercise routines. This mode does involve putting in quite a lot of personal information about yourself. While Claude has made a point of not using any data that you put in for training, it is important to consider if you're comfortable divulging any information. Claude's Choice This is a bit like Google's 'I'm feeling lucky'. It's just a random assortment of starting points for a conversation with Claude. Some of the examples I was presented with include 'explore ancient wisdom', 'consider innovation patterns', and 'explore memory techniques'. This section is less useful, and more where you go when you're bored and looking for something to do. Once you've decided on your category, simply click the prompt that best works for what you're after. If none of them fit exactly what you need, click the one that is closest to your needs. Claude will then fill out the prompt for you with the model asking some follow-up questions to help nail down the conversation. Using these pre-made prompts is a bit like having someone introduce you and explain what you're looking for. It sets up the conversation so all you need to do is answer the questions that you're asked. The prompt that is generated by this method is almost identical every single time, looking roughly like this: If none of the pre-made options apply to you, try copying the above into Claude, replacing the enter topic section with what you're looking for. While the prompt style above won't always work, it is an easy way to get started with Claude and gives you an idea of the best way to get the chatbot to perform. I tried it with a variety of prompts, both pre-made and ones of my own choosing and had success with the vast majority of them. By using this kind of technique, it will also allow you to make the most of Claude's Artifacts feature - creating in-app games, tools, and interactive features. Get instant access to breaking news, the hottest reviews, great deals and helpful tips.
