Posting record
Open 12+ days
- Vidrush's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Vidrush, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
VidRush is an AI-native video production platform that replaces an entire video team with coordinated AI agents.
Creators turn a simple idea into a fully produced, long-form video—research, script, voiceover, visuals, motion graphics, and rendering—in under an hour. No timelines. No editing headaches. Just intent → finished video.
We’re building a new way to create video that feels more like writing than editing, and we’re already seeing strong traction from serious creators and media teams.
If you’re excited about AI, creator tools, and building category-defining products from first principles, you’ll fit right in.
We're looking for a backend engineer to help build and scale the infrastructure behind Vidrush, a video generation platform. You'll work on a TypeScript/Node.js serverless backend where code quality and thoughtful design are first-class priorities.
What you'll do
- Own and deliver backend features end-to-end, from API design through deployment
- Solve interesting problems across video generation pipelines, AI integrations, and billing systems
- Shape the architecture of services that power our core product workflows
- Contribute to a codebase that prioritizes long-term maintainability
- Collaborate closely with the team on technical decisions, code reviews, and continuous improvement
Requirements
- 2–7 years of professional backend engineering experience
- Strong proficiency in TypeScript and Node.js
- Hands-on experience with AWS in a serverless context
- Solid experience with MongoDB or other document databases
- Experience with Stripe or similar payment/billing platforms
- Familiarity with serverless frameworks (e.g., SST, Serverless Framework)
- Experience writing unit and integration tests with Jest or similar
- Understanding of RESTful API design and middleware patterns
- Comfortable with Git workflows, CI/CD, and code quality tooling
- Experience in building AI-powered applications, especially agentic systems using LLMs in production.
Nice to Have
- Experience with Infrastructure as Code (Pulumi, CDK, Terraform)
- Familiarity with event-driven architectures and messaging patterns
- Background in layered architecture patterns (Clean Architecture, hexagonal, ports & adapters)
- Experience with modern web frameworks like Hono
- Interest in AI/LLM technologies and experience integrating with AI APIs
- Familiarity with agentic AI systems and frameworks like Mastra
What We Value
- Craftsmanship : You care about code quality, testing, and maintainability—not just making it work
- Architectural discipline : You respect layer boundaries and established patterns rather than taking shortcuts
- Pragmatism : You ship working software without over-engineering
- Ownership : You take features end-to-end, from design through production
- AI-accelerated development : You actively use tools like Cursor, Copilot, and LLMs for scaffolding, tests, refactors, and debugging—without outsourcing your judgment
- Curiosity about AI : You're excited about the intersection of backend engineering and AI capabilities
Note: whilst we're a global company working remotely, we prefer to hire from Turkey - as most of our Engineering team is localized there.
Something wrong with this posting?