Skip to main content
k-ID logo

Founding Content Creator

k-ID

Remote · USJobPosted 4 days agoStill listed 2 days ago

See where you stand before you apply. No sign-up to start.

You apply on the posting's application page, with no Olive account needed.

Watch jobs like this.

Don't just apply. Show up ready.

Olive works from this exact posting.

At a glance

Compensation
No compensation found
Location
Remote · US
Work Authorization
Not specified

Olive focuses on jobs in the United States, including remote roles you can work from there.

Job overview

k-ID is seeking a hands-on content creator to make Kai, its self-serve console and SDK for age- and jurisdiction-adaptive access and consent, visible to software builders. The creator will produce video and social content, develop founder voices and creator collaborations, and explain the technical story accurately. Success includes genuine audience engagement and observable product outcomes, reported honestly.

Skills & qualifications

RequiredNice to have

Skills

Social Work, nice to haveCompliance, nice to haveSDK, nice to haveVideo Production, nice to haveSocial Media Content, nice to haveVideo Editing, nice to haveTechnical Demonstrations, nice to haveInterviewing, nice to haveWriting, nice to haveIndependent Execution, nice to haveExperimentation, nice to have

Qualifications

Finished Video and Social Portfolio, requiredAttention-Earning Evidence, required

Full job description

Founding Content Creator

Make Kai impossible for builders to ignore. What would you make if your job was to take over the builder internet for the day? We’re looking for a hands-on maker with serious video craft, sharp social instincts and the ambition to create breakout moments. Someone who sees the hook, makes the thing and gets it in front of people. You want real views, real conversation and work developers remember when they build their next feature. Kai is k-ID’s self-serve console and SDK for age- and jurisdiction-adaptive access and consent. Builders declare what their product does; Kai configures the underlying Compliance Development Kit (CDK). Their app enforces the returned permissions. The question becomes: “What can this person do in my product, and what needs to happen first?” Your job is to make that story travel.

What you’ll do

  • Make the work yourself. Research, interview, write, record, edit, package and publish. Turn builder problems into screen-recorded demos, short videos, native posts and useful explainers. Own the hook, pacing, sound, captions, readable software screens, titles and thumbnails. Know when a simple screen recording is the strongest choice.

  • Create breakout moments. Build coordinated launches around a supported demo, a useful insight or a compelling builder story. Bring together a standout video or demo, platform-native edits, founder participation and credible distribution partners. Try to make Kai the thing builders are sharing today, then learn and launch again.

  • Develop founder voices. Interview our founders for their strongest ideas. Make distinct posts, videos and conversations that sound like them. Keep approvals lightweight and help them participate when builders respond. Give people a reason to follow their thinking, beyond reposting the company account.

  • Build precise creator collaborations. Find creators and practitioners who ship software and reach the right builders. Develop joint demos, interviews and launch assets. Carry the production work that makes collaboration easy. Own the brief, delivery, disclosure and distribution, choosing credible audience overlap over follower count or mass outreach.

  • Tell the technical story accurately. Use Kai, follow a supported integration with technical help and talk to builders about their decisions. Work with Product and Engineering to validate demonstrations. Explain age signals, consent and access permissions clearly. Keep limitations honest: Kai is not compliance certification or a guarantee of platform approval.

  • Improve through evidence. Choose a few formats you can make exceptionally well. Experiment with hooks, packaging and distribution; study what traveled and why. Participate usefully in builder communities. Report genuine reach and observable product outcomes separately, distinguish organic from paid delivery and reject manufactured engagement.

What you bring

  • Finished video and social work that shows your taste, editing ability and understanding of how each platform works.

  • Evidence you can earn attention: a launch, a cold-start channel, a breakout post or a creator collaboration you helped make happen.

  • Technical curiosity and the ability to make a software demo understandable without making unsupported claims.

  • Strong interviewing and writing instincts, with the range to preserve someone else’s voice.

  • The judgment to move quickly, finish work independently and learn from an experiment that missed.

We care about what you can make and explain. Famous logos and a large personal following won’t substitute for craft. Tools and AI can speed up production; your taste and judgment still decide what ships.

What success looks like More genuine views and impressions. Stronger sharing. Growing social audiences. Founder ideas reaching new circles. Launch moments that break beyond the people who already know us. Builder adoption matters too: people understand Kai, visit, sign up, integrate and keep using it where those outcomes can be observed. A big attention win matters before it becomes revenue. A large view count does not prove product use. We want both reported honestly.

Kai first You’ll report to Mike Mongeau, Head of Product, and work with Product, Design and Engineering. You own media, social execution, founder programming and selected creator collaborations; product decisions and compliance sign-off stay with their owners. Once a Kai approach works, we may reuse the production and launch kit for one bounded Ventures product, with an explicit priority and capacity decision, including what pauses. You won’t be running every venture at once.

How to apply Include a small portfolio of finished videos and social work you personally made. Tell us exactly what you did, the audience you were trying to reach, the observed results and their time window. Include one experiment that failed and what you learned. Be ready to walk through your source files and decisions. Finalists may be invited to a three-hour take-home exercise, with no live posting or outreach. If you’d rather make the thing than present the plan, we’d like to see your work.

Applicants Privacy Policy

How this job compares

Set against the 311 open Content Creator jobs on Olive Jobs, counted November 16, 2026.

Pay
  • This postingNot listed
  • California median$90–120K/yr23 salary ranges
  • US median$18–20/hr90 hourly ranges
Openings
Olive Jobs lists 64 open Content Creator jobs in California and 311 across the US. 16% of them nationwide are listed as remote or flexible.
Hiring the most in California
Experience
Content Creator postings that state a minimum ask for 3 years of experience at the median; the middle half ask for 2 to 5 years (135 postings).
Education
58 of the 311 open Content Creator jobs (19%) ask for a bachelor's degree or higher.

Counted across the open, public US postings on Olive Jobs on November 16, 2026. Figures based on too few postings are left out.

Prepare for this role

You've read the whole posting — now see how you match it.