Modelling Software Engineer

Key Responsibilities

• Take full ownership of medium-complexity features and components end-to-end — design, implementation, testing, and production operation; you are responsible for their health over time, not just at point of delivery.
• Break down and estimate your own work reliably; deliver in increments so value is visible early and feedback arrives continuously.
• Review others' code substantively — give technical feedback that helps the author improve, not just flags issues.
• Contribute to technical discussions in the squad; offer solutions, not just problems.
• Actively support the engineers around you — junior engineers in particular — in technical and non-technical areas.
• Operate within the cross-office squad as a full peer — participate in shared ceremonies, communicate clearly across time zones, and default to written decisions so neither office is blocked.

Skills, Knowledge & Expertise

• 2–4 years of professional software engineering experience with a track record of independent ownership of production software.
• Strong Python engineering skills — this is the primary language of the codebase.
• Track record of code review and giving constructive technical feedback.
• Comfortable breaking down and estimating work independently; reliable delivery.
• Evidence of thinking about the "why" as well as the "how" — understands what value their work provides and can connect technical decisions to business outcomes.
• Collaborative — actively supports the people around them, not just their own output.
• Meaningful exposure to AI-assisted engineering across the development workflow — you have used these tools in practice and have a view on where they genuinely add value.
• Full professional fluency in both English and Portuguese (written and spoken); English is the primary working language across both offices.
  
  

• Experience with scientific computing, numerical methods, or domain-specific software (energy, finance, or similar).
• Familiarity with agile delivery in squad-based teams.
• Energy market or power systems domain knowledge — you understand the problems the models are solving, not just the software that solves them.
• Experience working in or with a distributed or cross-office team.

• 0–3 months: Operating independently on your assigned squad work. Code reviews are substantive. You understand what your squad is building and why. Your squad lead is not in your workflow for routine decisions.
• 3–6 months: You have owned at least one feature end-to-end, including its production operation. You are a reliable code reviewer. You are starting to coordinate smaller pieces of work involving other engineers.
• 6–12 months: Consistently productive on medium-complexity components. Actively supporting junior engineers. The team knows what you are working on and trusts your estimates. Starting to show an appetite for the next level of ownership.

Benefits

• A fun, informal and international work culture
• A competitive salary package
• Access to regular coaching and mentoring sessions and the opportunity to learn from experienced professionals
• Access to the Aurora Academy, our training programme offering a range of opportunities to develop your skills within the responsibilities of your role and within the wider context of the industry.