We're hiring · Engineering

Build the platform that turns a brief into a studio

Studioverse turns a single brief into a studio's worth of on-brand video, and the engineering team owns every part of that path: the ordering surfaces, the production pipeline, the creator tooling, and the APIs underneath them. This is a fully remote, delivery-focused role with real ownership of what you build.

What you will do

  • Build and ship the product surfaces our creators and clients work in every day
  • Own features end to end, from the schema through the API to the screen
  • Review each other's code and keep the codebase something the next person can read
  • Work in a fully remote, delivery-focused team spread across time zones

What we are looking for

  • Projects you actually shipped, with the tradeoffs you made to ship them
  • Depth in at least one stack, and the appetite to work outside it
  • Tests, reviews, and CI treated as part of the work rather than overhead
  • Someone who wants ownership of a surface, not a ticket queue

About Studioverse

Studioverse is an AI-powered video production platform for agencies and brands. We pair a global network of creators with automated tooling to ship UGC, ads, and short-form content at a volume and speed a traditional agency can't match. The engineering team is remote and international by design: you can do this job from anywhere with a reliable connection and a stake in the outcome.

Seven short stages plus a final review, about 15 minutes, and we reply within 7 days.

Join Studioverse Engineering

Eight stages, all on this page. Answer them in any order, and finish in one session.

Fields marked with a star are required. Everything else is optional, leave it blank if it does not apply.

Stage 1

Basic information

Used only for scheduling.

PDF, DOC or DOCX, up to 10 MB.

Stage 2

Technical expertise

Languages and frameworks *

Select everything you have shipped production code in.

Experience areas *
Tools and infrastructure *

Stage 3

Project experience

Include the team size and the stack it was built on.

The one project you would want us to open first.

Development practices *

Select the ones you practise as a matter of course.

Stage 4

Screening questions

Seven short answers, one open at a time. 0 of 7 answered.

One problem, and what made the fix the right one.

Stage 5

Code samples

Three to five links *

Open-source projects, GitHub repositories, or internal projects you can share. Links only. The first three are required; the last two are there if you want them.

Stage 6

Availability

Start date *
Preferred work model *

Stage 7

Compensation

The figure below which the role would not work for you.

Stage 8

Review and submit

Contact

Not answered

Edit

GitHub

Not answered

Edit

Location and time zone

Not answered

Edit

Focus and experience

Not answered

Edit

Technical expertise

Not answered

Edit

Project experience

Not answered

Edit

Largest team project

Not answered

Edit

Code samples

Not answered

Edit

Availability

Not answered

Edit

Compensation

Not answered

Edit

Uploaded files

Not answered

Edit

Screening answers

By submitting this application, you confirm that the information provided is accurate and agree that Studioverse may contact you regarding this position and other relevant opportunities.

You can finish in one session, nothing is saved as a draft.

Protected by reCAPTCHA. Google's Privacy Policy and Terms apply.