Get more replies from employers
Send a job-specific resume in minutes.
Farmforce in Oslo seeks a Development Chapter Lead, the senior engineering leader responsible for standards, architecture, maturity, and people across the Technology organization. This hands-on leadership role combines coding with strategy, reporting to the CTO and shaping how we build software.
You will define coding standards, lead architectural reviews, manage engineers, and contribute as a senior engineer in product squads. Fluent English required; Norwegian preferred.
Farmforce
Farmforce builds supply chain traceability software for the global food industry. Our platform connects food companies directly to the farms that supply them, tracking over one million farmers across 30+ countries in Africa, Latin America, and Southeast Asia. We are a ~50-person company headquartered in Oslo, with offices in Abidjan, Bangkok, and Guatemala City.
We are in an deliberate investment: building an AI-first engineering organization that develops software smarter, faster, and more impactful. The person we hire for this role is at the centre of that transformation.
Industry:Information Technology & Services
Employment Type:Full-time
Job Opening: Development Chapter Lead
Location:Oslo, Norway. Regular in-office presence required.
Start date: December 1, 2026 (target). Earlier availability is a plus.
Languages:Fluent English required. Norwegian preferred. French, Spanish, or Thai a bonus.
The Development Chapter Lead is the senior-most engineering leadership position at Farmforce, reporting directly to the CTO, and member of the tech leadership team. You own the software development capability of the entire Technology organization: its standards, architecture, maturity, and people.
In Farmforce's delivery model, the Development Chapter Lead holds organizational-level engineering authority. You define the standards that all developers follow across delivery teams, make architectural decisions that last, and hold the team to the technical bar you set, all in collaboration with the CTO. You also contribute actively as a senior engineer in a product squad. Hands-on involvement is a core expectation. This is a hands-on leadership role, not a pure-management or pure-IC seat. You will set engineering standards, architect, lead people, and write code, and the balance between those shifts with what the chapter needs.
You will work closely with the CTO to reshape how Farmforce builds software. If you want to build something that matters and leave a mark on how a global technology organization operates, this is that role. This way of working is new and still evolving. You will help define it, not inherit it.
You are a systems thinker and a practitioner. You bring deep architecture knowledge, current hands‑on engineering skills, and proven experience setting technical direction across a developer organization. You have held personnel responsibility for developers and take that seriously.
What matters as much as your technical depth is your mindset. We care more about how you approach engineering than the specific tools you currently use. You have moved beyond AI as autocomplete: you design how engineering work gets planned, delegated to agents, and verified, and you have helped others work that way too. You hold high standards for yourself and raise the bar for those around you, by example as much as by direction.
On the tech stack: Farmforce's primary stack is Java and Python. We care more about how you think and build than the specific language you currently work in. A strong architectural foundation and an AI‑first mindset matter more to us than years in a particular toolchain. The stack is learnable. The attitude is not.
On education: A Master's degree in Computer Science, Data Science, or Artificial Intelligence is a definite plus. That said, equivalent experience, the right mindset, and a genuine commitment to continuous learning matter more to us than a formal diploma. If the rest of this ad speaks to you, we want to hear from you.
In short: not a vibe coder, not a hands‑off manager, not an AI‑skeptic engineer. This role needs all three held at once: technical depth, people leadership, and a genuine AI‑first practice.
If any of those describe you right now, we respect that. It is just not the right match for this role and this moment.