Engineering & Technology - Engineering
Software Engineer
IC / Practitioner
Independently auditedBuilds and operates the software the business runs on. Owns a defined area of the function and the outcomes it produces.
Audited package
Built, independently audited role package. Everything on this page is written for this seat.
Your Stack (Swappable)
This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.
- Version Control & Code Review
- Languages and runtimes
- QA & Testing
- CI and delivery
- Feature control
- Observability & Monitoring
- Docs & Knowledge
Deliverables
- Design documents
- Review checklists
- Technical standards
- Delivery and sequencing plans
Responsibilities
- Translate a product or operational requirement into acceptance criteria, non-goals, and a bounded implementation sequence.
- Read and modify an existing codebase while following its architecture, conventions, ownership model, and compatibility promises.
- Implement feature logic and local refactors with explicit handling for errors, concurrency, retries, and boundary conditions.
- Write unit, integration, and contract tests that prove the change without overfitting to implementation detail.
- Participate in code review as author and reviewer, explaining the invariant, risk, and evidence.
- Ship through the approved delivery path using staged exposure when risk warrants it.
- Add logs, metrics, traces, or business telemetry needed to verify production behavior.
- Respond to defects and on-call issues in the code this seat owns and leave a regression proof.
The essence of this seat
The Software Engineer is the generalist product engineer who designs, implements, tests, ships, and operates a feature across an existing codebase, owning code quality and the production behavior of what they ship.
Signature move
Reconstruct the user-visible outcome. Translate the request into acceptance criteria, non-goals, and an observable definition of done before editing code
What good looks like
frames the outcome, reads the system, and scopes narrowly
Decision rights
- - - The implementation plan and delivery of a bounded feature inside an established architecture
Working vocabulary
What this role does
The Software Engineer is the generalist product engineer who designs, implements, tests, ships, and operates a feature across an existing codebase, owning code quality and the production behavior of what they ship. Its signature evidence includes the feature design note, the pull request evidence checklist, and the test matrix. The earliest proof that the seat is working is visible in these leading signals: acceptance criteria and non-goals are explicit before implementation; changes remain small enough for focused review; tests cover relevant failure paths and seams. It remains an individual contributor reporting through Engineering Manager, with technical review from a Senior Software Engineer. This package covers only the canonical Software Engineer roster title. It is the generalist seat used when no product domain, client platform, layer specialization, or higher seniority tier defines the role. Product-domain, platform-specific, and level-specific titles remain separate 1:1 role packages with their own constraints, stakeholders, evidence, and Golden Q&A. The altitude and seams are explicit. The Senior Software Engineer owns the most ambiguous cross-service design and team-wide technical leverage, while this seat owns well-scoped to moderately ambiguous delivery with review. Backend, Frontend, and Full-Stack Engineers are layer specialists, while this seat is the generalist when no one layer defines the job. The Site Reliability Engineer owns SLOs, error budgets, and the reliability practice, while this seat operates the feature it ships without owning that practice. Two mental models should be visible in the work. The existing system is part of the requirement. A change that ignores established contracts, ownership, and operational behavior is incomplete even if the new code works in isolation. The smallest coherent change is easier to prove. Minimize conceptual surface, not merely line count. For this Software Engineer, those ideas must be visible in its signature artifacts, review request, release decision, and hand-off rather than remaining vocabulary.
Best-fit customer
engineering teams that want consistent judgement applied to design, review, and delivery
Need more than one role?
Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.