Join a team that diagnoses before prescribing, documents decisions, builds practical systems and measures whether the work improves the client's business.
No roles currently open. Register interest below to be considered when hiring begins.
Most technical roles let you stop at 'built to spec'. Here the spec itself is up for challenge, and you're expected to connect what you build to what it changes commercially.
Every technical decision here is expected to trace back to a business outcome. “It works” isn't done. “It moved the number it was built to move” is.
The same engagement can span economic analysis, software delivery and ongoing operation. You'll see how audit findings become systems, not just tickets.
Work starts by finding the constraint, not by selling the capability. That discipline applies internally too, including to how roles themselves are scoped.
These aren't poster values. They're the same principles published to clients across this site, which means candidates and clients can hold the team to the identical standard.
Recommendations are made plainly and defended with reasoning: no theatre, no urgency manufactured to close a decision.
Claims are labelled as facts, estimates or judgement calls. If something can't be evidenced, it's said out loud.
Decisions and their trade-offs are documented as they're made, for clients and for each other.
Systems (AI included) ship with human review, clear limits and honest labelling of what's generated versus verified.
Work has a named owner from diagnosis to delivery. Handing a problem sideways isn't finishing it.
The published insights and open-source work exist because the team studies its own delivery, not just its clients'.
An honest read in both directions saves everyone's time.
Only confirmed policies get published here, and because arrangements genuinely vary by role, they're published role-by-role rather than as blanket promises.
Every advertised role states its own working arrangement, location, employment type, tooling, performance expectations and degree of client interaction directly on the listing, so what you read is what that role actually involves, not a generic culture page.
Anything a listing doesn’t answer is a fair question at any stage of the process, and it will be answered directly. If something can’t be confirmed, you’ll be told that rather than given a vague assurance.
Roles open as client demand supports them, across the same families the services are organised around.
Constraint diagnosis, unit economics and the analysis behind audit and advisory work.
Technology strategy, roadmapping and the decision work that precedes any build.
Custom systems, integrations and the web platforms client businesses run on.
Applied AI systems, data pipelines and the evaluation work that keeps them honest.
Web design and the interface work that makes systems usable by real staff and customers.
The marketing and growth systems work behind managed-service engagements.
Project ownership, communication and the continuity that keeps engagements accountable.
There are no advertised openings right now, and stale listings are never left up. When a role opens it will appear here with its title, level, location, work arrangement, employment type, salary range where policy allows, and application deadline.
Register your interest insteadRather than publish a generic pipeline that may not match the next role, every listing carries its own process.
Each advertised role publishes its hiring process alongside the listing: the stages involved, what each stage assesses, the expected timeline, how and when you’ll hear back, and whether any practical task is paid. You’ll know the full path before you apply: no surprise stages added mid-process.
Yes. Register your interest through the talent community below. It isn't a formal application and doesn't guarantee contact, but it's how the team knows who's out there when a role opens.
New roles are published on this page, with their level, location, work arrangement, employment type and application deadline. Listings are removed the moment a role closes. Nothing here is left up stale.
Web Lifter is a Brisbane-based studio. Location and work arrangement aren't blanket policies. Each advertised role states its own arrangement on the listing.
It depends on the role. Each listing states exactly what to submit and whether work samples, a portfolio or references are part of the assessment.
Each role's listing states how AI-assisted applications are treated for that role, so you're never guessing at an unwritten rule. Whatever you submit, you should be able to stand behind it in conversation.
Raise it through the contact page at any stage. Process steps for a role can be adapted, and asking has no bearing on how your application is assessed.
Anything you share is handled under Web Lifter's privacy policy, published on this site under Policies. Talent-community details are kept for future hiring contact only.
If your capability fits the role families above, you can register interest ahead of any opening.
There’s no standing application form yet. Use the contact form, mention you’re registering careers interest, and include what you do plus a link to your work. To be clear about what this is: registering interest is not an application and doesn’t guarantee contact. It simply means you’re known to the team when a genuine role opens.