Senior Specialist, Technical Coordination

Senior Specialist, Technical Coordination

The job responsibilities outlined in this document are not exhaustive and may evolve over time and be reviewed according to business needs.

ROLE DESCRIPTION SUMMARY

Facilitates Agile software development processes to ensure smooth and efficient software development cycles. Acts as a servant-leader to the development team by removing impediments, fostering collaboration, and promoting continuous improvement. Coordinates sprint planning, daily stand-ups, sprint reviews, and retrospectives. Works closely with Software Architects, Tech Leads, developers, QA, Release manager and other stakeholders to align project goals and ensure timely delivery of high-quality software products.

PRIMARY RESPONSIBILITIES / KEY RESULT AREAS

• Schedule and facilitate Agile ceremonies (Sprint Planning, Daily Stand-ups, Reviews, Retrospectives)
• Provide clear visibility and reporting on project and sprint progress to stakeholders
• Track demand and project implementation for single or multiple teams
• Represent the team in program-level meetings and cross-team coordination
• Act as the main point of contact for team and project-related issues
• Manage Azure DevOps tickets and ensure user story information is complete and up to date
• Shield the team from external disruptions to maintain focus and productivity
• Monitor and track progress of user stories and tasks throughout the sprint
• Coordinate with release management for smooth deployment and delivery processes

COMPETENCIES

• Excellent communication, interpersonal, and conflict resolution skills
• Ability to identify and remove impediments to ensure smooth team progress
• Proactively identifies ways to contribute to the team and wider SES goals. Shows the ability to motivate self, complete tasks and achieve goals.
• Accountability: holds self and others accountable for individual and team results. Accepts responsibility for mistakes. Uses resources in an efficient way. Shows honesty and truthfulness
• Ability to work autonomously as well in collaboration with other members of the team with minimal supervision with a commitment to KPI`s
• Service and customer-centric mindset
• Openness for new technologies, ability to learn them quickly, and readiness for change.
• Ability to work in a rapidly changing environment under tight timelines.
• Fluent in spoken and written English; additional languages are an asset

QUALIFICATIONS & EXPERIENCE

• Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field
• Strong understanding of Agile principles, Scrum framework, and other Agile methodologies
• Hands-on experience working as a Scrum Master or Agile Coordinator in a software development environment, facilitating Agile ceremonies and managing cross-functional teams
• Prior experience as a software developer or working closely with development teams to understand technical workflows and challenges
• Experience with Agile project management tools (e.g., Azure DevOps, Jira, Trello)
• Strong organizational skills with the ability to manage multiple priorities simultaneously
• Strong verbal and written communication skills for reporting, documentation, and stakeholder updates
• Familiarity with software development lifecycle and release management processes
• Familiarity with AI tools and platforms to enhance Agile processes, such as automating routine tasks, analytics, or progress tracking
• Certified Scrum Master (CSM), Professional Scrum Master (PSM), or equivalent Agile certification preferred

Based on our discussion, should we change this to "Agile SW development" to include kanban and scaled agile?

how would that fit with the tech lead, the architect and the PO? Can we map them in a RACI matrix to make sure we are increasing redundancy and unnecessary layers and or confusion?

This is a split of current tech lead role. Keeping tech lead as more technical topics oriented and SM for coordination. But yes, we are including it in the RACI

do we want to add that ability and willingness to step in as developer from time to time is a plus? it would help justifying the extra role and also with the fluctuations of the dev backlog.

I'm not expecting SM to act as developer. If we have 2 SM in the team, I believe they will be more than busy. But I don't want secretaries... I want people able to understand code, understand developers and their concerns

SES and its Affiliated Companies are committed to providing fair and equal employment opportunities to all. We are an Equal Opportunity employer and will consider all qualified applicants for employment without regard to race, color, religion, gender, pregnancy, sex, sexual orientation, gender identity, national origin, age, genetic information, protected veteran status, disability, or any other basis protected by local, state, or federal law.

For more information on SES, click here.