Application Maintenance Engineer

The Application Maintenance Engineer is responsible for ensuring the operational stability, maintenance, and continuous improvement of enterprise applications across both Linux and Windows environments. The role involves executing instruction-based maintenance tasks while leveraging analytical and creative problem-solving skills to investigate issues, optimize processes, and enhance application reliability. The engineer works under the guidance of the Application Maintenance Lead and collaborates closely with maintenance, QA, development, and operations teams.Key ResponsibilitiesExecute maintenance, configuration, and update tasks according to documented procedures.Perform advanced troubleshooting and root cause analysis across application, OS, and container layers (Docker/Podman).Investigate and interpret application and system logs to identify issues and propose corrective actions.Validate configurations and verify service functionality after releases or infrastructure changes.Apply independent judgment when resolving issues not fully covered by predefined instructions.Collaborate with the Lead and peers to refine and improve maintenance documentation.Participate in change and release activities, including pre-checks, post-validation, and rollback coordination.Communicate findings clearly to the Lead and related teams.Maintain accurate and up-to-date operational documentation.Contribute to process improvements and knowledge sharing within the maintenance team.Scope & BoundariesIn Scope:Application maintenance, updates, configuration, and troubleshooting in Linux and Windows environments.Root cause analysis and operational improvements within established frameworks.Support for change/release activities and validation of deployed services.Documentation and refinement of operational procedures.Out of Scope:Application development or feature design.End-user or customer-facing support.Infrastructure ownership or vendor management.Long-term architecture or platform design responsibilities.Applications and Tools in ScopeEnterprise Applications: Confluence, ServiceNow, and other internal systems.Container Platforms: Docker, Podman.Operating Systems: Linux (openSUSE, SLES) and Windows Server.Monitoring & Logging: Zabbix, system and container logs.Networking Tools: IP, DNS, and connectivity troubleshooting utilities.Required CompetenceHands-on experience in application operations, maintenance, or support.Strong troubleshooting skills in Linux (openSUSE, SLES, or similar) and Windows Server.Practical experience with Docker or Podman for containerized applications.Understanding of network fundamentals and inter-service dependencies.Experience analyzing system and application logs to identify and resolve issues.Working knowledge of ServiceNow, Confluence, or similar enterprise systems.Ability to update and validate applications following defined change and release procedures.Strong communication skills and fluency in English (spoken and written).Soft Skills:Analytical and curious, investigating root causes beyond the surface.Structured and reliable, following process and documentation standards.Collaborative, sharing insights effectively across teams.Creative problem-solver, applying logic and initiative when encountering new issues.Service-minded, committed to operational stability and quality.Adaptable, comfortable across diverse systems and environments.Assignment OverviewThe Application Maintenance Engineer will provide L2/L3 operational support for multiple applications. The role involves close collaboration with Swedish and Polish teams to maintain system stability, perform updates, and support development and release activities.Typical Tasks:Investigate and resolve application incidents (approx. 10–15 per month).Update and validate applications during maintenance and release cycles.Support new releases through configuration checks and application health monitoring.Execute configuration updates and minor fixes as per approved procedures.Participate in evening change/release windows (1–2 evenings per week, shared across the team).Monitor logs, containers, and services to detect issues early.Update certificates or configurations (e.g., in Kubernetes-based identity management systems).Perform first-level analysis of application errors, including JavaScript/TypeScript logs for web-based systems.Collaborate with infrastructure and application owners to isolate and resolve issues.Technologies and ToolsOperating Systems: Linux (openSUSE, SLES), Windows ServerContainers: Docker, PodmanVersion Control / CI: GitHub Actions (release workflows)Monitoring: Zabbix, system and container log toolsNetworking: IP, DNS, routing, connectivity troubleshootingScripting & Configuration: YAML, Bash, PowerShell (basic)Applications: Confluence, ServiceNow, and other internal enterprise systemsOperational ConditionsService Hours: 08:00–17:00 CET, five days per weekOn-Call: 07:00–22:00, seven days a weekIncident Volume: ~10–15 incidents/month (low-volume, high-stability environment)Collaboration: Direct coordination with Swedish-based Lead, developers, and system ownersExpected OutcomeStable and up-to-date application environments across all supported systems.Well-documented and continuously improved maintenance procedures.Efficient incident response and transparent communication with stakeholders.Incremental improvements to operational reliability and efficiency.