π€ 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.
Accountabilities (Key Responsibilities)
Continuously improve team efficiency, tooling, and automation
Refine tasks within the given context
Participate in the teamβs work planning, operational decision-making, and governance
Ensure reliable operation of the Service and handle disruptions
Collaborate with customers and other stakeholders on implementation, changes, and support of the Service
Provide technical advice and insights to Product Owners and Solution Architects
Implement and evolve product features and solutions in a maintainable and sustainable way
Maintain an understanding of the Service, its architecture, capabilities, and limitations
Stakeholders and Key Deliverables
- 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
- 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.
- Team Facilitator 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.