Video summary

cara gue masuk Apple Developer Academy | tips and tricks | sharing my experience

Main summary

Key takeaways

Technology

Summary (Technological Concepts + Selection Process Tips)

The speaker, Theo (Apple Developer Academy alumnus, Batch 7, graduated 2024), shares an experience-based guide with a disclaimer that details may change and that he is not affiliated with the academy. His main focus is how to prepare and succeed in the Apple Developer Academy selection, especially the online application, entry test, and focus group discussion (FGD).

1) Application & Registration Logistics (Indonesia-focused)

  • Registration is for the next cohort (he mentions Cohort 9).
  • Applications are stated as open until June 20 (year referenced in the video: 2025).
  • Applicants may apply to a subset of locations (he mentions “three of the five” locations listed).
  • He notes multiple academy locations in Indonesia (and mentions Bali as international).
  • He also highlights that Jakarta’s capacity/opening status may change (possible openings in the following year).
  • The registration site is mentioned as: developeraademy.binus.id (spelling may differ in subtitles).

2) Selection Process Timeline / Phases

Theo breaks the process into these main phases:

A. Online Application (submit several components)

  1. Motivation statement (essay)

    • Usually includes a specific topic chosen by the academy.

  2. Resume / CV

    • Should be ATS-friendly and not overly complex.
    • Include a proper, presentable photo (a phone camera is okay with good lighting).
    • Present projects, achievements, and experiences in a clear, “storytelling” format, ideally with data and clear wording.

  3. Portfolio

    • He states Apple provides templates, and applicants fill them in.
    • He suggests there may be no minimum, with an approximate maximum of 4–5 projects (uncertain).

B. Online Entry Test (technical + logic)

  • The test format is described as multiple choice (memory-based).
  • Topics include:
    • Logic / problem-solving questions (compared to CPNS-style tests)
    • Programming questions that require basic coding knowledge
    • Pseudo-code (no specific language)
    • Programming paradigms such as:
      • Dynamic programming
      • Object-oriented programming (OOP)

Key stress point:

  • Logic questions are “crazy/hard”; he recommends preparing with pen and paper.

Cheating prevention:

  • He mentions open mic / open video during the test.

C. Focus Group Discussion (FGD) — emphasized as most important

  • FGD can be online or offline, depending on the location:
    • Batam and Bali: online (mentioned)
    • Tangerang and Surabaya: offline/on-site (mentioned)
  • Assessed on:
    • Creativity
    • Collaboration skills
    • Communication abilities

Additional note:

  • He adds there may be a pre-registration phase before the online application.

3) What the Academy Looks for (Not Only Coding)

Theo emphasizes the academy is not only for developers or designers. The selection values:

  • Potential
  • Creativity
  • Growth mindset
  • Especially collaboration and empathy

He also notes applicants may not follow a rigid curriculum; the program expects self-learning and creativity.

4) Preparation Tips Tied to Tech / Product Work

Theo shares “what to focus on” guidance for applicants.

Key capability areas

  1. Basic coding (optional but helpful)

    • If you know Swift / SwiftUI / Objective-C, you’ll adapt faster.
    • Practice path ideas include:
      • Swift Playgrounds
      • Xcode

  2. Design thinking & ideation (core skill)

    • Empathy → define problems
    • Create prototypes → test with users
    • He claims a large part of academy work resembles this cycle.

  3. Comfort with tools

    • At minimum, familiarize with Figma
    • Also consider:
      • Xcode / Mac environment
      • Presentation tools like Canva / Keynote

Does your portfolio need a finished app?

  • He argues the academy doesn’t strictly require a completed app.
  • Research depth, the learning process, and prototype/mocks can still be valuable.
  • Early-stage work may be framed as research/design first, potentially with minimal/no coding.

5) Portfolio Strategy (How to Present Your Work)

Theo’s “controversial” stance:

  • A portfolio is not just your apps.
  • Don’t treat it as a list of finished products.

A better approach is to show:

  • Problem → why it matters
  • Process step-by-step
  • Technology / design / UX choices and the reasoning behind them
  • Proof that the solution is useful (not only that it “works”)

Additional portfolio advice:

  • Prefer team projects and evidence you can collaborate, since the program is heavy on collaboration.
  • Build online presence / personal branding (learning journal), such as:
    • LinkedIn
    • Medium
    • Instagram
    • X
    • YouTube
  • He notes reviewers may “lurk,” so document your journey.

6) FGD: Behavioral Rubric (Process Over Ego)

Theo provides practical coaching for the FGD interaction.

  1. Empathy over ego

    • Avoid turning it into a debate where the goal is “winning.”
    • Aim for active listening and collaborative agreement-building.

  2. Not the “most correct” answer—best path to the answer

    • What matters is explaining how you arrived at a solution.
    • A messy team mindset weakens the value of a “best answer.”

  3. Think out loud

    • Show reasoning and frameworks, not just conclusions.
    • Helps the team generate multiple angles and improve later discussion rounds.

  4. Don’t kill the vibe

    • Use respectful, gentle criticism.
    • Don’t dominate or rush others.

  5. Be curious, not defensive

    • If challenged, don’t shut down—treat criticism as constructive.
    • Ask clarifying questions without sounding combative (e.g., avoid phrasing like “Why is your solution better than mine?”).

Theo reiterates that the academy prioritizes communication, collaboration, and team dynamics more than “being the smartest person.”

7) Technical Content Examples in the Test (As Described)

Theo describes the entry test as resembling:

  • Logic patterns (similar to CPNS-style seat/ordering puzzle questions)
  • Number sequence tasks (including permutations)
  • Pseudo-code interpretation / error identification
  • Basic data structures:
    • arrays/lists
    • linked list
    • stack
    • queue
  • Paradigms likely including OOP (other paradigms may appear too)
  • He also suggests the test may include design and basic business questions—not only programming

Main Speakers / Sources

  • Theo — software engineer, Apple Developer Academy Batch 7 alumnus, speaker of the video.
  • Apple Developer Academy (Binus registration portal referenced) — the program being explained. (No other speakers/source channels mentioned.)

Original video