- Shape seasonal spaces, hub details, and themed builds that fit Astroworld.
- Work inside the existing visual language instead of forcing a personal style.
- Deliver production-ready spawn and feature builds the team can deploy.
- Collaborate on feedback loops with leads before pushing builds live.
ASTROWORLDMC|Builder Applications
Builders shape polished seasonal spaces, hub details, and themed builds that feel intentional.
- Strong world composition and detail control across scales.
- Can work inside an existing visual language without breaking it.
- Understands what production-ready spawn delivery actually looks like.
- A portfolio with screenshots or videos of relevant builds.
- Notes on what you contributed when work was collaborative.
- Examples that show range: terrain, structures, interiors, or utility spaces.
- Gather your best build samples before you open the application.
- Read the tips page for how to present proof of work cleanly.
- Use the main Astroworld application link when your portfolio is organized.
What the Builder application asks
After the seven fields every applicant fills in, choosing Builder opens 3 more questions, 2 of them required.
Why do you want this role?
Every role starts here, and the form asks you to be specific about what makes you a good fit. 600 characters is roughly a hundred words, so lead with the reason that is actually yours and one example that backs it up.
Portfolio or build examples
Links, with room for several: screenshots, videos or a Planet Minecraft page. The form says these get verified, and the listing wants things you actually built, so a downloaded map does not count.
What building tools do you use?
Optional. WorldEdit, VoxelSniper and Axiom are the examples on the form. WorldEdit helps but is not required, so a Builder who places every block by hand can apply too.
What Astroworld expects from a Builder
Spawn, events and hub areas
Those are the three places the Builder listing names, and it adds that the team is not looking for generic builds. One build that clearly had a purpose says more than a folder of the same starter house in five colors.
Your own work, and only yours
Screenshots have to show things you built yourself. Passing off a downloaded map or someone else's build is lying about your portfolio, one of the six reasons an application is denied on the spot. When a build was a group project, say which part was yours.
Fitting the Astroworld look
The listing asks for someone who can match an existing style instead of only doing their own thing, and for builds that fit the Astroworld look. If every build in your portfolio shares one style, add one where you worked inside somebody else's.
Tools are optional
WorldEdit helps but is not required, and the tools question can stay empty. If you fill it in, name what you actually use and let the screenshots carry the rest.
Other staff roles on Astroworld
Each role has its own form questions and its own guide, so compare them before you pick one.
Use these internal guides before you jump back to the official application.
Common questions about the Builder role
Do I need WorldEdit to apply as a Builder?
No. The listing says WorldEdit helps but is not required, and the question about building tools is optional. The form gives WorldEdit, VoxelSniper and Axiom as examples.
What should a Builder portfolio contain?
Links to screenshots, videos or a Planet Minecraft page with builds you made yourself. Reviewers verify those links, and passing off a downloaded map or someone else's build as your own is lying about your portfolio, which ends an application straight away.
What kind of builds is Astroworld looking for?
Builds for spawn, events and hub areas that fit the Astroworld look. The listing says generic builds are not what the team wants and asks for someone who can match an existing style.
Read here. Apply on Astroworld.
This guide explains each role and what we look for. Apply via astroworldmc.com/apply.