Blizzard Hiring C++ User For Their Classic Games Team

[StoPCampinGn00b]

One of the Blizzard recruiters, Jess Roberts, announced that they are hiring for a classic game position for someone with C++ and "hacking" skills. They want to talk! This was also shared by the official @BlizzardCareers Twitter and of course our (Hive's) social media.

Check it out!

Link to our Tweet about this.

 

[Barade]

If it wasn't for preventing cheaters and if I wouldn't be still at university (senior level engineer ....) I would consider writing them. I guess you still have to live next to the company?

 

[PurgeandFire]

If it wasn't for preventing cheaters and if I wouldn't be still at university (senior level engineer ....) I would consider writing them. I guess you still have to live next to the company?

They do favor locals, unfortunately. Visa issues are the main reason. It is like that with a lot of companies here unless they have an hq at another location (but even then, they prefer to keep teams together).

 

[Dr Super Good]

Its in the USA... Who on earth would want to move there at the moment.

I bet most issues with WC3 could be solved by anyone with decent c++ understanding in a few hours.

 

[Aniki]

I bet most issues with WC3 could be solved by anyone with decent c++ understanding in a few hours.

I beg to differ. It would take a while for one to familiarize themselvs with those million(s) of lines (just a guess) of C++ ("2000 - 2003 C++" would probably be a bit different than "modern C++") code that the "brainfuck" engine of Wc3 is [probably] written in.

 

[Dr Super Good]

I have fixed bugs in open source video games using pre 2000 technology. It is hardly going to be worse than those.

 

[A Void]

Can't they simply reassign other people from other projects to Classic team?

 

[Dr Super Good]

Can't they simply reassign other people from other projects to Classic team?

Think of business sense. It makes none to assign people from future projects which make money to something legacy which earns practically nothing.

 

[A Void]

Think of business sense. It makes none to assign people from future projects which make money to something legacy which earns practically nothing.

Well it's not like they would be what they are without classic games. Practically I don't play any of their newer games apart from SC2. Devoting a temporary team to make a few updates to classic games wouldn't hurt anyone, it would only attract more people.

The problem is that it's not on their priority list, which sucks.

 

[Dr Super Good]

Well it's not like they would be what they are without classic games. Practically I don't play any of their newer games apart from SC2.

So you basically are not a customer then as you are paying them nothing?

Devoting a temporary team to make a few updates to classic games wouldn't hurt anyone, it would only attract more people.

More people to play low value products, which they likely have already paid for. As opposed to if they assigned the same team onto Heroes of the Storm or StarCraft II to add a new hero extra which would earn them a lot.

The problem is that it's not on their priority list, which sucks.

Because developing stuff which has a value is worth more than maintaining something which is almost valueless. Worse, the maintenance might decrease the value of valuable products, eg if they started to make WC3 feature level parity with SC2.

 

[PurgeandFire]

Can't they simply reassign other people from other projects to Classic team?

Hmm, they might be able to. There probably are some issues though--e.g. preferences, and the technology (I imagine that people programming for hearthstone/overwatch would feel pretty lost switching to classic games).

But they are actively recruiting. Even though that senior software position has been up for what feels like a year, they've gotten several people since then. They're still looking for more, so they never took it down.