Discover the importance of Annaizu Compliance Management in today's business landscape and how a Home Office compliance management platform can help your business streamline its compliance efforts, reduce risks, and stay ahead of regulations.
SOC 3133 groups two genuinely different jobs — database administrators who design, test and maintain data systems, and web content technicians who manage and publish site content — under one sponsorship code. Employers must be able to show which duties actually apply before relying on it for a Skilled Worker sponsorship.
Why the job description has to do real work here
Because this code spans a technical database role and a more editorial content-management role, the Home Office expects the job description on the certificate of sponsorship to match what the person genuinely does day to day, not a generic IT job title. A content technician whose real duties are mostly social media scheduling or basic copy edits sits awkwardly under a code built around database design, testing and content architecture — and a mismatch between the CoS description and the actual role is one of the easier things a caseworker or compliance officer flags on review.
How the two halves of the code actually differ in practice
Treating SOC 3133 as one generic 'IT and web' bucket is where most job descriptions go wrong. On the database side, genuine duties tend to include schema design, query and performance tuning, backup and disaster-recovery planning, access-control administration and security patching of database systems — work that requires understanding how the underlying system behaves under load, not just how to run a report. On the content side, genuine duties look more like information architecture, managing a content management system's structure and templates, coordinating publishing workflows across a team, metadata and taxonomy management, and ensuring published content meets technical standards such as accessibility. A role that doesn't clearly resemble either list — because it's really general marketing support, basic admin, or IT helpdesk work with a website thrown in — is the kind of fit that won't survive a close look at what SOC 3133 is actually meant to cover.
Meeting the skill and salary thresholds
SOC 3133 sits at RQF3, so the applicant needs a role genuinely requiring that level of skill, and pay has to clear both the general salary floor and the specific going rate for this occupation code. Because going rates are set per SOC code and reviewed periodically, it is worth checking current figures directly against the going rates for this occupation rather than assuming last year's number still applies, alongside the wider salary floor rules that apply across all Skilled Worker sponsorship. It's also worth checking the role against neighbouring codes rather than assuming SOC 3133 is the only fit: a database role that is heavily focused on architecture and system design at a higher level of seniority, or a web role that is really front-end or full-stack software development, may sit more accurately under a different, higher-skilled occupation code with its own going rate — using 3133 because it's a familiar code, rather than because it's the right one, is a shortcut that tends to unravel later.
Cross-training and duties that shift between the two sides over time
In smaller IT teams, it's common for one person to be hired primarily as a database administrator or content technician and, over time, pick up work from the other half of the code as the business needs it — a DBA who ends up owning the intranet, or a content technician who takes on basic database maintenance because there's no one else to do it. That kind of drift is generally fine, since both sets of duties sit within the same occupation code, but it's worth revisiting the job description periodically so it still reflects reality, particularly if the balance has shifted enough that the original title no longer describes most of what the person does day to day.
Platform and CMS migrations don't reset the clock
Web content technicians in particular often go through a platform migration — moving from one content management system to another, or consolidating several sites onto one platform — partway through a sponsorship. That's a normal operational event, not a change to the underlying role, and it doesn't need to be treated as though the job has changed. What is worth keeping is a short record of the migration and the technician's part in it, since 'why does the CV or internal records show a different CMS than the one named in the original job description' is an easy, avoidable question to leave unanswered.
Building the evidence file before assigning a CoS
Sponsors are required to keep evidence showing the role is genuine and the worker is doing the job they were sponsored for, under the eligible occupations and codes guidance. For a hybrid code like this one, that means retaining the original job description, any recruitment materials, and org-chart context showing where the role fits — records that are far easier to produce on demand when stored through a system built for secure, retrievable document management rather than scattered across email threads. A short evidence checklist worth building for either side of the code:
- The original, duty-specific job description used at the point of recruitment, not a generic template.
- Records showing which systems, platforms or databases the person actually works on, and how that has changed over time.
- Salary evidence showing pay has kept pace with the current going rate, including at any renewal.
- Where duties have shifted between the database and content sides of the role, a brief note of when and why.
FAQs
Can I sponsor someone doing purely social-media or basic content-editing work under SOC 3133? Only if the substantive duties genuinely meet the RQF3 threshold and match the occupation description — a role that is really just posting updates is unlikely to satisfy scrutiny even if the job title says 'web content technician'.
What happens if the going rate for this code rises after the CoS is assigned? The salary that applied at the point the CoS was issued generally governs that grant, but sponsors should still track rate changes for future assignments and renewals so pay never falls behind current requirements.
Does experience with a specific database platform or CMS matter for eligibility? The Skilled Worker route assesses the occupation and skill level, not named software products, so eligibility doesn't turn on whether someone has used one particular platform over another — though the job description should still describe the actual systems and tools the role involves.
What if the person genuinely splits their time evenly between database administration and content management? That's still consistent with SOC 3133, since both sets of duties sit under the same code — the job description should simply describe both halves of the work accurately rather than emphasising only one.
.svg)