Understand the codebase
Read the relevant code, project instructions and existing tests. Identify the affected components and clarify the intended behaviour before implementing a change.
Hand-over: a concise implementation brief and open questions.
03 / Developer
The next feature.
In good hands.
A feature waiting to be built. A bug that needs an explanation. An integration that keeps being postponed. Give that work a defined place in your team.
Discuss this roleA place in your team / Role 03
Your codebase.
Its next contributor.
For product teams, software businesses and companies with internal tools to maintain. A developer role configured around your repository, coding conventions and review process.
The responsibilities
Give the work
a clear owner.
Choose a first responsibility, agree the expected output and define the way it will be reviewed.
Build a feature
Implement the agreed behaviour in your application, from interface logic to server endpoints and data handling where the scope requires it.
Hand-over: a focused change with an explanation of the resulting behaviour.
Investigate a bug
Work from a reproduction, error report or failing test. Trace the cause, prepare a correction and check the affected behaviour.
Hand-over: the cause, the fix and evidence that the reported path was checked.
Connect your systems
Develop scoped API integrations, data exchanges and internal automations. Account for authentication, failures and retries in the agreed workflow.
Hand-over: an integration for review, configuration notes and relevant failure-path checks.
Strengthen reliability
Add tests where they protect meaningful behaviour. Investigate failing checks and make validation part of the hand-over.
Hand-over: relevant tests, results and any verification gaps.
Maintain and explain
Make bounded maintenance changes, update project documentation and prepare work for the next reviewer. Preserve the conventions that make your codebase understandable.
Hand-over: a clear change description, setup notes and any migration or release steps.
Example briefs / A starting point
What would you
hand over first?
These are proposed assignments to shape an introduction. Your pilot is defined around your own project, files and review process.
Example 01 / A product feature
A product feature
“Add this customer-requested feature to the existing product. Use our conventions and bring back a change we can review.”
Start with
A repository, the intended user behaviour, acceptance criteria and a review owner.
Receive
- Implementation in the scoped working branch
- Relevant tests and verification results
- A change description and rollout notes
Your technical lead reviews the code and authorises merge and release.
Example 02 / A reproducible bug
A reproducible bug
“Find why this workflow fails, fix the cause and show us how the correction was checked.”
Start with
Reproduction steps, expected behaviour, relevant logs and the affected environment.
Receive
- A documented cause and focused correction
- A regression check where appropriate
- Remaining uncertainty made explicit
Your reviewer confirms the behaviour and approves the change.
Example 03 / A system integration
A system integration
“Connect these two services so this repeated hand-over can happen through a controlled workflow.”
Start with
The systems, API documentation, sample data, access boundaries and failure expectations.
Receive
- A scoped integration and configuration
- Checks for success, failure and retries
- Operating notes and a release plan
Your team approves data access, credentials and any production activation.
The working rhythm
A hand-over your team can follow.
01
Read the context
Establish the expected behaviour, relevant code, project conventions and review criteria.
02
Implement and check
Prepare a focused change and run the checks appropriate to the affected behaviour.
03
Bring it to review
Explain what changed, why, how it was tested and what your team needs to decide next.
Your environment
The tools you use.
The standards you keep.
Start with your existing stack and a representative task. Language support, framework versions, repository access and external services are assessed during scoping. The pilot establishes the workflow that the ongoing role will use.
Your repositoryYour issue trackerYour language & frameworkYour test suiteYour release workflow
How the role is configured A clear working relationship
Prepared with care.
Released with your approval.
ResponsibilityAI colleagueYour team
ImplementationPrepare the scoped code changeConfirm requirements and review
Tests and diagnosticsRun agreed checks and report resultsAssess readiness and remaining risks
Data and system accessUse the permissions grantedDefine and authorise access
Merge and deploymentPrepare the change and release stepsAuthorise merge and public release
Other roles / The same considered approach
A different responsibility?
Role 01
The architecture colleague.
A colleague for the drawings, quantities and coordination questions that keep your projects moving.
- Drawing intelligence
- Working quantities
- Project coordination
Role 02
The web designer. And integrator.
A colleague who develops the visual direction, designs the pages and brings the approved experience to life on the web.
- Art direction & UI
- Responsive integration
- Website delivery
Role 04
The marketing colleague.
A colleague who learns your audience, voice and priorities, then prepares the content, campaigns and reporting that keep your marketing moving.
- Brand & content
- Campaign preparation
- Performance reporting
Private access / Developer
One less item waiting.
One more colleague working.
Tell us about the work, your current environment and the person who would review the result. The first assignment starts there.
Request an introduction