Mobile & Desktop Engineer

Role overview This role owns the mobile and desktop experience across a small engineering team, working where shared product code meets platform-specific implementation. The mobile client is built with Expo and React Native, with native Swift work where the platform requires it, and the desktop client is built with Electron and needs to reach Windows. It suits an engineer who cares about everyday interaction, release safety, and recovery, not just shipping builds.

Responsibilities - Build and refine React Native mobile flows with attention to navigation, responsiveness, offline behavior, and the small details that make a daily-use app feel trustworthy - Use Swift where native iOS capabilities or integrations need it, keeping the boundary with shared application code clear and maintainable - Help adapt and ship the Electron desktop application for Windows, including platform-specific behavior, packaging, installation, updates, and recovery - Partner with product and infrastructure engineers on contracts, tests, release readiness, and bugs that cross the app and service boundary - Reproduce issues from real customer use, explain root cause clearly, and turn recurring friction into better client behavior

Requirements - Track record of shipping and maintaining a mobile or desktop application people rely on, beyond a prototype - Strong TypeScript skills and comfort with React Native or Electron - Ability to work in Swift when a feature genuinely needs native code - Comfort crossing between shared product code and platform-specific work without forcing one platform's patterns onto another - Based in the United States or Canada, with overlap for product, engineering, and customer-facing work

Nice to have - Experience taking an Electron application from one desktop operating system to another and owning the release details - History building a React Native application with a deliberate native Swift boundary - Work improving offline or unreliable-network behavior in a client application - A specific product detail made materially better after watching someone use it

Benefits and work setup - Small, distributed engineering team - Reports to the founder, working closely with product and infrastructure leads, and direct access to customer context - Heavy use of AI tooling, careful review of consequential changes, and clear ownership of work after release - Compensation combines cash and meaningful equity, aligned early in the process - Interview process includes a founder conversation, a walkthrough of a mobile or desktop feature with a platform-specific challenge, a paid scoped working session on a realistic client problem, and a final conversation on mandate and compensation