Kakunyn Talent

YOUR CANDIDATE JOURNEY

Know what comes next.

Our process is short, practical and conversational. The exact path may change by role, but we will always tell you what to expect.

See open roles Open the 1-page guide
  • Up to three conversations15–30 minutes each
  • English and PortugueseThe first call is in English
  • Remote or on-siteWe confirm the format in advance

THE PROCESS

Up to three clear conversations.

No surprise tests, no trick questions. Every stage exists so we can understand how you think — and so you can understand how we work.

  1. A candidate smiling during a video interview at home

    15–30 min · Remote · In English

    First conversation

    A relaxed introduction so we can meet you, understand your interests and learn how you communicate. You do not need perfect English: we care about whether we can understand one another.

    • Keep your CV or LinkedIn nearby.
    • Tell us what you are curious about.
    • Ask us to repeat anything you did not catch.
  2. Two people testing a mobile game next to a notebook with a checklist

    15–30 min · Remote or on-site

    Hiring manager + practical exercise

    If you move forward, the next step depends on the role. You will meet a hiring manager and work through a short practical exercise. We want to understand how you observe, ask questions and explain your decisions.

    • Bring your notes — you may use them.
    • Say your reasoning out loud as you test.
    • Ask questions before you start.
  3. A candidate in a relaxed conversation with two founders

    15–30 min · When applicable

    Conversation with the founders

    Some roles finish with a conversation with our founders. In an on-site process, this may happen during the same visit as the practical exercise. We will confirm the format beforehand.

    • Talk about what you want to learn.
    • Bring your questions about the company.
    • Be yourself — that is the whole point.

HOW TO SHOW UP

You do not need rehearsed answers.

The way you think matters more than knowing every term. These are the values you will see throughout the process.

Interns running a playtest workshop in a bright studio

A curious mind

Ask questions, explore beyond the obvious and tell us what you would investigate next.

Truth with respect

Be honest about what you know and what you do not. Clear, respectful communication builds trust.

Care in the details

Take your time to observe, organise your thinking and make your work easy for someone else to understand.

QA STARTER GUIDE

New to QA? Start here.

QA helps a team see risks before they reach the player. Testing is not just playing: it is observing with intention, comparing expected and actual behaviour, keeping evidence and communicating impact.

About 40–45 minutesNo previous QA experience required. Use subtitles or translation when useful.

A notebook with a hand-drawn test plan next to a phone running a game

Quick concept

Turn ideas into tests

A scenario is a high-level situation. A test case is a repeatable check with a title, precondition, steps, expected result, actual result, status and evidence.

What a mini test plan holds

  • The objective of the test
  • Scope, and what stays out
  • Environment: device, OS, build and network
  • The main risks
  • Five to eight scenarios in priority order

Key question: with little time, what could damage the player experience the most?

Anatomy of a test case

A scenario is a situation. A test case is a specific, repeatable check.

Title
what will be verified
Precondition
the starting state you need
Steps
numbered, objective actions
Result
expected, actual, status and evidence

Example — “Restart the level after losing”. Lose the level, then tap Try again. Expected: the level restarts from the beginning and the controls respond.

Four possible statuses

  • Passedexpected = actual
  • Failedthere was a difference
  • Blockedtesting was not possible
  • Not runit has not been executed yet

EXPLORATORY TESTING

Seven lenses for a mobile game

Leaving the “correct” path is where most bugs live. Run each lens for a couple of minutes and note anything that surprises you.

A shelf of phones and tablets used for device testing
  • Main flow

    Open, play, win, lose and restart.

  • Wrong order

    Skip steps or act before the game expects it.

  • Rough input

    Fast, repeated or unexpected taps.

  • Boundaries

    Collisions, limits, backtracking and alternative paths.

  • Interruptions

    Background and return, rotation, network changes.

  • Persistence

    Close and reopen: progress, settings, audio and state.

  • Health

    Interface, loading, freezing, slowdown, heat and battery.

Hands annotating a captured game frame on a tablet

BUG REPORTING

Six lines make a great bug report

The goal is simple: someone else should reproduce the problem without asking you a single question.

  1. Title[Area] + action + observed failure
  2. Environmentdevice, OS, build and network
  3. Preconditionthe state before you start
  4. Stepsa numbered sequence anyone can follow
  5. Resultexpected versus actual
  6. Contextfrequency, severity and evidence

Severity is the impact of the problem. Priority is how urgent it is to fix.

15 MIN

A 15-minute practice

  1. Open any simple mobile game.
  2. Write down the test objective, environment and three risks.
  3. List five scenarios in priority order and run three of them.
  4. Write one real or hypothetical bug report.
Bring your notes. You may use them during the exercise.

Quick glossary

Build
the version being tested
Environment
the conditions of the test
Scope
what is included
Retest
confirming a fix
Regression
checking whether a change broke existing behaviour
Open the CTFL glossary (opens in a new tab)

TAKE IT WITH YOU

One page. Everything you need.

A printable summary of the mini test plan, the test case anatomy, the statuses, the exploration lenses and the bug report template. Print it or keep it open during the exercise.

Open the 1-page guide

YOUR CANDIDATE JOURNEY

Ready to bring your questions?

See open roles