Founding Mobile Engineer

About the role

This role owns and defines the mobile experience for a social commerce platform, delivering AI capabilities to brand teams through a mobile interface.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Ownership of the mobile platform end-to-end drives architecture, building, and shipping of a React Native application for iOS and Android, delivering AI-powered social commerce experiences directly to brand teams and customers.

Setting of reliability and performance standards through monitoring, error tracking, and optimization ensures mobile environments.

Requirements

Deep software engineering expertise with React Native spans 5+ years of professional practice.

A proven track record exists for shipping high-quality production mobile applications in real-world conditions.

Strong understanding of mobile architecture, navigation patterns, state management, and platform-specific nuances is required.

Experience integrating with external APIs and building real-time, data-intensive features is necessary.

Comfort operating across the full stack is needed in a fast-moving startup environment.

An ownership mindset drives action, and comfort with ambiguity is required when shaping product direction.

Product intuition guides decisions about what gets built, not only how solutions are implemented.

A degree requirement is stated and must be met.

Nice to have

Hands-on experience with native iOS or Android development or bridging native modules adds depth.

Background in social media platforms, e-commerce systems, or commerce infrastructure informs design decisions.

Exposure to LLMs, AI agents, or machine learning-powered features in production enhances impact.

Previous founding or early-stage startup experience accelerates team collaboration.

Open-source contributions or notable side projects demonstrate sustained engineering engagement.

Practical notes

The role follows a hybrid model with 4 days in the office and 3 flex remote days per quarter after a 3-month period.

Compensation includes health, vision, and dental benefits plus a 401(k) match, with additional stipends for housing, mobile, internet, and commuter benefits.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Mobile engineers operate at the intersection of product, design, and engineering to define user-facing experiences.

Social commerce platforms combine community conversation with transactional flows, requiring tight integration between product and technology.

AI-native systems personalize and guide interactions, demanding reliability, performance, and thoughtful architecture on mobile devices.

Early-stage environments expect cross-functional contribution, fast iteration, and comfort with evolving priorities.

Engineering practices such as testing strategies, CI/CD pipelines, and monitoring shape long-term maintainability and release confidence.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.