Visualfiles Developer - Fully Remote

Required Skills

• Visualfiles
• Developer
• Remote
• Legal
• SQL

Job Summary

VisualFiles Developer

Fully Remote | £60,000-£70,000

Standard 8 is working with a well-established legal firm with a wide-ranging practice. They’re serious about their systems because they’re serious about how the firm actually runs. They want a seasoned VisualFiles Developer who knows the platform properly and doesn’t need hand-holding.

This is fully remote, properly supported, and refreshingly light on theatre. You’re trusted to do the job, not monitored while you do it.

The role

You’ll be shaping and maintaining VisualFiles across multiple legal workstreams. That means building workflows that reflect real legal processes, not theoretical ones, and making sure the system helps people get work done instead of slowing them down.

What you’ll be doing

You’ll own it. Not just coding. Not just support. The full thing.

You’ll take requirements that are sometimes half-formed, work out what’s actually needed, and build something that holds up in production.

Day to day looks like:

• Building and improving Visualfiles workflows and scripts that legal teams rely on
• Getting stuck into integrations APIs, data flows, whatever’s needed to make systems talk
• Working closely with a Product Owner who expects input, not silence
• Making calls on design and approach, not waiting for permission on every detail
• Fixing problems properly, not layering workarounds on top of workarounds

The tech

• Visualfiles
• Azure
• SQL
• Power BI
• .NET (around the edges)

There’s some .NET, around the edges but this isn’t about ticking tech boxes. It’s about building solid, working systems.

What matters

You know Visualfiles. You’ve delivered real solutions, not just tweaks and fixes. You understand how these systems behave under pressure - and how quickly they fall apart when they’re badly designed.

You’re comfortable:

• Owning delivery end to end
• Working things out without a step‑by‑step brief
• Talking to stakeholders who don’t care about the tech, just the outcome
• Making sensible trade‑offs between “perfect” and “done”