Spellbreak Dev Tracker

For your portfolio, highlight the best thing. Put it front and center. Make it easy to see what you did, what's cool about it, what you'd change. Don't expect me to install your game, just make a video on YouTube. P.S. Excel files totally count as portfolio material! (13/18)

In an interview, when asked a question, take a breath. You don't need to rush through answers. We want to see how you work through problems, how you collaborate and take feedback, so "show your work". We want you to succeed so ask for clarification or help if you need. (12/18)

Do mock interviews with your school, friends, or anyone you can. Interviewing is a skill and it's hard, so get some practice in. (11/18)

Be concise. For a entry-level role, we get 100s of applications, so get in, say what you need, and get out. Don't make me sift through a 4-page resume and 30 pages of supporting documents. Also make it legible. This is not the place for your creativity to shine through. (10/18)

Have a friend copy-edit and proofread your materials. A second set of eyes is so much better than looking over things yourself. (9/18)

Use your cover letter to tell us, specifically, why we should hire you, specifically. Don't just restate your resume, long-form. Don't use a generic cover letter for a dozen different jobs. (8/18)

You know that feeling you get when you're so wound up about something that you start to ramble? Harness that and make us feel your excitement (but don't ramble). (7/18)

Have core knowledge for the role. If you're applying for a systems design job, you should have an understanding of probability and stats. If you want to be an encounter designer, be able to debate the merits and drawbacks of trash or downtime on fights, and so on. (6/18)

There's never been a better time to tinker with games. Game engines, tools, and compilers are free. Modding games is easy. Build a portfolio, show off your stuff, even if it's not polished. Tell us what you learned in the process and what you'd do next time. (5/18)

Be familiar with game and genre you'd be working in. Come prepared to talk about them and don't be surprised when you're asked for your thoughts about what's good, bad, what could be better, what you'd do differently, etc. Be honest and constructive. (4/18)

Call out experience with the games of the company where you're applying. Own the fact that you achieved something big, contributed to the wiki or fan site, built tools for a game! (This is how I got my foot in 23 years ago...) (3/18)

You probably have more relevant experience than you think! That volunteering to teach kids to code, moderating a gaming discord, leading a guild... those are all way more interesting and relevant than the year you spent being paid by a chain restaurant. (2/18)

We recently opened hiring for a number of associate / entry-level game designer roles. This is exciting and a great opportunity. While looking at and talking to a lot of candidates, some things stood out to keep in mind when applying for jobs.

No surprises here but a 🧵(1/18)

No one told me that the most emotionally satisfying thing in my life would be making pancakes in the morning for the kid and watching her double fist and stuff them into her face. Occasionally she offers one mangled carcass up to me and I die.

In a game long ago, @paperraincoat made "Difficulty Potato" as a way for players to select how easy/hard they wanted the game to be.

It's so good even if the sloth is on ogles and not me.

(We also have systems and quest design openings too!)

This team is great and our Boston office is pretty rad too (even if you don't ever have to be there).

I am taking cues from the kid and have favorite utensils for very specific things. I get very sassy if my favorite yogurt-eating spoon or egg-beating fork are not available.

And finally, thank you, co-founders. Joe, @diannuzzelli, @dogles, and @sjsivak. I can’t imagine doing this with anyone else. And if I’m honest, I’d do it again with you in a heartbeat. 10/11