Guides · Hiring

How to Check a Roblox Dev’s Portfolio

A portfolio is an argument, and in this market many of them are fiction. The good news: real work leaves evidence that is hard to fake, and checking it takes minutes once you know what to ask for. This guide walks the checks in order, from the evidence that proves almost everything to the signals that merely suggest.

BLOXWORK, the most trusted Roblox developer marketplace in the world.

Escrow on every order

Your money stays held until you approve the finished work. Only then does the dev get paid.

How escrow works
Devs verified with real ID

Every dev shows ID to earn the Verified badge. The document stays private. Only the badge is public.

About the badge
One fair fee

10% of the job, never more than $1,000. No buyer fees. Nothing stacked on top.

The fee rule

The strongest evidence: live work

Evidence you can open beats evidence you can only look at. A system running in a live game, a map you can walk, a vehicle you can drive, an interface you can tap: these are nearly impossible to fake, because the game around them is real and the dev’s name is attached to a specific contribution. Ask which part is theirs and test that part hardest. A scripter who built the trading system will talk about its edge cases for ten minutes without notes.

Where live work cannot be shown, ask for the next best thing: a walkthrough in Studio, screen shared or recorded, with the dev driving. Builders open the place and show the organisation. Scripters show the code’s shape and explain a hard problem they solved inside it. Fakers avoid motion and depth; professionals walk toward both, because showing the work properly is the pleasure of having done it.

The explanation test

Ask one question about a choice inside the work: why is this lobby shaped like this, why does this system store data that way, what broke during this build and what fixed it. Real authors answer with specifics, trade offs and small regrets. Borrowed portfolios answer with compliments about the work in general, because the borrower admires the same surface you do and knows nothing beneath it.

This test scales to every trade. Designers explain hierarchy decisions. Animators explain a timing choice. Modelers explain a triangle budget. The vocabulary differs; the depth signature does not. Two minutes of explanation tells you more about authorship than twenty images, and it costs you nothing but the asking, which is why it should be a habit on every hire above pocket money.

Reviews, records and identity

Reviews are evidence only when they are hard to write. On BLOXWORK a review exists solely because an order completed and released, one per order, with a written reason required, feeding a Trust Score that falls as fast as it rises. That structure is the point: a record assembled from finished transactions, attached to an ID verified person, is expensive to fake and ruinous to waste, which is exactly the kind of record worth trusting.

Elsewhere, weigh reviews by their specificity and their cost. Named games, named deliverables and detailed praise carry weight; a wall of five star one liners from accounts created the same week carries none. Cross check one claim independently, a game’s credits, a group’s staff list, before money rides on the rest. Verification is a ladder; climb as many rungs as the job’s size deserves.

The red flags, collected

A portfolio of famous games’ key art and icons, recognisable because they succeeded publicly. Work shown only as stills, never in motion, never in a place you can visit. Prices far below the market band for the claimed skill, paired with urgency about paying today. Reluctance to use escrow, framed as insult or inconvenience. A history that resets: new accounts, new names, old work. Any one flag is a question; any two are an answer.

Hold the opposite list with equal care, because good devs deserve to be recognised as fast as bad ones: live work with a named part, explanations with trade offs in them, reviews with specifics, prices inside the market’s logic, and eagerness for a written scope and escrow. That last one is the tell of tells. Professionals love structures that make their honesty visible; only the other kind finds them insulting.

Make checking a habit, not an event

Keep notes. Every check you run, every explanation that impressed or evaporated, every delivery judged against its scope, written down against the dev’s name. Memory flatters and forgets; notes compound. Six months of notes is a private hiring database worth more than any platform’s search filters, because it records the only data that finally matters, how this person worked with you, on your kind of job, under your kind of deadline.

And check again even on the second order. Records go stale, people’s circumstances change, and the dev who was hungry and brilliant last spring may be overbooked and delegating this autumn. The habit is not suspicion; it is maintenance, the same respect for evidence at order five that protected you at order one, applied without the romance of the new or the comfort of the familiar.

Where BLOXWORK stands today

BLOXWORK is new, so portfolios here are young too. Judge founding devs by the checks in this guide, live work and verifiable history, and know that every review beside their names here could only be written after a real order released.

How hiring works here

1
Agree the scope & pay into escrow

The scope is in writing before you pay. BLOXWORK holds your money. It does not go to the dev yet.

2
The dev builds

Work runs against the agreed scope and delivery time. Revisions in the package are tracked on the order.

3
You approve, money releases

Check the work. Only your approval releases the pay, minus the 10% fee capped at $1,000.

Are you a Roblox developer?

Keep 90% of every job. The fee never takes more than $1,000, even on a $25,000 job where a 20% platform takes $5,000. Your pay sits in escrow before you start and lands in USD when the client approves. Show your ID once, wear the Verified badge, and let clients trust you on sight.

Questions, answered

A dev’s work is under NDA or unreleased. What then?

It happens legitimately. Ask for the next rung down: a Studio walkthrough of their own test place showing the same skills, references from the client if allowed, or a small paid first piece through escrow that proves the trade on your own ground. Real devs understand the problem and offer substitutes; fakers offer pressure.

How much checking is enough for a small job?

Scale the effort to the money and the access. A small art order needs the explanation test and a live example or two. A systems order touching your game’s data needs live work, reviews and the full conversation. Escrow covers the money in all cases; checking covers the calendar, which escrow cannot refund.

Can I ask for a test piece?

A small paid test inside a first scoped order is fair and common; an unpaid spec piece is not, and good devs refuse those on principle. Structure it as the real thing at small size: one asset, one system slice, delivered through escrow and judged exactly as the big job would be.

The portfolio is great but there are no reviews. Worry?

Not by itself, especially on a young marketplace where everyone’s record starts somewhere, and on BLOXWORK every dev is ID verified before the first order. Weight the live work and the explanation test more heavily, start with a scoped first piece, and let the record build from your own order.

What if two devs claim the same work?

Ask each the explanation questions about different parts of it. Teams genuinely share work, and honest collaborators name each other’s parts precisely. Competing solo claims collapse under detail: the real author knows where the bodies are buried in the build, and the borrower knows the screenshots.

Keep going

Ready when you are

Browse the marketplace with escrow on every order, or put your own work in front of the clients arriving here.