SAFe Solution Train Engineer Wireless Technology, Agile @w2 only

Job Description:

The BSSe Solution Train Engineer is responsible for facilitating end-to-end delivery of value at the Epic level across cross-functional product, engineering, architecture, testing, and delivery teams. This role owns the integrated execution view for assigned Epics, drives proactive dependency and risk management, maintains delivery discipline, scales team adoption of approved AI and automation practices, and ensures leaders have clear, decision-ready visibility into scope, sequencing, commitments, milestones, and delivery health.

About the Team

The BSSe Wireless Delivery Team leads execution across one of AT&T s most strategic technology modernization efforts: moving wireless customers from legacy platforms to a simplified, scalable BSSe platform. The team partners across product, engineering, architecture, testing, release management, business stakeholders, and supplier teams to deliver roadmap capabilities, migration cohorts, and critical customer-facing functionality with disciplined planning, clear accountability, and proactive risk management.

The team is focused on delivering seamless migrations through the lightest-lift path, challenging legacy-driven complexity, and enabling working software that supports business commitments, customer readiness, and future platform growth. Team members operate in a highly cross-functional environment where collaboration, delivery transparency, data quality, dependency management, executive-ready communication, and scaled use of approved AI and automation are essential to meeting milestone outcomes.

Role Summary

The STE serves as the Epic-level delivery leader and integrator for BSSe, ensuring that scope, milestones, dependencies, risks, commitments, and automation opportunities are visible, aligned, and actively managed from pre-planning through execution. The role requires strong Agile delivery experience, executive-ready communication, structured problem solving, responsible AI adoption, and the ability to influence across teams without absorbing ownership that belongs to product, engineering, architecture, testing, or business partners.

Key Responsibilities

• Own the integrated execution view for assigned Epics, including scope, sequencing, delivery status, dependencies, risks, milestones, critical path, and impacts to commitments.
• Lead Epic-level pre-planning and PI Planning readiness activities, ensuring teams understand scope, outcomes, feature decomposition, dependency needs, and milestone expectations.
• Establish and lead cross-functional Epic forums that create visibility, decisions, action closure, and accountability across TPM, product, architecture, CQE, engineering, and delivery teams.
• Drive proactive dependency identification, validation, documentation, sequencing, ownership, follow-up, and escalation before dependencies create milestone risk.
• Maintain feature and Epic hygiene by ensuring delivery data is current, complete, and trusted for planning, execution, reporting, and leadership decision-making.
• Escalate likely misses, unresolved dependencies, delivery risks, and readiness gaps early with clear impact, accountable owners, mitigation options, decisions needed, and timing.
• Translate delivery details into milestone-level impact and decision-ready guidance for leaders, including implications to critical path, commitments, and release confidence.
• Partner with CQE and delivery teams to align Epic-level test strategy, environment readiness, defect resolution, and production validation plans.
• Scale the team s use of approved AI and automation tools to improve planning, reporting, follow-up, delivery analysis, risk detection, dependency tracking, meeting effectiveness, and responsiveness while validating outputs and applying sound judgment.
• Drive continuous improvement by strengthening operating cadences, delivery discipline, governance, data quality, accountability, repeatable practices, and automation-enabled ways of working across the program.

Expectations

• Role clarity and ownership: Clarifies who owns what, drives the right people to act, and reduces ambiguity across STE, TPM, product, architecture, testing, and delivery teams.
• Delivery discipline: Maintains a credible, current integrated plan and reinforces disciplined feature, Epic, dependency, and milestone tracking.
• Proactive risk management: Identifies risks and likely misses early, escalates with precision, and connects issues to milestone impact before dates slip.
• Forum leadership: Runs working sessions that move work forward, create accountability, resolve blockers, and produce clear actions, decisions, and follow-through.
• Stakeholder partnership: Builds trust across cross-functional teams, communicates clearly, manages tension constructively, and avoids surprises.
• Executive-ready communication: Provides crisp, structured updates with status, impact, owners, mitigation, decisions needed, and confidence level.
• Judgment and influence: Influences outcomes without formal authority, challenges assumptions when needed, and ensures delivery ownership remains with accountable teams.
• AI and automation enablement: Identifies practical use cases, encourages responsible adoption, helps teams build repeatable AI-enabled workflows, and measures whether automation is improving speed, quality, transparency, and follow-through.
• Continuous improvement: Identifies practical improvements, implements repeatable practices, and strengthens predictability, transparency, and delivery confidence over time.