Upwork has more Divi developers than any other single place, along with escrow and dispute handling that direct hiring doesn't give you. It also has a proposal system that rewards volume over fit. Here's how to hire well despite that.
TL;DR: Rates run $15–30 junior, $30–60 mid, $60–100+ senior. Put one project-specific question in your job post — it eliminates most applicants in ten seconds each. Ignore star ratings; run a small paid test. Fund by milestone, never up front. And for jobs under about $400, the screening time costs more than you'll save.
1. Write a Job Post That Filters
Applicant quality is downstream of post quality. Include:
- Specific deliverables. Not "build a website." Instead: "5-page Divi 5 site, custom Theme Builder header and footer, blog archive template, contact form with conditional fields."
- Design references. Two or three live URLs. This communicates more than three paragraphs of adjectives.
- Budget range. Omitting it doesn't get you cheaper bids; it gets you bids that ignore your budget.
- Timeline, including your content deadlines. Content delay is the most common cause of overrun, and naming the dates makes it a shared problem rather than a surprise.
- Existing setup. Divi 4 or Divi 5, which host, which plugins, whether a design exists.
Then add one thing most people leave out, covered in the opinion section below.
2. Know the Rates Before You Read Proposals
| Level | Rate | Suited to |
|---|---|---|
| Junior | $15–30/hr | Content updates, small edits, single-page tweaks |
| Mid-level | $30–60/hr | Full builds, redesigns, Theme Builder templates |
| Senior | $60–100+/hr | Divi 4 to Divi 5 migrations, custom code, performance work |
Rates track geography heavily. A $35/hour builder in Warsaw and an $85/hour builder in Chicago can produce the same site.
The comparison that matters isn't the rate. A $25/hour developer needing 40 hours costs $1,000. A $70/hour developer needing 12 hours costs $840 — and the second one leaves you a preset system rather than 60 modules with inline styles. What a Divi freelancer actually costs has the full breakdown, including the expenses that never appear in a quote.
3. Read Portfolios Properly
Screenshots prove someone owns Photoshop. Ask for live URLs and then actually check them:
- Open each on your phone. Not a resized desktop window — a phone. Roughly a third of Divi portfolios fall apart at 390px.
- Look for variety. Six sites in the same template with different logos tells you they can swap content, not build.
- Confirm it's Divi. View source and search for
et_pb_. It's a ten-second check and it occasionally surprises you. - Run one page through PageSpeed Insights. You're not looking for 100. You're looking for whether performance was ever a consideration.
Then ask the question that separates builders from bluffers: "Which Divi features did you use on this project, specifically?" A real Divi developer names things — Design Variables for the brand palette, option group presets for the card shadows, Theme Builder conditions for the category archives, Loop Builder for the portfolio filter. Someone padding their profile says "all the standard modules."
4. Red Flags
- No live sites. Anyone can write "Divi expert" in a headline.
- A rate under $15/hour for a build. Somebody is subcontracting, or you're their training project.
- "Unlimited revisions." This means the work hasn't been scoped. It ends badly for whichever of you has less patience.
- No questions about your project. Good developers ask two or three things before quoting. Silence means they haven't read the brief.
- A proposal that never mentions your project. The clearest signal available, and it's free.
- Vague on Divi 5. In 2026, "I mostly work in Divi 4" is fine and honest. "Divi 5 is basically the same thing" is not — it isn't.
5. Interview Questions That Actually Test Divi Knowledge
Generic questions get generic answers. These five have right answers, which makes them useful:
"How would you make every image in a blog grid the same shape when the client uploads whatever they like?" Looking for: Aspect Ratio with Object Fit. A Divi 4 answer of custom CSS is acceptable. "I'd ask them to crop the images" is not.
"What's the difference between an element preset and an option group preset?" Looking for: element presets style a whole module, option group presets style one group — just the border, just the shadow — so several can combine on one element.
"How do you handle brand colours across a 20-page site?" Looking for: Design Variables in the Variable Manager. If the answer is "I paste the hex code," you've found a Divi 4 workflow, and the reason that's now a problem.
"How do you move a CTA above the image on mobile without duplicating the module?" Looking for: Display Order per breakpoint. Duplicating modules and hiding one is the Divi 4 workaround, and it doubles the maintenance.
"What do you check before upgrading a client site from Divi 4 to Divi 5?" Looking for: third-party Divi module plugins and custom child theme code. This is the single best question on the list, because it's the one failure mode that actually bites and only people who've been burned mention it.
Their answers also tell you whether they'll build you a site that's maintainable or one that's merely finished.
6. Run a Small Paid Test First
Before a full build, commission one contained piece of work: a single landing page, a Theme Builder header, or converting one design into a live page.
You're buying information about four things a proposal can't tell you — code quality, communication speed, whether they meet a stated date, and whether they ask good questions mid-task. At $100–300 it's the cheapest insurance in this process.
Pay for it. An unpaid test filters for desperation, not skill.
7. Fund by Milestone
Never fund the whole project up front. A five-milestone structure that works:
- Design direction approved — mockup or first section signed off
- Homepage built — including mobile
- Remaining pages
- Mobile testing and speed pass
- Launch and handover — including documentation of the preset and variable system
Each milestone needs a written deliverable and a release trigger. And insist on that last item: a site handed over without notes on how the presets and variables are structured costs more to change later than to rebuild.
My Take: Upwork Ratings Are Nearly Worthless — One Question Does the Work Instead
Here's my one strong opinion: stop filtering by star rating, and put a single project-specific question in your job post. It will screen your applicant list faster and more accurately than every other signal on the platform combined.
The ratings problem is structural, not anecdotal. Ratings are mutual, so both sides have an incentive not to leave a bad one. Disputes get settled privately. The result is that essentially everyone working regularly sits between 4.8 and 5.0. A 4.9 tells you someone has completed jobs without a catastrophe, which is a floor, not a recommendation. You cannot rank people on a scale where everyone scores an A.
Meanwhile, proposals cost Connects, so experienced freelancers spray templated applications wide and cheap. You'll get thirty proposals, of which twenty-five were written before your post existed.
So do this. At the bottom of the job post, add:
"In your proposal, tell me in one sentence which Divi feature you'd use to keep the blog grid images the same shape."
Then delete every proposal that doesn't answer it. In my experience that's roughly four out of five, and it takes ten seconds per application. What's left is people who read your post — which is already better than filtering by rating, because reading the brief correlates with everything else you want.
I've built over 100 Divi sites and I've also been on the receiving end of this hiring process. The clients whose posts contained a real question were, without exception, the better projects. It's not that the question is magic. It's that writing one requires knowing what you want, and people who know what they want are easier to build for.
The honest corollary: sometimes Upwork is the wrong venue. For a job under about $400, the hours you'll spend writing the post, screening thirty proposals and running a test cost more than you're saving — take a referral instead. And for a mission-critical Divi 4 to Divi 5 migration on a site that earns money, the senior people who do that work well are mostly not bidding on marketplaces. Post it if you like, but ask around at the same time.
Straight Answers
Rates on Upwork? $15–30 junior, $30–60 mid, $60–100+ senior.
How do I spot a real Divi developer? Ask which Divi 5 features they used and listen for specifics.
Are ratings useful? Barely. Everyone active sits at 4.8 to 5.0.
Hourly or fixed? Fixed with milestones for defined builds, hourly for debugging and migrations.
What goes in the job post? Deliverables, references, budget, timeline, and one project-specific question.
Biggest red flag? A proposal that never mentions your project.
The Last Word
Hiring on Upwork isn't hard, it's just noisy. The platform optimises for proposal volume, so your job is to add friction in one useful place.
Write a specific post, ask one question a template can't answer, check the portfolio on your phone, pay for a small test, and fund by milestone. Five steps, and they eliminate nearly every way this goes wrong.
Whoever you hire, buy the Divi licence yourself and register it to your own account — around $89/year or $249 lifetime for unlimited sites. If you part ways, you keep the updates. If you'd rather skip the screening and talk to someone who'll answer those five questions on the spot, that's what the contact form is for.
Related Reading
- How Much Does a Divi Freelancer Cost? — real numbers, plus what quotes leave out
- Converting AI Designs to Divi 5 Layouts — what to brief if you're hiring for this
- Divi 5 Speed Optimization Tips — what "performance included" should mean in a proposal