Blink Industries

09/02/26: Introductory session/start of live brief

Nicola Strina – games producer

Started Blink in 2023

pivoting to a new strategy:

focus on small games to develop a strong portfolio of games. 6 months – 1 year development cycle.
Need a quick validation process

takeaways:

-validate ur idea early,

– cut scope (start small!)

-find a small and fun core concept and build a game around it.

-quick development cycle

-aim for small budgets

-to further reduce the cost, consider government grants, tax breaks, outsourcing

-exploit existing IPs, they can bring in a built-in audience.

The Brief:

Logo Animation Brief for nippets

different groups for different seasons : spring -> summer -> autumn -> winter

animation should loop seamlessly

transparent bg

keep logo recognisable at all times- do not redesign it or turn it into a character

allowed: subtle motion, environmental effects,

managing scope creep- lots of spreadsheets and someone who can say no to ideas.

can you swap ideas? Is it just an idea? Does it require new features? Will it conflict with existing features? Does ur work with the existing ideas.

Larian Studios talk 9/12/25

level design-crafting journeys, combat design-every fight a puzzle, rpg design- story tellers, ui/ux design-a window to worlds , scripting, systems design

research-

source material (player’s handbook), community research (YouTubers(xp to level 3), websites (rpg bot), Reddit et al)

Ideation

Google docs/word, spreadsheets, micro or Visio, photoshop

design goals and pillars, internal design review and iteration

feature groups

Unity trip 17/11/25

What did we do? Was it useful? Why? What would have been more helpful? Questions asked and answered

Notes (to be formatted):

Jon von Neumann 

Jobsworth weekly

EOS (where everything is valuable)

Game jams with prizes: can kill creativity and partnership. Not about the process but the goal.

No prize: more about the passion.

My question: Is there any bad advice about getting into the games industry that you’ve heard? In comparison, what’s some of the best?

Feedback-

Best advice: 

Stay curiosity driven

Delight in the glitch, when things go wrong, it’s when the fun stuff usually comes out. (Out wrong script on object, made it that it would shoot u in the other direction when out under your leg.

Don’t wait for things to be perfect before you put them out there

Don’t be sorry, be better. (Just focus on improving)

Perfect is the enemy of the good (getting something done is better than getting nothing done at all.)

Worst advice:

Feeling like you need to know every step of the way to make something, team up with people instead. 

Advice that doesn’t apply to you. (Know when to throw advice away)

Professional advice isn’t always applicable to games (assuming it will be super formal and hierarchical), do not stress, it’s no where near as scary as you think it is.

to form connections that are still valuable now.

-Be nice and be good

-Aim is to have repeat work.

-Industry is so tiny so be likeable.

-Say what you don’t know if they ask you. Let them know you can give it a shot but don’t actually know, haven’t done it before. Be honest. 

-be curious, if you’re interested in 1 part of the process, that will draw people to you.

1729

Unity.com/careers

4 principles 

-lead with empathy and respect

CVs 

Structure:

Less is more, recruiter can usually decide in the first 6-7 seconds

Hobbies and interests not required

Summary: recent experience, and top skills that are relevant to what u r looking for

Showcase key achievements 

Talk abt current goal is, looking for…

Experience:

Keep clear and searchable

Stick to standard job titles

LinkedIn-

Headline: 2-5 keywords to describe skills and key goals

If in active education, feature that. 

Featured:

Portfolio links, standout projects, presentations, cv, general cover letter

About: 

Experience:

Cover letter-

Portfolio-

-Brief summary of project

-samples of work

-discuss your approach and thought process 

-tools

-results

-improvements you wish you could make for future projects 

Interview prep:

-adaptability and problem solving skills

-to a certain degree skills can be taught, if any skill gaps explain how you’re eager to learn and link to relevant experience. Be HONEST 

-prepare questions beforehand

-be in an environment u feel comfortable 

Technical tasks:

Technical interview, active conversation where you solve problems and explain concepts or discuss past technical experience

ALWAYS FOLLOW UP W UR RECRUITER.

Give it a day or so after interview.

On cv, never claim you are an “expert”

Taking the initiative, why is this being asked of me, what might be needed next, could it be done better, who do I know who might also be doing this sort of thing?