Software Engineer || (plugin and libraries)

This role exists because libraries fail in ways that game code does not. We want someone who has already run into these problems and has opinions about them:

● Designing a small, clean API surface and keeping it stable as the number of consumers grows.

● Semantic versioning and managing breaking changes across multiple live projects sitting on different engine versions.

● Native interop — JNI and Objective-C/Swift bridging, marshalling, and memory ownership across the managed/native boundary.

● Dependency and transitive dependency conflicts: Gradle/AAR collisions, duplicate symbols, CocoaPods and Swift Package version pinning.

● Build system integration: Gradle templates, Xcode post-process build steps, Unreal .Build.cs and .uplugin configuration.

● Threading and lifecycle correctness — main-thread marshalling, application pause/resume, and background callbacks re-entering managed code.

● Debugging failures inside a consumer’s project that you cannot reproduce locally: logging strategy, symbolication and crash triage.

● Binary size, startup cost, and the implications of code stripping, IL2CPP or equivalent on what you ship.

● Keeping up with editor tooling changes and first-party SDK and policy churn without breaking downstream projects.

● Shipped titles live on Android or iOS.

● Gameplay systems experience — Finite State Machines, Behaviour Trees, animation or physics integration.

● Editor tooling: custom inspectors, importers or build automation in Unity or Unreal.

● Rendering awareness — shaders, batching, draw call and overdraw budgets.

● Integrating third-party game SDKs such as analytics, ads, IAP or attribution.

● Performance work on low-end devices: memory budgets, GC pressure and frame pacing.

● Open-source contributions or a published package used by others.