Full-Stack Growth Engineer
Anywhere in the World·Posted 1mo ago
<img src="https://we-work-remotely.imgix.net/logos/0170/8761/logo.gif?ixlib=rails-4.0.0&w=50&h=50&dpr=2&fit=fill&auto=compress" /> <p> <strong>Headquarters:</strong> St. Petersburg, FL <br /><strong>URL:</strong> <a href="https://www.clipp.com/">https://www.clipp.com/</a> </p> <p>High-autonomy. Fast-growing startup. You ask the right questions before you start, then ship fast — clarifying scope with non-technical stakeholders and having something live by the end of the week. This is a role for builders and operators who know that 10 minutes of good questions beats a week of building the wrong thing.</p> <h2 class="section-h2">What you'll own end‑to‑end</h2> <ul class="styled-list"> <li>Ship onboarding automations, lifecycle triggers, and customer task queues — not one-off scripts, real systems</li> <li>Analytics pipelines and dashboards non-technical stakeholders can self-serve from day one</li> <li>A/B test infrastructure the team can run without engineering tickets</li> <li>Take a brief cold, ask sharp clarifying questions to align on scope, then own it from start to ship</li> </ul> <div> <h2 class="section-h2">The Builder <em>or </em>The Operator</h2> <p>You might be one, or both. Either will thrive here. What matters: startup experience, genuine product sense, and the ability to translate a vague ask into a working system.</p> </div> <div> <div class="section-eyebrow">What we're looking for</div> <ul class="styled-list"> <li>3–6 years full-stack engineering, startup background strongly preferred</li> <li>You ask sharp clarifying questions before starting — you'd rather spend 10 minutes aligning on scope than a week building the wrong thing</li> <li>You can translate vague business problems into working technical systems</li> <li>Genuine product sense — you care whether what you built moved the metric</li> <li>Experience in PLG, growth, activation, or onboarding engineering is a plus</li> <li>High autonomy — but you proactively surface blockers and check assumptions early rather than going dark and resurfacing with the wrong thing</li> </ul> <p>Application instructions here: <a href="https://grow.clipp.com/">https://grow.clipp.com/</a></p> </div> <p><strong>To apply:</strong> <a href="https://weworkremotely.com/remote-jobs/clipp-com-full-stack-growth-engineer">https://weworkremotely.com/remote-jobs/clipp-com-full-stack-growth-engineer</a></p>