Search

Application Support Engineer

PublishedPublished: 6/14/2022
Technology

Job Description

Job Title: Application Support Engineer

\n

Location: Newark, NJ – Hybrid (3 days onsite per week)

\n

Duration: 12 months (contract to Perm Hire)

\n


\n

About Role:

\n

We are seeking an experienced Application Support Engineer to manage and enhance the stability, performance and availability of our client facing applications. This role requires a proactive leader who can guide a dedicated support team, collaborate with engineering teams, and effectively manage incidents to minimize downtime, improve user experience and communicate with stakeholders.

\n


\n

Key Responsibilities:

\n

Incident Management and Resolution:

\n

    \n
  • Oversee the triage, investigation and resolution of production issues, ensuring timely communication and status updates.
  • \n

  • Manage incident response efforts, including documentation and root cause analysis and post-incident reviews to identify preventative actions.
  • \n

  • Establish clear escalation protocols and ensure adherence to serve level agreements (SLAs).
  • \n

  • Coordinate resolution and follow ups with dependencies outside immediate team.
  • \n

  • Coordinate KTs between development teams and L1/L2 triage to establish runbooks and knowledge base Team Leadership and Coordination.
  • \n

  • Coordinate with development, QA, and infrastructure teams to ensure seamless issue resolution and knowledge sharing.
  • \n

  • Foster a strong ownership mindset within the team, ensuring accountability for system health and stability.
  • \n

\n

Monitoring and Alerting:

\n

    \n
  • Define and maintain effective monitoring solutions in partnership with development teams to proactively identify and address potential issues.
  • \n

  • Continuously improve observability by implementing dashboards, alerts and automated health checks in partnership with development teams Process and Documentation.
  • \n

  • Develop and maintain detailed runbooks, SOPs and knowledge base articles to ensure consistent response procedures.
  • \n

  • Establish best practices for incident response, including communication templates and decision frameworks.
  • \n

\n

Stakeholder Communication:

\n

    \n
  • Serve as the primary point of contact for production issues affecting client experiences
  • \n

  • Provide clear, concise updates to leadership, internal teams and clients during incidents and post-incident reviews.
  • \n

\n

Continuous Improvement:

\n

    \n
  • Identify patterns in recurring incidents and partner with development teams to implement permanent fixes.
  • \n

  • Drive initiatives to enhance system reliability, scalability, and performance.
  • \n

\n


\n

Qualifications and Skills:

\n

    \n
  • Proven experience in a production support leadership role for client facing applications.
  • \n

  • Strong understanding of incident management frameworks.
  • \n

  • Proficiency in troubleshooting application, database, and infrastructure issues.
  • \n

  • Familiarity with monitoring tools such Dynatrace, Datadog , Splunk etc.
  • \n

  • Familiarity with incident management platforms such as ServiceNow.
  • \n

  • Ability to prioritize tasks effectively, and communicate technical concepts to non technical stakeholders
  • \n

  • Excellent problem solving skills and a calm, solution-focused approach under pressure.
  • \n

  • Experience working in AWS
  • \n

  • Familiarity with CI/CD pipelines and release management processes
  • \n

\n


\n

Preferred:

\n

    \n
  • Background in software development or scripting for automation.
  • \n

  • Previous experience in the financial services industry Success Metrics
  • \n

  • MTTA: Mean time to acknowledge
  • \n

  • MTTR: Mean time to resolve
  • \n

  • Stakeholder satisfaction with incident communication
  • \n

  • Knowledge base usage rate and coverage
  • \n

  • Number of issues handed over to L1/L2, EMKT teams
  • \n

  • Measure # of system identified vs user reported alerts and trends over time
  • \n

  • Enhancements and alerts requested
  • \n

  • Minimize # of user reported incidents
  • \n

  • Measure incidents resolved with L1/L2 without app support team
  • \n

  • Reduction in resolution times due to documented processes
  • \n

\n


Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...