Software Engineer
We are looking for Staff Software Engineers who have stopped measuring their impact by how much code they personally write and started measuring it by how much better the entire engineering system performs.
𝗪𝗲’𝗿𝗲 𝗵𝗶𝗿𝗶𝗻𝗴 𝗿𝗼𝗰𝗸𝘀𝘁𝗮𝗿𝘀.
We are looking for Staff Software Engineers who have stopped measuring their impact by how much code they personally write and started measuring it by how much better the entire engineering system performs.
Gradion is hiring a Staff Software Engineer, AI-Native to work across systems, teams and technical domains. Your scope is bigger than one product or one technical layer. You will shape systems spanning web, desktop and mobile front ends, back-end services and APIs, data pipelines, infrastructure, testing, security and operations.
You are a software engineer first . AI is how you work.
The working rule on this team is 𝘇𝗲𝗿𝗼 𝗵𝗮𝗻𝗱-𝘄𝗿𝗶𝘁𝘁𝗲𝗻 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗰𝗼𝗱𝗲 . You work through Claude Code, Codex and whatever replaces them next, and you own every line that lands even though you do not type it. Your job is to turn outcomes into specifications, give agents the context and constraints they need, direct the implementation, and prove the result before it ships.
At Staff level, that leverage extends beyond your own work. You shape how other engineers work with agents, establish technical standards, identify where the real difficulty sits, and create patterns that help teams move faster without lowering the engineering bar.
The implementation may be generated. The engineering judgement is yours.
You decide the boundaries, data models, failure behaviour, trade-offs, security controls, migration paths and operational concerns that AI will not decide for you. You know when to build, when not to build, and when a plausible answer from an agent is still the wrong answer.
If your best work still comes from writing the hardest code yourself, this is probably not the right role. If you want your technical judgement to influence systems, teams and the way software gets built, keep reading.
𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗿𝗼𝗹𝗲 𝗶𝘀 𝗿𝗲𝗮𝗹𝗹𝘆 𝗮𝗯𝗼𝘂𝘁
Setting technical direction across systems and teams. Turn ambiguous problems into architecture, constraints and an approach that engineers can execute against.
Owning architecture and delivery for complex systems. Stay involved from specification and design through implementation, testing, deployment and production operation.
Designing how engineers work with AI agents. Establish the conventions, repository context, tooling, evaluation methods and quality gates that make agents reliable on real production work.
Making the decisions AI will not make for you. Shape boundaries, data models, failure behaviour, scalability, security, migration paths and the trade-offs that are expensive to reverse.
Raising the quality of engineering output. Review the implementations carrying the most risk, set standards others can review against, and build mechanisms that catch bad output before it reaches production.
Posted September 28, 2026