Video Editor
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include all content from sections, but formatted.
Let's extract content:
About Us: "Base360.ai is building the AI operating system for short-term rental companies. Born from the technology behind The Flex, our platform helps property managers launch, operate, and scale their businesses on AI autopilot." This is about company, not role. Should we include? The instruction: Use headings for sections like About the role, Responsibilities, etc. About Us is not listed; maybe we can omit because not a required heading. But we must preserve ALL substantive information. However we cannot invent headings not allowed. Could we include About Us as a paragraph without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs without heading. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but we should follow those headings for sections. Probably we should include About Us as a
before any headings, as it's substantive. That seems okay.
About The Role: "You'll turn raw footage, product recordings, and ambitious ideas into launch films, social content, and ads that capture attention and hold it. This is a hands-on creative role for someone who understands storytelling, pacing, sound, and motion. You'll help shape the concept, find the strongest hook, and take each video through to its final cut. Your work will show short-term rental operators what’s possible with Base360—and tell the story of the people building it."
What You'll Do: list of duties (multiple sentences each starting with a verb). We'll make
- each.
Who You Are: list of attributes: "You have a strong portfolio that demonstrates storytelling, editing craft, and visual taste. You're proficient in Premiere Pro, DaVinci Resolve, or Final Cut Pro, with motion design skills in After Effects or an equivalent tool. You know how to hook viewers in the first three seconds—and give them a reason to keep watching. You can turn a long recording into a concise, compelling story. You understand how music, silence, sound effects, and pacing shape emotion. You're comfortable using AI tools such as Runway, Kling, Sora, and ElevenLabs as part of your creative workflow. You work independently, meet deadlines, and respond well to direct feedback. You balance speed with quality and care about the details that make work feel polished. Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus."
Why join Base360.ai?: bullet points: "Help shape the video identity of a growing company from an early stage. Work directly with the founder on product launches, storytelling, and building in public. Take creative ownership and see your work published across our brand and marketing channels. Grow into broader creative leadership, with the opportunity to help build a video team. Competitive salary and performance-based incentives. Remote working in an ambitious, entrepreneurial team."
Our expectations: "We value ownership, direct communication, high standards, and continuous improvement. You'll thrive here if you enjoy taking initiative, experimenting, and pushing your craft."
You Should NOT Join Base360.ai If: list of negatives.
We need to map to sections: About the role (maybe combine About The Role and About Us? Actually About the role heading should contain the About The Role paragraph). Responsibilities: What You'll Do. Requirements: maybe Who You Are (core requirements). Qualifications: maybe Experience with SaaS product videos... plus proficiency? But we already used Who You Are for requirements. Could treat Qualifications as "Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus." But that's a plus, not required. Could also include proficiency in software as qualifications. However we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one? But instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including who you are and qualifications), Benefits, Pay, Schedule. Skills maybe not needed if covered in Requirements. But we need to follow headings list; we can omit sections lacking real specific content. So we can omit Skills if we don't have a distinct list beyond what's in Requirements. But we have a list of proficiencies; could be Skills. However we could put them under Requirements as part of who you are. That may be okay.
Benefits: from Why join Base360.ai? includes items: shape video identity, work directly with founder, creative ownership, grow into broader creative leadership, competitive salary and performance-based incentives, remote working. But we already have Pay and Schedule separate; we might move salary and remote to Pay and Schedule, leaving other benefits.
Thus Benefits section: Help shape the video identity..., Work directly with the founder..., Take creative ownership..., Grow into broader creative leadership..., Opportunity to help build a video team.
Pay: Competitive salary and performance-based incentives.
Schedule: Remote working in an ambitious, entrepreneurial team.
We also have Our expectations and You Should NOT Join... Could be omitted? They are substantive but not matching headings. Could we include them as a section like "Expectations" but not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create other headings. We could incorporate that prose into existing sections, maybe under About the role or Benefits? But they are distinct. However we must preserve ALL substantive information. If we cannot add a heading for them, we could embed them as paragraphs without heading, which is allowed? The instruction didn't forbid extra paragraphs. It said use for section headings (e.g ...). It didn't say you cannot have other headings, but to follow that pattern. Safer to include them as
without heading, maybe after the sections. That would preserve info.
Thus final HTML: start with a
for About Us. Then
About the role
...
. Then Responsibilities
- ... each duty
. Then Requirements
... combine Who You Are and maybe qualifications? We'll put the whole Who You Are paragraph(s) as
(maybe multiple sentences). Could also split into
but it's not a list; it's prose. We'll keep as . Then
Benefits
- ... each benefit except salary and remote
. Then Pay
Competitive salary and performance-based incentives.
. Then Schedule
Remote working in an ambitious, entrepreneurial team.
. Then maybe add for expectations and negative statements as prose.
Check for any duplicated lines: none.
Make sure not to include any boilerplate like cookie/navigation etc. Not present.
Now craft HTML.
Let's list duties:
- Edit product launches and brand films that combine storytelling, product demonstrations, and strong visual direction.
- Create founder-led content from interviews, talking-head footage, and behind-the-scenes moments.
- Produce short-form videos for Instagram Reels, TikTok, YouTube Shorts, and LinkedIn, with strong hooks and purposeful pacing.
- Build paid ad creative with variations in openings, messaging, and calls to action.
- Bring the product to life through screen recordings, motion graphics, kinetic typography, and clear visual explanations.
- Own post-production including footage selection, editing, colour grading, sound design, music, captions, and final exports.
- Use AI creative tools to generate supporting visuals, voiceovers, and other assets where they improve the result or speed up production.
- Maintain a consistent visual identity across formats and channels.
- Improve content through performance insights, using retention, watch time, and conversion data to inform future edits.
Now Who You Are content: We'll make a paragraph with sentences.
"You have a strong portfolio that demonstrates storytelling, editing craft, and visual taste. You're proficient in Premiere Pro, DaVinci Resolve, or Final Cut Pro, with motion design skills in After Effects or an equivalent tool. You know how to hook viewers in the first three seconds—and give them a reason to keep watching. You can turn a long recording into a concise, compelling story. You understand how music, silence, sound effects, and pacing shape emotion. You're comfortable using AI tools such as Runway, Kling, Sora, and ElevenLabs as part of your creative workflow. You work independently, meet deadlines, and respond well to direct feedback. You balance speed with quality and care about the details that make work feel polished. Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus."
Now Benefits list (excluding salary and remote):
- Help shape the video identity of a growing company from an early stage.
- Work directly with the founder on product launches, storytelling, and building in public.
- Take creative ownership and see your work published across our brand and marketing channels.
- Grow into broader creative leadership, with the opportunity to help build a video team.
Now Pay paragraph: Competitive salary and performance-based incentives.
Schedule paragraph: Remote working in an ambitious, entrepreneurial team.
Now expectations paragraph: "We value ownership, direct communication, high standards, and continuous improvement. You'll thrive here if you enjoy taking initiative, experimenting, and pushing your craft."
Now negative paragraph: "You should NOT join Base360.ai if you prefer detailed instructions for every task over taking creative ownership; you're looking for a predictable, slow-paced role with little change; you struggle with direct feedback, revisions, or testing new approaches; you care more about making videos look good than whether they tell a story and deliver results; you avoid learning new tools or adapting your creative process; you bring ego or office politics instead of collaboration and accountability; you aren't motivated to
for prose. We need to preserve all substantive information. So we need to include all content from sections, but formatted. Let's extract content: About Us: "Base360.ai is building the AI operating system for short-term rental companies. Born from the technology behind The Flex, our platform helps property managers launch, operate, and scale their businesses on AI autopilot." This is about company, not role. Should we include? The instruction: Use headings for sections like About the role, Responsibilities, etc. About Us is not listed; maybe we can omit because not a required heading. But we must preserve ALL substantive information. However we cannot invent headings not allowed. Could we include About Us as a paragraph without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs without heading. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but we should follow those headings for sections. Probably we should include About Us as a
before any headings, as it's substantive. That seems okay. About The Role: "You'll turn raw footage, product recordings, and ambitious ideas into launch films, social content, and ads that capture attention and hold it. This is a hands-on creative role for someone who understands storytelling, pacing, sound, and motion. You'll help shape the concept, find the strongest hook, and take each video through to its final cut. Your work will show short-term rental operators what’s possible with Base360—and tell the story of the people building it." What You'll Do: list of duties (multiple sentences each starting with a verb). We'll make
- each.
Who You Are: list of attributes: "You have a strong portfolio that demonstrates storytelling, editing craft, and visual taste. You're proficient in Premiere Pro, DaVinci Resolve, or Final Cut Pro, with motion design skills in After Effects or an equivalent tool. You know how to hook viewers in the first three seconds—and give them a reason to keep watching. You can turn a long recording into a concise, compelling story. You understand how music, silence, sound effects, and pacing shape emotion. You're comfortable using AI tools such as Runway, Kling, Sora, and ElevenLabs as part of your creative workflow. You work independently, meet deadlines, and respond well to direct feedback. You balance speed with quality and care about the details that make work feel polished. Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus."
Why join Base360.ai?: bullet points: "Help shape the video identity of a growing company from an early stage. Work directly with the founder on product launches, storytelling, and building in public. Take creative ownership and see your work published across our brand and marketing channels. Grow into broader creative leadership, with the opportunity to help build a video team. Competitive salary and performance-based incentives. Remote working in an ambitious, entrepreneurial team."
Our expectations: "We value ownership, direct communication, high standards, and continuous improvement. You'll thrive here if you enjoy taking initiative, experimenting, and pushing your craft."
You Should NOT Join Base360.ai If: list of negatives.
We need to map to sections: About the role (maybe combine About The Role and About Us? Actually About the role heading should contain the About The Role paragraph). Responsibilities: What You'll Do. Requirements: maybe Who You Are (core requirements). Qualifications: maybe Experience with SaaS product videos... plus proficiency? But we already used Who You Are for requirements. Could treat Qualifications as "Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus." But that's a plus, not required. Could also include proficiency in software as qualifications. However we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one? But instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including who you are and qualifications), Benefits, Pay, Schedule. Skills maybe not needed if covered in Requirements. But we need to follow headings list; we can omit sections lacking real specific content. So we can omit Skills if we don't have a distinct list beyond what's in Requirements. But we have a list of proficiencies; could be Skills. However we could put them under Requirements as part of who you are. That may be okay.
Benefits: from Why join Base360.ai? includes items: shape video identity, work directly with founder, creative ownership, grow into broader creative leadership, competitive salary and performance-based incentives, remote working. But we already have Pay and Schedule separate; we might move salary and remote to Pay and Schedule, leaving other benefits.
Thus Benefits section: Help shape the video identity..., Work directly with the founder..., Take creative ownership..., Grow into broader creative leadership..., Opportunity to help build a video team.
Pay: Competitive salary and performance-based incentives.
Schedule: Remote working in an ambitious, entrepreneurial team.
We also have Our expectations and You Should NOT Join... Could be omitted? They are substantive but not matching headings. Could we include them as a section like "Expectations" but not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create other headings. We could incorporate that prose into existing sections, maybe under About the role or Benefits? But they are distinct. However we must preserve ALL substantive information. If we cannot add a heading for them, we could embed them as paragraphs without heading, which is allowed? The instruction didn't forbid extra paragraphs. It said use
for section headings (e.g ...). It didn't say you cannot have other headings, but to follow that pattern. Safer to include them as
without heading, maybe after the sections. That would preserve info. Thus final HTML: start with a
for About Us. Then
About the role
...
. ThenResponsibilities
- ... each duty
Requirements
... combine Who You Are and maybe qualifications? We'll put the whole Who You Are paragraph(s) as
(maybe multiple sentences). Could also split into
- but it's not a list; it's prose. We'll keep as
- ... each benefit except salary and remote
. Then
Benefits
Pay
Competitive salary and performance-based incentives.
. ThenSchedule
Remote working in an ambitious, entrepreneurial team.
. Then maybe addfor expectations and negative statements as prose. Check for any duplicated lines: none. Make sure not to include any boilerplate like cookie/navigation etc. Not present. Now craft HTML. Let's list duties: - Edit product launches and brand films that combine storytelling, product demonstrations, and strong visual direction. - Create founder-led content from interviews, talking-head footage, and behind-the-scenes moments. - Produce short-form videos for Instagram Reels, TikTok, YouTube Shorts, and LinkedIn, with strong hooks and purposeful pacing. - Build paid ad creative with variations in openings, messaging, and calls to action. - Bring the product to life through screen recordings, motion graphics, kinetic typography, and clear visual explanations. - Own post-production including footage selection, editing, colour grading, sound design, music, captions, and final exports. - Use AI creative tools to generate supporting visuals, voiceovers, and other assets where they improve the result or speed up production. - Maintain a consistent visual identity across formats and channels. - Improve content through performance insights, using retention, watch time, and conversion data to inform future edits. Now Who You Are content: We'll make a paragraph with sentences. "You have a strong portfolio that demonstrates storytelling, editing craft, and visual taste. You're proficient in Premiere Pro, DaVinci Resolve, or Final Cut Pro, with motion design skills in After Effects or an equivalent tool. You know how to hook viewers in the first three seconds—and give them a reason to keep watching. You can turn a long recording into a concise, compelling story. You understand how music, silence, sound effects, and pacing shape emotion. You're comfortable using AI tools such as Runway, Kling, Sora, and ElevenLabs as part of your creative workflow. You work independently, meet deadlines, and respond well to direct feedback. You balance speed with quality and care about the details that make work feel polished. Experience with SaaS product videos, founder content, documentary storytelling, or paid social ads is a plus." Now Benefits list (excluding salary and remote): - Help shape the video identity of a growing company from an early stage. - Work directly with the founder on product launches, storytelling, and building in public. - Take creative ownership and see your work published across our brand and marketing channels. - Grow into broader creative leadership, with the opportunity to help build a video team. Now Pay paragraph: Competitive salary and performance-based incentives. Schedule paragraph: Remote working in an ambitious, entrepreneurial team. Now expectations paragraph: "We value ownership, direct communication, high standards, and continuous improvement. You'll thrive here if you enjoy taking initiative, experimenting, and pushing your craft." Now negative paragraph: "You should NOT join Base360.ai if you prefer detailed instructions for every task over taking creative ownership; you're looking for a predictable, slow-paced role with little change; you struggle with direct feedback, revisions, or testing new approaches; you care more about making videos look good than whether they tell a story and deliver results; you avoid learning new tools or adapting your creative process; you bring ego or office politics instead of collaboration and accountability; you aren't motivated to