Vrftjkry

For the purposes of this, I'm going to assume that at least the bare facts of the reviews are accurate (i.e., that the company uses older technologies and sometimes requires legacy code from new hires). That being the case, I'd actually lean towards "Ignore it", perhaps even with a mixture of "Embrace it".

The whole point of Glassdoor reviews is so you can assess whether a company provides a working environment that you'll be happy in - and while I personally don't agree with the whole bratty trend of developers whinging because they think they should be entitled to be working on the newest shiny toys (regardless of trivial things like whether it suits the business needs of the company), at the end of the day if someone does have that mindset then ultimately they aren't going to be happy working at that company so you don't want to hire them anyway.

If the company is upfront about what technologies etc. the position will entail, then you are going to stand a much better chance of hiring people who are a better fit for that environment, rather than people coming in with a misconception and ending up disgruntled.

You're looking at this "problem" the wrong way. The way your question reads is "People are leaving negative reviews, therefore people shouldn't be leaving negative reviews, how do we stop people from leaving negative reviews, or have the negative reviews removed to keep our reputation?". That's the mindset that makes you deserving of those negative reviews; to put it another way, if that's how you react to negative reviews, then you deserve as many negative reviews as you get, and there is no hope for you. Remember, Glassdoor doesn't take action from companies based on the companies' wishes; they don't delete reviews just for being negative just because the company asked them to, that's in their policy.

Your mindset should be: "People are leaving negative reviews. Why are they being negative, and what can we take away from this to make people more positive?" Here's the thing: If you have 20 negative reviews that were written last month, you have a problem. If you have 20 negative reviews from 5 years ago and then another 100 positive reviews from last month, the problem goes away. So what you should do for now is ignore the negative reviews (or respond to them in a positive, professional manner, respecting the point of view of the reviewer; coming off as petulant children, which is what sounds like is happening currently, will only serve to make the problem worse). Then you take the constructive parts of the negative reviews (such as they are) and use them to implement changes. Some examples:

1) Tech stack is too old. This is bad not only for your employees but also for your business as a whole. Perhaps today you are using technologies like C++, JQuery, and HTML4 for your tech stack, and that's fine, because these technologies are old but people still know them. But soon they won't be, and you'll be hard pressed to find a developer below retirement age who knows how to dereference a pointer. And then you're SOL because you have legacy code that nobody can maintain. This is a warning sign for you: You should update your tech stack to something that people are learning now, and this is something you should be doing without someone giving you a 1/5 on Glassdoor before you figure it out.

2) Management incompetence is a sign of a company which is ready to fail. If the company is big enough, management doesn't need to know the details of the tech stack. But it sounds like your company isn't at that scale yet, so management needs to be aware of what is going on. It sounds like management has their heads in the clouds. This is just irresponsible, because it means if something goes wrong they not only don't know how to fix it, but they don't even know how to go about finding out how to fix it. This can lead to misallocated resources (e.g. a frontend developer assigned to fix a database-level task) and schedule churn.

Here's the bottom line: People leaving Glassdoor reviews is NEVER a bad thing. If you think it is a bad thing, that's because you have a problem which you know is a problem and you acknowledge as a problem but you refuse to fix it because of your pride. Get off your high horse, fix your business, make some money, and stop grandstanding.

Leave a comment under each review calling it fake.

What would "fake" mean in this case?

Did the person claiming the reviews were fake think the info in the reviews was false (i.e. the company doesn't use old-fashioned systems) or did they think the reviews were all written by one person?

If the reviews aren't facts-based, this can be pointed to. For example, it can be pointed out by the company's HR that they are actually using state-of-the-art technologies.

But lying can normally lead to a PR disaster.

Write to Glassdoor asking them to
remove "fake" reviews.

If they were all produced by one person, it should be possible to prove that easily, so yes, it's a solution. But hopefully, glassdoor doesn't delete legitimate reviews.

Ask employees, directly or indirectly,
to write some good reviews instead.

I use glassdoor and similar sites a lot and it's normally very clear which reviews were written by the HR.

Not to mention that when I was asked to produce similar reviews, this did impact on my opinion about my current employer. It's hard to respect a company that wants you to produce fake reviews.

Ignore it.

Well, it's better to ignore it than to write a silly answer, that's for sure.

The best response from the PR point of view would be, however, one not listed by you. The best response is to react constructively. This means the management should analyze the points from the reviews and take a fair stance on them. For example, if many people write the company is using old technologies, it would be good to scrutinize whether that's really the case or not.

If that's true, the company should own to it, but stress for example, that the technologies are still used by plenty of important companies, so by learning them new employees get valuable skills and that candidates learn about the technologies used from job ads and later during the interview processes - that nobody is misled.

This assertion makes sense only if really nobody is misled of course.

And if the company is really bad - if it misleads candidates promising them modern technologies, development and then gives them jobs using technologies from the 80s?

Well, then it's good it gets criticized online. The relation between employers and candidates is a dramatically unequal one. So it's good that some candidates will learn the truth from such reviews.

Adding a response to complaints is the correct answer - but calling them each "fake" is the wrong answer.

When people leave a review on the company, and the feedback is negative, responding by calling it 'fake' does not leave the correct impression - it leads people to believe that your company sweeps problems under the rug and doesn't really care about negative feedback at all. While it might be frustrating to your CEO, if a problem is preported it should be addressed - and in a mature and level-headed manner.

The correct way to respond to these reviews is to address the issue - to leave a comment detailing how the company works to assist people with the problems these programmers have - perhaps even to explain that yes, your company is in the business of maintaining legacy programs, because you are a long-standing company with a lot of legacy users who need that support, and that you offer plenty of training for these long-standing programs and for new recruits.

I don't know the full details of your company - but the bottom line of this is that the best way to deflect complaints like this is to tackle them head-on, and show that you are above these whiners - not to completely ignore them, but to overwhelm them with concern for their reported company issues.

Note - ideally, you would also actually be implementing these improvements, but in lieu of that, you can at least acknowledge these problems and explain steps that you plan to take to correct them.

Make it a positive experience. Leave a note on Glassdoor that says "Yes, your company's infrastructure is based on VB6 and SQL Server 7 and that it works nicely and meets your needs, and that you're happy with it, not planning on replacing it, and are looking for employees that are also happy with it." Also note that this wasn't a surprise and that the employee was told what the work was before accepting employment.

The world is full of people who would be thrilled to work with whatever technology you have.

The biggest thing you need to do is make sure you set their expectations from the start. You'll probably need to hire experienced, older devs and skip recent grads.

Glassdoor debacle?

It's only a debacle if you perceive it as such.

There really is only two things that the management can do about this. One is long-term, and the other is short-term.

In the short-term...

Instead of inserting comments which call negative reviews "fake", someone who represents the company can address the individual case in a kind and humane way while also indicating the steps the company is taking to avoid this kind of problem in the future. This is the best way to handle hot-headed negative reviews, in some cases it can even be interpreted as a positive by readers.

In the long term...

Learn from the criticism they've received, and implement changes.

I have seen this happening, and the net result was lowering the level of candidates for non-managerial jobs. Your CEO has work to do if he wants to rescue the company's reputation in the talent pool.
In terms of practical actions, the CEO needs to address this internally, prioritising complaints and reviewing the most urgent ones internally. Certainly, he doesn't want to brainstorm about those reviews with the whole organisation.

Simple: pay considerably above the market rate.

That's what many "leading" technology companies do. This brings in lots of candidates to the job interviews, and retains (locks in) existing employees. Of course this requires that company is making money or has regular investment rounds, but if that were not the case, I imagine you wouldn't be asking :)

The above is the easy part. The hard part is how to get healthier company culture adopted. That takes time, but if you solve that, you wouldn't have to worry about a bad review or two.

These are centered mostly around the use of old technologies, the inability of management to keep pace with newer tech, and the disappointment of new hires at having to write legacy code right out of the door.

That's good to have in there. This is just the kind of information you want prospective applicants/new hires to have. If they know this going in, you're likely to have better retention and higher worker satisfaction (which also positively affects productivity). Management should probably even put this information in the job description for applicants who don't read Glassdoor. If you can't get people on when that's accurately disclosed, increase salary or other relevant attraction factors. Don't deceive applicants about the type of technology or work they're being hired to do.

Many of them are emotional and some come off a bit bratty, but it's encouraged others to do the same.

If you can tell from reading it that a post is emotional/bratty, probably so can a prospective applicant, who can also discount the value of that review appropriately.

When reading through reviews (for a job or anything else) I find that the negative reviews where people complain about petty things can be some of the most convincing to get me to buy in. If people are complaining about little things, and there are enough reviews that more major issues likely would have been included, that usually means the important things are all at least OK, maybe quite good. "I was hired as a COBOL developer and they just have me writing COBOL for 8 hours a day; so boring" was maybe intended as negative but it'd be a plus in that company's column for me and probably other readers.

Sometimes the effect is even more direct. The coffee is cold on the devs' corporate yacht, and the salary for remote work is only enough to rent a mid-size apartment in San Francisco or Manhattan? Where do I go to sign up?

Assuming I were the CEO or had a place in management, what could I do regarding damage control?

Fix your job descriptions so people know what they are getting into.

If there are other problems being raised in the reviews, think about whether or not those are issues the company can/should fix and if so, how.

If you know of particular loyal employees who are having a good experience, consider asking them to write reviews, to help attract new colleagues.

Also, keep in mind that the percentage of potential applicants/employees who read Glassdoor is lower than you might expect.

The only two correct responses are actually fixing the issues and making a large pr move promising to fix the issues that shows what you're doing for your devs and how it's making their life easier.

The latter is very similar to a popular strategy used by youtubers when they get caught in unsavory light. The thing this response affords a company to do is pretend to fix the problem and convince their audience that it's been fixed without actually fixing anything. Youtube itself also employs this strategy.

You don't have to fix anything, if you've made it look like you've fixed everything.

If you don't want to just lie until people agree with you, then you could try being more transparent about what the job actually is, or you can stop making the decision to work for your company something that's massively career limiting by refusing to use modern frameworks that would give your devs relevant experience to put on their resume when applying to better places. You could also try offsetting the garbage work conditions with perks like more time off, more time off, or modern work practices like working from home, unlimited PTO, or unlimited sick days.

Those are really the only good responses. The rest are just going to see the company go really negative as far as hiring PR is concerned.

Well, one possibility could be to use the critics and try to solve some issues, e.g. by using more modern practices and spend more time in refactoring your legacy code problem. When things change and become more positive for each of the employees, then they may change the review.