What this route is

A normal junior role, shaped around useful AI and web delivery.

Spring employs me directly, agrees pay and hours, and gives the role a clear practical focus. There is no training-provider setup, no government scheme to wait for and no need to frame the first step as freelance work.

This is the strongest route if Spring already feels the fit is clear and wants to start building internal technical capability without adding apprenticeship structure on day one.

What the role covers

The role should sit where production work meets technical delivery.

The value is not just having another pair of hands. It is giving Spring someone who can move between design, websites, small tools, documentation, QA and AI-assisted build work.

• Web delivery Build support, content implementation, QA, fixes, documentation and handover notes.
• AI production Prompted drafting, content systems, research support and AI-assisted implementation with human review.
• Internal tools Small utilities, workflows or automations that reduce repeated manual work.
• Client support Useful technical production where Spring needs speed without lowering standards.

How it starts

Agree the job shape first, then keep the first weeks concrete.

The setup should be a written employment agreement with agreed pay, hours, notice and reporting line. The work should start with a short list of useful outputs rather than a vague promise to “help with AI”.

A sensible first version could be part-time, reviewed after a fixed period, and expanded only if Spring can see the value clearly.

First-month focus

The first month should prove usefulness, not try to define everything forever.

• Audit friction Identify repeated production tasks, content bottlenecks and small technical jobs that waste time.
• Ship visible work Make useful site changes, QA improvements or client-facing support tasks that Spring can judge quickly.
• Build one internal helper Create a small repeatable tool or workflow improvement rather than a theoretical AI demo.
• Review scope Decide which work is worth expanding and which should stay outside the role.

Boundaries

The simple route still needs a clean definition.

Direct employment should not become an undefined catch-all. The role needs clear ownership, expectations and review points so it remains useful for Spring and sustainable for me.

• Not vague AI enthusiasm Work should attach to real production needs, client delivery or internal systems.
• Not unsupported responsibility Client-critical work still needs review, QA and Spring's judgement.
• Not locked forever Hours and scope can be reviewed once the useful work is clearer.

Questions to agree

The key decisions are practical, not theoretical.

• Hours How many days a week would create value without creating management drag?
• Pay What wage makes sense for a junior AI/web role with room to grow?
• Manager Who sets priorities and reviews work?
• First outputs Which three jobs would prove the role is useful fastest?
• Review point When do we decide whether to expand, narrow or change route?