Capability evidence
Assess one interaction through authoring, runtime, target, and recovery.
A scene that behaves in Play Mode proves a narrow authoring loop. Use one valuable interaction that crosses time, input, state, content, platform and release boundaries, then interrupt it. The person should be able to show what survives and why.
01Runtime state, input, player-loop timing, and simulation
Provide one multi-step interaction with keyboard mouse touch gamepad and an applicable spatial input; pause, focus loss, low and variable frame rates, slow loading, fixed-step backlog, asynchronous completion, object disable and destruction, scene change, process restart, saved progress, physics contacts and a simulation claim. Ask what owns every state and when code runs.
Confirm: The person separates product rules, presentation, component state, scene state, session state, durable save data and server truth; uses MonoBehaviour events deliberately instead of relying on incidental script order; keeps object and subscription lifetime explicit; places input sampling, fixed simulation, per-frame presentation and late visual work according to their semantics; handles zero or multiple fixed updates per rendered frame; records time scale, maximum step and pause behavior; models asynchronous work and cancellation without writing into destroyed owners; maps named input actions to supported control schemes and rebinding; isolates simulation parameters, units, seeds and validation; treats physics as an engine model rather than universal determinism; and restores only versioned validated state after interruption.
02Scenes, assets, serialization, tools, and content delivery
Provide source textures models animation audio text and data, their metadata and import settings, Prefabs and variants, ScriptableObject authoring data, additive and asynchronous scene loading, persistent objects, a saved-data change, Addressables groups and catalogs, local and remote bundles, a content-only update, interrupted download, cache pressure and an older installed player. Ask which artifacts are source, derived, compatible and trusted.
Confirm: The person preserves source rights and provenance, Unity metadata and stable asset identity; treats the Library and imported outputs as derived; owns units scale compression color audio animation mesh texture shader and platform import settings; prevents scene and persistent-object duplication; makes load activation and teardown observable; understands Unity field serialization, Prefab and Inspector consequences without using engine serialization as an unversioned save format; defines explicit durable schemas and migrations; maps Addressables keys labels groups dependencies load and release handles, profiles catalogs hashes bundles and cache behavior; keeps player and content versions compatible; preserves the content-state record needed for updates; uses secure transport and integrity checks for remote bundles; validates untrusted serialized data; and can return to a known compatible catalog and content set.
03Accessible targets, XR and native seams, and multiplayer authority
Provide two supported target classes with different graphics memory input window lifecycle and permission constraints, large and localized text, keyboard and assistive use, reduced motion, an XR or native capability where relevant, a native plug-in, a networked shared action, hostile client input, disconnect, late join and version mismatch. Ask what is shared and who is authoritative.
Confirm: The person shares product rules while keeping target configuration, rendering, quality levels, safe areas, aspect ratios, windows, lifecycle, permissions, storage and device capabilities explicit; builds semantic accessibility hierarchies only on supported platforms and still provides focus order, labels states values actions text scaling contrast captions remapping motion alternatives and human testing across all targets; treats XR comfort, boundaries, tracking and physical safety as client-owned acceptance areas; keeps native plug-in ABI architecture threading memory lifetime error and platform review visible; defines client server or distributed authority per state and consequence; rejects and rate-limits untrusted input; separates prediction and presentation from accepted shared state; handles spawn ownership ordering snapshots reconciliation latency loss disconnect reconnect late join and migration; and does not treat an engine package as a complete threat model, identity service, moderation policy or reliable backend.
04Tests, target profiling, builds, release, and recovery
Provide pure rules, authored content, scenes, input, persistence, asynchronous loading, network behavior and a native seam; representative devices; frame memory loading network power and thermal budgets; exact player and Addressables builds; a package or editor upgrade; a crash or performance trace; signing and store boundaries; and a receiving owner. Ask which evidence belongs to each target and release.
Confirm: The person layers ordinary C# tests, Edit Mode and Play Mode checks, asset and scene validation, integration and network tests, deterministic fixtures where justified, and real player flows without mocking away the boundary under review; profiles development players on target devices and accounts for profiling overhead rather than using Editor results as release evidence; separates main render job audio physics scripting garbage-collection GPU and platform costs; measures representative and adverse frames, allocations memory residency loading storage network power and thermal behavior against budgets; pins the Unity editor patch, project settings, package manifest and lock, source asset and metadata revisions, render pipeline, scripting backend, compiler, platform SDK, native plug-ins, Addressables profile and build profile; builds in a controlled environment; preserves logs reports symbols mappings catalogs hashes content-state and player artifacts; stages only through approved signing and distribution roles; checks player and content compatibility; diagnoses one field failure; and demonstrates rollback or a compatible forward correction and rebuild to another owner.
