If you have ever watched a coworker record a five-minute walkthrough video instead of writing three paragraphs nobody would read, you already understand why this role exists. Companies are leaning harder on async video for training, updates, and onboarding, and someone has to make sure that video tooling actually works the way a team needs it to.
This is a full-time, fully remote role. You can do it from home, a co-working space, wherever you focus best, since there is no office attached to this position and no particular country or city required. The team you would join is already distributed, so working across time zones and communicating mostly in writing and video is simply how things run here.
You will likely notice quickly that video itself becomes your default way of explaining things, which feels a little fitting given what the platform is built for. A quick screen recording usually clears up a confusing question in under two minutes, and once that habit sticks, typing out long instructions starts to feel slow by comparison.
The salary for this role is 81,500 dollars a year, and it comes with a solid benefits package on top. Health coverage, paid time off, and retirement plan matching are all included, along with a stipend specifically for ongoing platform training or certification, so staying current on the tools does not come out of your own pocket.
You will be the person who makes Loom actually useful for a company rather than just installed. That covers a lot of ground, from setting up workflows to catching the small breakages nobody else notices until a video will not upload.
Say a sales team keeps recording ten-minute rambling demo videos that prospects never finish watching. You would be the one running a short training session, tightening their template, and watching the completion rate climb over the following weeks. That kind of visible improvement is a normal part of the job here, not a one-off win.
You would also be working closely with whoever owns internal tooling more broadly, since Loom rarely lives in isolation. It usually connects to a CRM, a knowledge base, or a project-management tool, and keeping those connections working smoothly is part of what keeps the whole system reliable for everyone using it.
Most people who land this role hold a bachelor's degree in marketing, business, or a related field, and they have genuine hands-on experience configuring and managing a platform like this one, not just casual personal use of it. Two years of relevant experience, 24 months, is what employers are asking for. If you have spent that time inside a similar SaaS platform doing configuration, training, or workflow work, this should feel familiar rather than intimidating.
Platform certification helps where it is available, though it will not replace real experience. Problem-solving matters just as much: a lot of this job is figuring out why something broke for one team but not another, with limited information and someone waiting on an answer.
You do not need to have started your career in this exact niche. Plenty of strong candidates come from adjacent roles, marketing operations, customer success, or general SaaS administration, and pick up the platform specifics quickly once the fundamentals are already there.
It is a bonus, not a requirement, if you have experience with related SaaS tools such as Slack, Notion, or a CRM platform, since a lot of the integration work touches those systems too. Prior experience running internal training sessions is also a nice plus, even informally.
What tends to separate a strong candidate from an average one is not the length of a resume but how they talk about the platforms they have used. Someone who can describe a specific workflow they built, why they built it that way, and what changed for the team afterward stands out far more than someone who simply lists tool names.
Some days lean technical, digging through integration settings or permission errors. Other days lean human, walking a confused new hire through why their recording will not save, patiently, more than once if needed. There is rarely a week where both sides do not show up at least once. Remoteroles hears from candidates often that this mix is exactly what makes the role enjoyable rather than repetitive.
You will spend real time in written documentation too, building short guides so people can solve their own problems next time instead of messaging you again. Good documentation quietly saves you hours down the line, since a clear guide answers the same question for ten different people without you typing it out ten times.
Send a resume, and if you have one, a short Loom recording of yourself walking through a workflow or automation you built previously. It does not need to be polished. Reviewers care more about how clearly you explain your thinking than about production value, and applications are read in the order they arrive.
If you are currently between roles and worried a gap looks bad on paper, do not let that stop you from applying. What matters most here is whether you can walk into a messy setup, figure out what is broken, and fix it without needing someone standing over your shoulder the whole time.
We read every application that comes in, so there is no need to follow up multiple times in the first week. If your background fits, expect to hear back with a next step rather than silence.