Hytale Dev Tracker

My thoughts are with everyone in Thailand grieving this atrocity. What a dark day this is.

in breaks after working on removing 7 layers of hell wallpaper ive been playing some skylines

played the manor lords demo and its really promising! all the more excited for release

Some wip other angles

Just started #sculptober , and I'm already late. A speed sculpt for day 01 - "Boss". The only and one boss. I already know I won't be able to make all the days, but this one was fun to make #Zbrush

With that said, we currently have many open positions!

🎮 Game Systems Engineer (level II and senior)
🎮 Gameplay Engineer (level II and senior)
🤖 AI Engineer (senior)
📝 Game Designer (senior)

To apply:

#gamedev #gamedevjobs #gamejobs #remotework

#10 - For engineers, if you're given a problem, don't try to remember an answer.

Walk the interviewers through your thought process, how you go about solving the issue. This is more important than trying to give the right answer, sometimes there are not even right answers.

#9 - During interviews, when talking about experiences you had, think about CAR.

- Context: What happened
- Action: What did you do (not the team, YOU)
- Result: What was the solution and impact

I'd suggest you to train with this mindset before interviews.

#8 - Before interviews, take the time to think about your past experiences.

In most cases, you'll be asked to tell some of your stories (e.g. "Tell me a time where you faced a difficult problem"). If you do this preparation, you'll have an easier time during interviews.

#7 - Don't spam applications.

Between two applications, give it time, especially for you to keep growing in areas where you might have not been meeting the requirements. 6 months between two applications should be enough.

#6 - If you wanna include a cover letter, tailor it for the company and keep it short.

An intro, why this company, what you can bring based on what they look for. It's easy to spot generic letters sent with every applications, I'd say it's better to send none than a generic one.

#5 - In your resume, describe your responsibilities for each job/project you were part of.

Write short declarative statements (e.g. - Implemented a data-driven movement controller with ECS in C++). It's a way for you to prove that you meet the requirements for the role.

#4 - In your resume, only keep relevant information for the role you want.

On average, recruiters spend less than 10 seconds reading it, make the important things stand out (e.g job titles in bold) to catch their attention, and discard any information that doesn't add value.

#3 - I know, yeah, entry-level roles are rare in the gamedev industry.

Though there are still ways to grow your skills! You can create mods (e.g. Minecraft, Slay The Spire...), participate at game jams (GGJ, Ludum Dare...), create personal projects (fanarts, games)...

#2 - School experience != professional experience.

If you're a recent graduate, you'll want to look for junior/associate/graduate roles.

#1 - Apply for the role and level (I, II, senior...) that fits your experience.

Assess your experience against the job's requirements. It's fine if you don't meet all the requirements, but it should be at least almost all the essential ones if you wanna have a good shot at it.

Lately I've been looking at the applications we've received at the studio for gameplay roles, here are a few tips for applications and interviews (for any role, any company).

🧵 A thread:

I thought this was funny earlier and shared it with friends, it’s only later that I realised it was THE lizzo that was being referred too, and not Queen Elizabeth II. https://twitter.com/Mobute/status/1575625976515416064

When I'm retired and 80 years old I think I'll open a shop and spend the rest of my days shouting at anyone who leaves my store empty handed: "and don't come back!!!"

Converted a few firstborn space marines to be a little taller by slapping them on some primaris legs. Turned out pretty good!

#WarhammerCommunity