Member of Technical Staff, Application Engineering

You will own the application layer that users actually touch.

Onix is building Personal Intelligence: AI that runs on your device, belongs to you, and connects you with real human expertise. We have a mobile app (React Native), a web app (React), and cloud infrastructure tying it all together. Someone needs to own the full surface. Build features that ship to both platforms. Make the experience fast, coherent, and worth coming back to.

You are that person.

The application layer is where the product lives or dies. The best AI in the world is useless if the app is slow, confusing, or unreliable. You understand that deeply, and it motivates you.

• Build and ship features across React Native (iOS/Android) and React (web) from a shared codebase where possible
• Own frontend architecture decisions: state management, navigation, component systems, and performance
• Work with cloud infrastructure (serverless, edge compute, real-time messaging) to deliver responsive, reliable experiences
• Implement AI-powered interfaces: conversational UIs, streaming responses, and context-aware interactions
• Collaborate directly with product and design to translate user needs into shipped software

You have built production React Native apps that real people use daily. Not a side project, not a tutorial. An app that had to handle edge cases, performance constraints, push notifications at scale, and the thousand small things that separate a demo from a product. You have also built production web apps in React and you move fluidly between the two.

You care about the user experience at a level that goes beyond pixel-perfect implementation. You think about loading states, error recovery, offline behavior, and what happens when the network drops mid-conversation. You have opinions about when to use optimistic updates, how to structure a design system that works across platforms, and why most chat UIs are bad.

You have:

• Production experience with React Native and React, not one or the other, both
• Experience with cloud infrastructure: serverless functions, real-time databases, edge compute, CDNs, or similar
• Familiarity with mobile-specific concerns: app store deployment, push notifications, performance profiling, native modules
• Experience building real-time or streaming interfaces (chat, collaboration tools, live data)

You are:

• A product thinker who happens to write code. You ask “why” before you build
• Fast. You ship features in days, not sprints. You are comfortable with velocity
• Detail-oriented about UX. Janky animations and slow transitions bother you personally
• Comfortable owning decisions. You do not wait for a tech lead to tell you which library to use

• You are primarily a web developer who has dabbled in React Native
• You prefer working on one platform and handing off to another team for the other
• You need a detailed spec before you can start building
• You are not interested in AI-powered product experiences
• You want a remote job

• Features ship to both mobile and web simultaneously, not as separate projects
• The app feels fast and polished. Users comment on how good the experience is
• You have established patterns and component systems that make the next engineer faster
• Cloud infrastructure decisions support the product without over engineering
• You can pick up a feature from design mockup to production deploy without a handoff chain

Submit your application and answer:

• Show us a React Native app you built that is in production. What was the hardest technical problem you solved in it?
• How do you approach sharing code between React Native and React web? Where does it work and where does it break down?
• Describe a time you made a product decision (not just a technical decision) that improved the user experience. What did you notice that others missed?