Software Engineer in Swift + SwiftUI with real AppKit experience

Job Role: Software Engineer in Swift + SwiftUI with real AppKit experience

Location: 100% Remote

Long Term Contract

Swift + SwiftUI with real AppKit experience.

The Finder-grade file browser leans heavily on AppKit (NSCollectionView, NSTableView, NSBrowser, NSPathControl via NSViewRepresentable), so hands-on AppKit experience matters here.

 Who you are:

You're a true full-stack engineer. You're as at home in a native macOS app written in Swift as you are in a Rust systems core, and you care as much about the seams between them as the code on either side. You like owning a problem end-to-end, and you're drawn to a place where the surface area is big and the impact is visible. You're happy going deep on something you haven't touched before, and you have the judgment to work within an established architecture rather than around it.

There's a lot of ownership here, whatever your level. You'll collaborate closely with product and design without being micromanaged, own real surface area early, and see your work in front of users fast.

What you'll do:

·      Own customer-facing features end-to-end, across the Swift/SwiftUI client and the Rust backend that powers it.

·      Build and evolve the Finder-grade file browser, bridging AppKit (NSCollectionView, NSTableView, NSBrowser, NSPathControl) into SwiftUI where SwiftUI alone won't cut it.

·      Design and evolve the gRPC / Protobuf contract between the app and the agent as the product grows.

·      Work in a large Rust workspace of shared crates — async/tokio, fault-tolerant, built to run reliably on customers' machines.

·      Ship native: code signing, entitlements, notarization, sandboxing, launchd services, and real observability (os.Logger and friends).

·      Balance speed, performance, and future scalability — and know which one matters most for the change in front of you.

Must-have (core, non-negotiable)

·      Swift + SwiftUI with real AppKit experience. The Finder-grade file browser leans heavily on AppKit (NSCollectionView, NSTableView, NSBrowser, NSPathControl via NSViewRepresentable), so hands-on AppKit experience matters here.

·      Rust — async/tokio, comfortable in a large workspace of shared crates.

·      Strong concurrency and async on both sides: Swift async/await (MVVM, @Observable) and Rust tokio/futures.

·      gRPC / Protocol Buffers — designing and evolving a versioned RPC contract as clients evolve.

·      macOS platform fluency — launchd services, code signing, entitlements, notarization, sandboxing, os.Logger.

Where you could make a big impact

·      Strong candidates will have some of these — and going deep in any one is a way to have outsized impact on the product.

·      GraphQL client work (Apollo iOS or equivalent — normalized caching, codegen, subscriptions).

·      Filesystem internals — FUSE / FSKit / WinFSP, NFS mounts, FSEventStream / inotify-style change observation. This is the hardest-to-hire and highest-leverage skill on the team.

·      P2P and networking systems — WebRTC, NAT traversal, signaling, WebSockets, NATS or similar message transport.

·      Cross-platform systems thinking — the agent also runs on Windows (WMI, Windows services, winreg, WinFSP).

Nice to have / bonus

·      Rust ꠏbjC interop (objc2), or FFI experience generally.

·      Media-pipeline exposure — GStreamer, AVFoundation, thumbnail / transcode workflows.

·      Secure secret storage and auth flows — OAuth2, Stronghold / Keychain, Argon2.

·      XcodeGen or other project-generation / reproducible-build tooling.