Software Engineer, MDDI

Software Engineer Role

As a Software Engineer, your scope includes contributing to multiple components or features within your team, with growing independence in driving development. You are expected to deliver moderately complex tasks, balancing quality, speed, and maintainability, while still collaborating closely with team members for design and planning. You take more initiative in suggesting improvements, supporting teammates, and building awareness of the broader product and technical ecosystem. Your impact extends beyond individual tasks to positively affect team processes and product outcomes. You influence quality of deliverables, and contribute to reliable and maintainable systems.

Craft and Execution

Deliver features across multiple components independently:

• Deliver POCs or features that span multiple components/modules, with guidance when needed.
• Make thoughtful trade-offs between performance, security, and maintainability based on your understanding of context.
• Write/review code with clarity and maintainability in mind, applying good practices consistently.
• Expand test coverage (e.g. unit, integration) to support key workflows and reduce flakiness.

Improve code reliability and maintainability:

• Address small pockets of technical debt within your domain.
• Suggest small improvements that enhance product performance or team velocity.
• Contribute to CI/CD processes and deployment pipelines in collaboration with the team.
• Contribute to resolving moderate incidents with team support; escalate complex issues when needed.

Deepen product and platform technical knowledge:

• Develop a deeper understanding of your product's architecture and dependencies.
• Apply secure coding and compliance principles with guidance, integrating platform standards into your work.

Ownership

Own moderately complex features from start to finish:

• Independently plan and complete moderately scoped tasks, from design to delivery.
• Flag risks early.

Monitor and validate impact of your work:

• Follow through on the impact of your work after it ships (e.g., metrics, bugs, or feedback).
• Proactively troubleshoot and fix small production issues.

Actively seek and provide constructive feedback:

• Seek and apply feedback regularly on both code and working style.
• Actively participate in team knowledge-sharing activities (e.g., demos, retros, or guilds).

Unblock and support team members when needed:

• Provide constructive code review feedback to peers and junior engineers.
• Help others get unblocked or navigate tools, documentation, or context within your team.

Strategic Alignment

Align work with team and product priorities:

• Align your tasks with team goals and priorities; suggest improvements where you see opportunities.
• Ask clarifying questions when requirements are unclear.

Balance short-term delivery with code health:

• Demonstrate the ability to balance short-term delivery with long-term code health.
• Participate in discussions about solution design and trade-offs, contributing your perspective.

Apply platform and compliance standards effectively:

• Use relevant organizational stack, platforms, or standards effectively in your work.
• Understand compliance, cost, and performance considerations that affect your domain.

Culture and Organisational Influence

Model good engineering practices for peers:

• Reinforce the organization's engineering values through your day-to-day work and interactions.
• Help newer engineers navigate team workflows or practices.

Actively shape and reinforce team culture:

• Participate in engineering-wide activities like retros, internal talks, or improvement initiatives.
• Engage respectfully with cross-functional collaborators (e.g., Product, UX) in shaping good outcomes.

Share knowledge and mentor junior engineers:

• Share technical insights or lessons learned in informal settings (e.g., demos, brown bags).
• Support newer engineers in small ways, such as explaining concepts, debugging strategies, or team practices.

Traits We're Looking For:

Technical Depth:

• Has designed, built, or operated systems; credible when discussing code or architecture.

Product Mindset:

• Frames problems clearly, focuses on user and agency outcomes, validates assumptions early, and guides teams toward evidence-based decisions.

Lifecycle Awareness:

• Knows how to move from discovery → POC → POV → scale; understands how practices, architecture, and operational rigour should evolve through each stage.

Pragmatic Leadership:

• Balances ideal designs with delivery realities.

Collaborative Energy:

• Works easily with Product and Design; values diverse perspectives.

Curiosity and Growth:

• Keeps learning and helps others adapt to new technologies and practices.
• Keeps up with modern practices like AI-assisted development and platform automation.