Engineer

Purpose

The Engineer role enables the successful delivery and operation of VSHN services by building, evolving, and running products and custom solutions in close collaboration with the team and—depending on context—directly with customers. By implementing solutions and product features according to requirements, and by communicating technical expertise where it creates value, this role ensures that each Service fulfils its intended purpose and operates reliably in customer environments.

Key Responsibilities

List the essential responsibilities assigned to this role.

  • Maintain an understanding of the Service, its architecture, capabilities, and limitations

  • Implement and evolve product features and solutions in a maintainable and sustainable way

  • Provide technical advice and insights to Product Owners and Solution Architects

  • Collaborate with customers and other stakeholders on implementation, changes, and support of the Service

  • Ensure reliable operation of the Service and handle disruptions

  • Participate in the team’s work planning, operational decision-making, and governance

  • Refine tasks within the given context

  • Continuously improve team efficiency, tooling, and automation

Stakeholders and Key Deliverables

Whom does this role deliver value to, and what do they need from this role?

Product Owner of the Engineer’s team

  • Technical knowledge about the product or solution building blocks and its architecture.

  • Implementation of new features or changes to the Service

  • (Support) Backlog item creation, refinement and estimation.

Solution Architects

  • The implementation of customer solutions.

  • The setup or changes to product instances of customers.

  • Technical details of the (future) architecture.

Customer

  • Technical knowledge and support for specific questions (via ticket).

  • Response to incidents (as defined in customer contract).

  • Continuous development of product features and improvement of existing solutions.

Team

  • Active contribution to the team’s work backlog

  • Active contribution to Service reliability, support and incident handling (including 24/7 OnCall)

  • Active contribution to the team’s work planning, operational decision-making and governance

  • Sharing of technical knowledge

  • Transparently documented work progress and status

  • Documentation of Service architecture and technical procedures

Dependencies

Who and what does this role depend on?

Product Owner of the Engineer’s team

  • This role depends on the Product Owner for actionable backlog items and prioritization of work.

  • The Product Owner provides requirements for new features that are to be developed, and for new solutions that are to be built for customers.

  • Context (What and Why) for product related tasks

Solution Architect

  • Context (What and Why) for solution related tasks in the scope of projects (Epics) or bigger changes.

  • Advice (as suggestion) on approach how to build or change things.

Scrum Master of the Engineer’s team

  • The Scrum Master provides a functioning framework, within which a team’s DevOps Engineers can perform their work and collaborate effectively.

Team

This role depends on the team for clear communication, positive collaboration, up-to-date documentation of activities and outcomes, and proactive knowledge sharing.