<h3>Build It Clean. Launch It Right. Scale It Stable. 🔧🚀</h3><p>Creators move fast. But when things break, lag, misfire, or fail to integrate? Momentum stalls.</p><p>That’s where you come in. You don’t just love the launch moment. You love what happens before it.</p><p>▶️ The <strong>structure</strong>.</p><p>⏩ The <strong>configuration</strong>.</p><p>⏭️ The “let’s make sure this <strong>passes review the first time</strong>.”</p><p>At <a href="https://himalayas.app/companies/passion-io">Passion.io</a>, <strong>we’re evolving fast</strong> - rolling out <strong>AI-powered features</strong> that accelerate how creators build and scale their apps. And, yes you guessed it. Where speed increases…. Complexity does too.</p><p>Which means… <strong>This isn’t traditional Customer Success either. </strong></p><p>This is <strong>technical ownership</strong> inside a high-growth <strong>creator platform</strong>. This role exists to guide customers through <strong>build → QA → App Store submission → optimisation → long-term stability. </strong></p><p>So launches feel smooth, not stressful. </p><h3>Not Reactive. Reliable. </h3><h3>You don’t just answer “how-to” questions.</h3><h3>✅ You diagnose.</h3><h3>✅ You optimize.</h3><h3>✅ You future-proof.</h3><h3>🖥️ A Day in Your Launch Pipeline</h3><p>You’ll <strong>manage a</strong><strong>portfolio of ±45 creators </strong>who need <strong>deeper technical partnership</strong> -primarily US-based (so yes, <strong>EST/PST is part of your rhythm).</strong></p><h3>On any given day, you’re:</h3><ul><li>Troubleshooting <strong>complex</strong> platform <strong>configurations</strong></li><li>Reviewing <strong>integrations and automation logic</strong></li><li><strong>Advising on backend setup</strong> to support scale</li><li>Diagnosing <strong>root causes</strong> behind feature friction</li><li>Guiding creators through <strong>technical implementation</strong> decisions</li><li>Partnering with Product on <strong>advanced use cases</strong></li><li><strong>Translating technical</strong> possibilities into <strong>clear action</strong></li><li>Escalating technical blockers with <strong>structured documentation</strong></li><li>Ensuring <strong>adoption of SDK updates</strong> or platform changes</li></ul><p><strong>You’re not patching issues. You’re engineering smoother outcomes. ⚛️</strong></p><h3>🔁 A Week in Your System</h3><ul><li>Run <strong>technical launch-readiness</strong> reviews</li><li><strong>Review crash logs</strong> and performance signals</li><li><strong>Identifying recurring friction patterns</strong> across portfolios</li><li><strong>Escalating</strong> true platform issues <strong>with clarity and context</strong></li><li><strong>Validate new feature releases</strong> before wider rollout</li><li>Monitor <strong>compliance </strong>updates from <strong>Apple &amp; Google</strong></li><li>Documenting <strong>technical best practices</strong></li><li>Improving<strong> implementation</