Software Engineer

Key Responsibilities

Core accountabilities and decision ownership

Implement features, fixes, APIs, components or migration assets from clear designs and acceptance criteria.

Write maintainable code and automated tests, participate in review, and keep technical documentation and operational notes current.

Learn X3 processes, metadata, Xtrem/X3 architecture and the effect of changes on customers, partners and upgrades.

Use CI/CD, observability and local diagnostics to find problems early; escalate uncertainty with evidence.

Contribute to refactoring, automation, accessibility, performance and reliability improvements within the squad.

Decision ownership:

Implementation choices within agreed patterns, test coverage for owned changes, and prompt escalation when requirements, customer behaviour, security or rollback are unclear.

Common capability baseline

All X3 roles are expected to build capability in the following areas. Depth and decision scope increase with level:

Understand X3 customer workflows, metadata, customisation and architecture well enough to protect supported behaviour, partner investment and SaaS readiness in the decisions owned by the role.

Treat the internal platform as a product: use developer and operator research, feedback and adoption evidence to reduce cognitive load; provide self-service APIs and golden paths where they solve a demonstrated need.

Use cloud-native service boundaries, versioned API contracts and event integration where appropriate, preserving compatibility and clear ownership across X3 capabilities.

Apply CI/CD and secure software-supply-chain controls, with identity, secrets and policy enforcement built into relevant delivery and runtime paths.

Make services diagnosable with OpenTelemetry-compatible logs, metrics and traces; define role-appropriate SLOs, reliability and resilience evidence.

Manage performance and cost deliberately, and engineer lifecycle, upgrade, deprecation and rollback paths as part of supported capability ownership.

Use migration, reconciliation and compatibility evidence to preserve customer data and behaviour while moving towards portable, secure, cloud-operable and upgradeable capabilities.

Use AI-assisted engineering securely, with human review, privacy and IP protection, regression evidence and a recovery path; use deterministic methods when they are more appropriate.

Depth follows role scope: engineers demonstrate hands-on lifecycle capability in their discipline; managers, product and programme leaders, and architects need decision-relevant fluency, not universal coding or every tool. Containerisation and Kubernetes are required for all engineering roles. Infrastructure as code, GitOps and a custom internal developer platform apply where the role owns those paths.