Engineering Team Lead

Salary Range: 195000 to 215000 (Currency: USD) (Pay period: per-year-salary)

What Success Looks Like:

• Measurable impact shipped → Initiatives launch with defined success metrics and honest post-launch analysis — and by the end of your second quarter, your team's work has visibly moved metrics the business cares about.

• A faster, more autonomous team → The team ships measurably faster than when you joined, engineers deliver end-to-end without you in every decision, and your reports are visibly leveling up.

• Quality by design → Quality and performance don't erode as the team ships — SLOs guard them, feature work stays balanced against maintenance, bugs get addressed instead of accumulating, and UX improves proactively.

• Architecture that holds → Your design decisions hold up as the product grows — new features get easier to build, not harder, and design flaws get caught in review, not production. 

• Trust through ownership → You communicate early and own outcomes — surfacing misses before they surprise anyone — so partners trust you and bring you problems, not tickets.

What You'll Do:

Own delivery end-to-end across the team's full surface — mobile, web, and backend — and the business outcomes it drives.

Partner closely with product, design, and growth — bring engineering reality into roadmaps early and evaluate UI/UX for the customer and the business, not just function.

Run intake and prioritization: sequence work against business objectives, keep concurrent projects on track, and set realistic commitments — what ships, what waits, and why.

Start big bets small: ship the thinnest slice that proves the idea, and grow it only on evidence.

Lead and grow the team — 1:1s, feedback, and career development.

Protect quality systematically — SLOs as guardrails, feature work balanced against maintenance, rigorous code review, and a release pipeline that catches regressions before customers do.

Set technical direction and architecture — scope cross-stack features to land as one coherent change, and pressure-test plans for risk before the team commits.

Build the factory, not just the product: embed AI and data into how the team works, so everyone ships faster, learns from every release, and stays pointed at impact.

We're Looking for Someone With:

• A track record of leading engineers. 8+ years building software, including leading a team — formally or informally — and growing the engineers around you. This is the core of the role.

• Strong architecture and code review. This is how you lead — you set technical direction and strategy through sound system design and give the kind of code review that makes engineers better, spotting risk and design flaws before they ship.

• Full-stack technical judgment. Deep enough knowledge across mobile, web, and backend to review across the stack and evaluate what your team builds — even where you're not the one writing it.

• Deep iOS expertise. You've built and shipped production iOS apps with real depth (Swift/SwiftUI) — it's our lead platform and where most of our customers are — with solid Android (Kotlin/Jetpack) alongside. It's the technical foundation this role builds on.

• Stakeholder management and expectation setting. You partner cross-functionally with product, design, marketing, and partners — communicating trade-offs and keeping everyone aligned as priorities shift.

• A product and business mindset. You prioritize business objectives and measure success by value delivered — what moves the metrics — not by raw output or precise task estimates.

• Prioritization in a high-demand environment. With more good ideas than capacity, you triage competing requests, sequence against capacity, and say no well.

• High-traffic product sense. You've worked on consumer products at scale (e-commerce or similarly demanding), and you care about performance, reliability, and the customer experience that flows from them.

• AI fluency, clear written communication, and a collaborative default. You share context freely and disagree-and-commit when it's time to move.

You don't need to tick every box. If most of this sounds like you, we'd love to hear from you.

Nice to Have:

Hands-on experience with React / Next.js for the web and webview surfaces.

Experience designing and building REST/GraphQL APIs (we use Node, Python, and Java/Groovy on the backend).

Experience with CDP and lifecycle-messaging / marketing-automation platforms.

Experience with cross-platform tooling (React Native or Kotlin Multiplatform) — there are opportunities to share more across platforms.

Experience with mobile CI/CD and release automation (Fastlane, phased rollouts, feature flags).

Background in ticketing, live events, payments, or complex third-party integrations.

Experience with observability and crash reporting tooling (Datadog, Crashlytics, or similar).

 

OUR STACK

We use the right tool for the job. On mobile that means native iOS and Android, with React Native in the mix. On web it's React/Redux/Next.js, including the webviews embedded in the apps. The backend includes Node, Python, and Java/Groovy, backed by AWS Aurora, MongoDB, Redis, Elasticsearch, and Datadog, with a dedicated CDP and lifecycle-messaging layer for personalization. Any of it could change if there's a good enough reason.