About MobiLoud
MobiLoud helps established ecommerce brands turn their existing websites into iOS and Android apps, without rebuilding their product or managing two separate systems.
We work with ecommerce businesses doing real volume that want a direct mobile channel they actually own. Our customers use MobiLoud to lift retention, recover abandoned carts through push, and reduce their dependence on paid acquisition.
We’re a bootstrapped, profitable, remote-first SaaS company founded in 2013. We’ve served 2,000+ brands and have hundreds of active customers today, including Estée Lauder, John Varvatos, Jack & Jones, and Tadashi Shoji. 13 years profitable. We’ve never raised a round, and we never need to. Our team is 16 people, all remote, all hands-on, all trusted to work independently.
The role
This is the technical implementation seat behind the Customer Success Manager. When a merchant launches their app and our CSM proposes a play, you’re the one who wires it up: the GA4 events, the push segments, the abandoned cart push, the Klaviyo Push integration, the Databox dashboard the merchant looks at every Monday morning.
This is not a developer role and it is not a relationship-led customer success role. It’s a hands-on configuration and integrations role. You’ll spend most of your week inside Google Analytics, OneSignal, Klaviyo (on the push side, not the email side), Shopify, WooCommerce, and our own admin panel, getting the wiring right so the merchant’s stack actually works the way the CSM promised.
You’ll work alongside our Customer Success Manager, who owns the merchant relationship and the strategy. They propose the play; you make it real. You report to our Customer Success Lead and sit on the Operations team. You also coordinate with the engineering team when something needs a native change, and you produce a clean reproduction case so they can act on it without re-litigating the bug.
The role is one of two we’re opening to build out the CS function. We’ve split this work across the founding team and a generalist for too long. This seat takes ownership of the technical implementation side as a proper function, with room to shape the playbook and the toolkit.
What you’ll do
- Configure analytics for newly launched apps: GA4 event tracking, ecommerce events, Shopify and WooCommerce reporting, attribution sanity checks
- Set up push notification infrastructure (OneSignal and Klaviyo Push) for new launches. Opt-in flow, segments, campaign templates, abandoned cart push
- Build the Klaviyo Push integration on accounts that use Klaviyo. You’re working with their existing email flows on the trigger side, not building the email flows themselves
- Build and maintain reporting dashboards (Databox or equivalent) so each merchant has a weekly view of the metrics that matter
- Investigate root causes when tracking, attribution, or push is broken or wrong. Implement long-term fixes so the same break doesn’t happen twice
- Act as the technical escalation point during onboarding and ongoing operations. When a fix is in scope, you ship it; when it needs engineering, you write the reproduction
- Document the configuration of every merchant in your portfolio so the next person who looks at it doesn’t start from zero
- Stay current on the platforms we touch. GA4, OneSignal, Klaviyo, Shopify, WooCommerce, and the analytics ecosystem move; you keep us moving with them
Who you are
- Two to five years in technical customer success, implementation, onboarding, or solutions work at a B2B SaaS company serving ecommerce
- Hands-on with GA4 and Google Tag Manager. You’ve debugged broken events, missing ecommerce data, and attribution mismatches yourself, not handed them off
- Comfortable in Klaviyo. You can segment lists, set up triggers, and connect data sources. You don’t need to be a Klaviyo email-flow expert; you do need to know your way around the platform
- Comfortable with Shopify and WooCommerce admin and reporting. You don’t need to write Liquid or PHP, but you know where the data lives
- Comfortable picking up new tools in this category. You haven’t used OneSignal or Databox? Fine, you’ll learn them in week two. You’ve never touched anything like them? That’s the problem
- Read and write JSON, run a Postman request, follow a webhook payload. The configuration work assumes this baseline
- You finish what you start. Half-configured flows, broken events left to drift, undocumented setups are the failure mode this role is built to prevent
- Native or near-native English. Comfortable overlap with Eastern Time business hours for sync with the CSM and the engineering team
Why this role
- You own the technical execution behind every growth play we run for our merchants. The push that actually segments, the events that actually fire, the dashboard that actually reports
- The CS function is being built from the ground up. Decisions on tooling, process, and scope happen in the same week, not the next quarter
- You partner with the Customer Success Manager directly. Strategy and execution live next to each other, not in different orgs
- The merchants you’ll touch are real ecommerce brands with real revenue on the line. Estée Lauder, John Varvatos, Jack & Jones, Tadashi Shoji, plus the next tier of mid-market names across Shopify, BigCommerce, Magento, and WooCommerce
- Room to shape the playbook, the tooling, and how this function runs going forward
- Fully remote, work from anywhere. We have no office and no plans to open one
Not a fit if
- You want to write production code all day. The fixes you’ll ship are inside platform admins, not in our app codebase
- You want pure relationship work. The merchant relationship lives with the CSM; your work is the configuration behind it
- You need a finished playbook handed to you. We have data and patterns, not a step-by-step runbook for every merchant scenario
- You need full-time employee benefits (healthcare, parental leave, equity). This is a contractor engagement, not employment. PTO is unlimited; the gaps are healthcare, parental leave, equity
- You only want to work with one platform. Our merchants span Shopify, BigCommerce, Magento, Salesforce Commerce, and WooCommerce. You’ll touch all of them
Apply for this role
Takes about 5 minutes. We read every application and respond within a week, either way.
Specifics matter. Walk us through real configurations and real bugs you've shipped fixes for - it tells us more than tool name-drops.
Application received
Thanks for applying. We read every application and will get back to you within a week, either way.