Software Engineer, Developer Productivity

About the role

As a Software Engineer, Developer Productivity at Forus, you will own the systems that determine how fast our entire engineering team ships. Velocity is one of Forus' core advantages, and this role exists to compound it. You will own the CI/CD, operational workflows, build systems, and development environments that every engineer depends on, and the infrastructure that lets us build with AI coding agents rather than around them. You will operate across the whole engineering org: owning the path from commit to production, designing the infrastructure that lets coding agents work safely and effectively in our codebase, automating the toil that slows everyone down, and driving company-wide adoption of agentic development.

You will define what "fast" means at Forus, instrument it, and be measured on real outcomes: faster feedback loops, faster onboarding, and more shipped per engineer. It is a high-leverage, high-context seat that touches every team and directly shapes how quickly we can build. This is a demanding role, with a high level of autonomy and responsibility. You will be expected to "act like an owner" and commit yourself to Forus' success.

Requirements

• A track record of building developer tooling, internal platforms, or CI/CD and development-environment infrastructure that other engineers depend on.
• Strong systems and infrastructure instincts – you write production code, live in your terminal, and instinctively build reusable tools; strong in Python and Bash/Unix.
• Gone deep on modern agentic development yourself (Claude Code, Codex, or similar) and want to productize that leverage for a team; you do not need prior experience building AI systems, but curiosity and evidence of shipping matter.
• Demonstrated ability to drive adoption and change how a team works, not just hand over a tool.
• The ability to go from an ambiguous problem to a clear, structured, shipped solution with minimal guidance.
• A high NPS with your former teammates.

Qualifications

• A track record of building developer tooling, internal platforms, or CI/CD and development-environment infrastructure that other engineers depend on.
• Strong systems and infrastructure instincts – you write production code, live in your terminal, and instinctively build reusable tools; strong in Python and Bash/Unix.
• Gone deep on modern agentic development yourself (Claude Code, Codex, or similar) and want to productize that leverage for a team; you do not need prior experience building AI systems, but curiosity and evidence of shipping matter.
• Demonstrated ability to drive adoption and change how a team works, not just hand over a tool.
• The ability to go from an ambiguous problem to a clear, structured, shipped solution with minimal guidance.
• A high NPS with your former teammates.