Engineering Software engineer
Your software engineer.
Give an engineer a codebase to get to know and a clear area of ownership. Work together on bug fixes, feature changes, technical investigations, and the maintenance that keeps coming back.
See how a hire works
The context.
A focused change.
A clear explanation.
A place on your team
Define their role.
Make it your own.
The repository, development instructions, project tooling, and issue or feature context you make available to the hire.
A role brief for your software engineerWork with our engineering team on this repository. Read the project conventions, investigate assigned issues, prepare focused changes, and run the available checks. Explain the changes and bring design questions back to us before widening the scope.
An ongoing engineering role, with assigned work and recurring maintenance responsibilities.
Ongoing responsibilities
A few things they can look after.
Get to know the codebase
Read the project files, relevant issues, and existing changes. Give them responsibility for a component or a stream of maintenance, with the team's conventions in the shared context.
Work through changes
Ask for a bug investigation, an implementation, or a refactor within a defined scope. In an enabled command environment, they can edit files and run the checks the project provides.
Keep the handoff clear
Review the proposed changes and recorded steps. Ask for revisions, further checks, or a technical explanation, and keep unresolved questions with the ongoing work.
A change you can follow through.
The issue, a focused patch, and the checks belong together. Your engineer keeps the reasoning with the proposed work.
Keep the filter
when changing views.
Switching from the list to the board clears the selected filter.
Investigation notes attachedfunction changeView(nextView) {− resetFilters();+ keepCurrentFilters(); setView(nextView);
}The tools for their role
A connection.
A clear boundary.
Connect and authorize your own accounts, then choose what this hire may read or change. Provider setup and account permissions determine the available access.
Explore tools and permissions- GitHub
- Connect the required repositories with the appropriate credential permissions. The integration reads files, issues, pull requests, and CI runs, with comments or issue writes available when granted.
- Development environment
- Enable the hire's command environment and provide the repository and project dependencies. Code changes use the working directory and Git; available checks depend on the project setup.
- Linear
- Optional issue context can be limited to the relevant teams. Reading, commenting, and changing issues follow the hire's granted access.
The handoff
Useful work.
A person in the loop.
Investigations, proposed code changes, check results, technical notes, and a record of the work behind them.
Your team owns architecture, review, merging, and release decisions. Set the engineer's repository and command access to match their remit, and review changes before promoting them.
Who would you
hire first?
Sign in to RosterMake a little room on your team.
Good work
has a name.
Start with the role your team needs.
See what a little more team can do.