Full Time
$1500/month
60
Aug 28, 2026
We're redesigning the visual and front-end layer of our brand ecosystem. There are two distinct tracks below. Apply to one or both — tell us clearly which.
Most applicants should apply to one. We'd rather hire two specialists than one generalist who is adequate at both.
Track A — Graphic Design & 3D Product Visualization
The work
1. Product render library (primary deliverable)
We need a consistent, photorealistic render set covering our full catalog of roughly 18 SKUs — lyophilized powder in glass vials with blue aluminum crimp caps, plus a small number of liquid products.
We already have one render that defines the target quality: a 3/4-angle GLP-TZ vial, studio lighting, transparent background. That image is the standard. Every other SKU needs to match it — same camera angle, same lighting setup, same shadow treatment, same crop ratio.
Consistency matters more than individual image quality here. A catalog grid where every vial sits at a slightly different angle is what makes a brand read as small.
Deliverables per SKU: transparent PNG at high resolution, plus white-background WebP optimized for web. Source files (Blender/C4D/KeyShot scene) delivered at project close.
Critical: all label text must be pixel-accurate to the artwork we supply. Compound name, milligram strength, and disclaimer text are non-negotiable. Our customers are technically literate and a garbled label destroys trust instantly. If you work with AI-assisted generation, we need real artwork composited in post rather than model-generated text.
2. Presentation packaging visualization
We have 2,500 magnetic-closure presentation boxes in inventory: neutral white, square footprint, front-flap magnetic latch producing a visible horizontal seam roughly one-fifth of the box width in height. We need renders of these with our artwork applied, in both standalone and vial-composite arrangements.
3. Web design comps
Figma comps for homepage and a representative product page. This is the spec our developer builds against, so we need real specificity: type scale, spacing system, component states, mobile and desktop breakpoints, motion and interaction direction. Not a static picture of a page.
Aesthetic direction
Think Apple restraint crossed with pharmaceutical clinical credibility. Pure neutral white backgrounds. Generous whitespace. Navy on white — not dark mode. Clean geometric sans typography. Nothing decorative, nothing "supplement industry," no gradients-and-glow wellness styling.
Reference for the level of front-end polish we're targeting:
We have documented brand standards, a locked color palette, and existing logo artwork. You'll receive all of it.
Track B — Front-End / WooCommerce Development
The work
Implement approved Figma comps on our existing WordPress store. Homepage, product pages, catalog grid, and mobile treatment across all of it.
This is an implementation role, not a design role. You'll be building against an approved comp. Success is binary: does the live page match the file. We're not asking you to make aesthetic calls, and we won't ask you to guess what we want.
Mobile quality is weighted heavily. Most of our traffic is mobile and it's where most builds fall apart.
Technical environment — read this before quoting
Being straight about the constraints, because they're real and they've cost us debugging time. We have all of this documented and will share the full runbook with shortlisted candidates.
WordPress + WooCommerce + Astra 4.13 + Elementor Pro on Hostinger, PHP 8.3
No child theme currently exists. Astra runs as the parent theme, so custom PHP lives in the Code Snippets plugin rather than in version-controlled files. Migrating to a proper child theme with a git repo and rsync deploy is a possible additional scope item — a build brief already exists for it.
The host WAF rejects REST request bodies containing literal script or meta tags — 403 or a silent 500. Existing code works around this with wp_enqueue_* and wp_add_inline_script rather than echoing tags. The firewall does plain substring matching, so even tag text inside a PHP comment trips it.
LiteSpeed caches aggressively and does not auto-purge on Code Snippets writes, because that plugin uses its own database table and never fires save_post. Manual purge required after every snippet change.
Elementor page structure lives in _elementor_data, a single JSON blob that is not exposed to REST. The homepage alone is 159 widgets. Current work is done through render filters rather than by writing to that blob.
Two separate snippet plugins are in play — Code Snippets (REST-accessible) and WPCode (not). Some existing CSS is only reachable through wp-admin.
Airlift and LiteSpeed both defer JavaScript until first interaction. A previous client-side product grid rendered empty on load. Rendering happens in PHP for that reason. Don't move it back to the client.
Also running: AIOSEO, AffiliateWP, Solid Security, PixelYourSite, Omnisend, Woo Discount Rules, and OTTO (Search Atlas), which rewrites headings client-side.