Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sunsetting Hire

support.google.com

Post reply on HN
Print view View original

271–280 of 301 posts

Re: Sunsetting Hire

#271

Post by lonelappde »

tylerl wrote: post #194
n42 wrote: post #163

What is humorous to me is that Google is hurting users who typically have the most influence over SaaS integrations at their company (managers) by taking away a tool that helped them deal with the part of their job most of them hate the most (hiring/recruiting). If it hasn't been obvious yet to managers watching this, Google's software is not a safe investment for you to make for your company. It is only a matter of…

Bebop was an acqui-hire, not a real product. All they wanted was the CEO. I don't think anyone took the product seriously except for the person who started it, and once she left Google, there was no reason to continue pretending that it was a real thing.

That's fine, but why do a whole rebranding before shutdown instead of sunsetting Bebop which was a dead brand anyway?

Re: Sunsetting Hire

#272

Post by nateps »

mjfisher wrote: post #246
nateps wrote: post #132

I'm the founder and CTO of Lever, YC S12. I also worked at Google as a PM prior to founding Lever. Let me know how I can help if anyone has questions! We're a great alternative to Google Hire.

Hi Nate. I've recently launched a service for managing coding challenges for recruitment through git ( https://candidatecode.com ). I'm keen to start offering some lightweight integrations for a few ATS - is there anyone you can point me to in Lever that might be able to kick off that discussion?

Sure thing. Send me a note and I can forward

Re: Sunsetting Hire

#273

Post by lonelappde »

tonyedgecombe wrote: post #238
kayoone wrote: post #169

Earlier quoted context omitted.

Well to that extent, most other SaaS products which are affordable for SMBs are not a safe investment either, it's not that non-google companies/startup never shut down. Actually most SaaS startups fail.

Profits that don't register for Google can make a sensible business for a smaller company.

Do you think Bebop would have survived if Google never tried to buy it? Or if Google poached the key staff but didn't buy the company?

Re: Sunsetting Hire

#274

Post by lonelappde »

croon wrote: post #243
kayoone wrote: post #169

Earlier quoted context omitted.

Well to that extent, most other SaaS products which are affordable for SMBs are not a safe investment either, it's not that non-google companies/startup never shut down. Actually most SaaS startups fail.

> While Hire has been successful, we’re focusing our resources on other products in the Google Cloud portfolio This is not a decision any startup would make. So there's at least some difference, in Googles disfavor.

It literally was a decision a startup made. Bebop was a startup that sold itself.

Re: Sunsetting Hire

#275

Post by nateps »

2arrs2ells wrote: post #214
nateps wrote: post #132

I'm the founder and CTO of Lever, YC S12. I also worked at Google as a PM prior to founding Lever. Let me know how I can help if anyone has questions! We're a great alternative to Google Hire.

Nate - why do you think Google shut down Hire? When it launched, did you see any path for it to become a major ATS player, given Google's impatience? Thx & hope Lever scoops up a bunch of customers from the transition (if Hire even had a bunch of customers!).

As many of the news articles have talked about, Google Hire's origin was the acquisition of Bebop. Some discussion on this HN thread: https://news.ycombinator.com/item?id=10839516

In this case, I know that Diane Greene advocated for her team to have the opportunity to launch their product, which they had been developing in stealth from 2012-2016.

I haven't worked there for some time now, but Google has historically supported teams in launching into the market through experiments, labs, new product launches, etc. However, Google's current scale makes it very difficult for a new product to be worth improving and maintaining. They must make billions in revenue directly or indirectly to show up in a meaningful way. In most cases, products are given a few years, tested for impact, and ultimately the most likely outcome is that a product will fail when that is the bar. It is not entirely different from the reality of a startup—the majority of startups don't last either.

Re: Sunsetting Hire

#276

Post by ulfw »

suzzer99 wrote: post #174
ulfw wrote: post #145

I stopped using every Google product besides Search and Maps. Still have Photos but thats replaceable. Oh and Youtube, which is not replaceable. Haven’t used Gmail in a decade and no use for all the other stuff that no one knows if it will be around next year or not. Sorry to say but that what it has become.

I still have the old picasa executable so I can use it on new or reinstalled computers. It's great for browsing all the images and videos on your computer.

Sadly doesn't run on Macs using Catalina anymore

Re: Sunsetting Hire

#278

Post by mogar1980 »

Strom wrote: post #258
noahl wrote: post #254

Earlier quoted context omitted.

The trouble is that if you have to understand or correctly guess internal Google politics like this in order to know which products you can really rely on, then it's effectively not reliable. With that said, I'd feel fine relying on VMs, disks, managed SQL, managed Kubernetes, etc. Maybe I'm too optimistic. And Google is giving exactly the guarantees they promised - 1 year of notice before shutting down a product.

> And Google is giving exactly the guarantees they promised - 1 year of notice before shutting down a product. This is mostly true, but a bit more nuanced than one might think. Let's take the Go 1.9 runtime for App Engine. It was deprecated on June 27, 2019. [1] Existing deployments will keep working for an undetermined time, however new deployments won't be accepted starting October 1, 2019. That's just a 3 month no…

Note: I work on App Engine. Go 1.11 supports all legacy 1st generation APIs. It's in the first section of the doc [2] that you posted although perhaps we can make this even clearer. We maintained support for these APIs precisely to make this migration extremely straightforward for our existing users as we moved to a more modern underlying technology stack and a version of Go supported by the language community. We absolutely want App Engine to be a place you can confidently build a business upon.

Re: Sunsetting Hire

#279

Post by iamsb »

dillondoyle wrote: post #196
iamsb wrote: post #109

Earlier quoted context omitted.

Given the speed with which youtube is demonetizing people or outright banning them, not sure how much longer it will sustain though.

This argument doesn't hold weight for me. Google demonetizes because advertisers don't want their ads on that content - and that is true no matter what platform.

To some extent, yes. But see this comment -> https://news.ycombinator.com/item?id=20818621 There are plenty of examples like this. Google's problem is not that it is cracking down on bad actors. The problem is, it does not have a human interface. So once you are part of type-1 error set, you have very little way out. Once there is sufficient number of such people, who have critical mass for a competing service.

And honestly, I am really glad that google products are dying. I switched to DDG 6 months ago, Firefox 1.5 years ago and I dont miss either of the products. Hopefully big tech monopolies will start crumbling one way or the other.

Re: Sunsetting Hire

#280

Post by tmpz22 »

mogar1980 wrote: post #278
Strom wrote: post #258

Earlier quoted context omitted.

> And Google is giving exactly the guarantees they promised - 1 year of notice before shutting down a product. This is mostly true, but a bit more nuanced than one might think. Let's take the Go 1.9 runtime for App Engine. It was deprecated on June 27, 2019. [1] Existing deployments will keep working for an undetermined time, however new deployments won't be accepted starting October 1, 2019. That's just a 3 month no…

Note: I work on App Engine. Go 1.11 supports all legacy 1st generation APIs. It's in the first section of the doc [2] that you posted although perhaps we can make this even clearer. We maintained support for these APIs precisely to make this migration extremely straightforward for our existing users as we moved to a more modern underlying technology stack and a version of Go supported by the language community. We ab…

Was this done proactively or reactively after many months of negative feedback? If it was the former that gives me a lot more faith in app engine after trialing in some years ago and giving up on it.
Post reply on HN