> Markdown version of [/jobs/ext/2041143-lead-solutions-architect-edwin-ai](https://www.wearedevelopers.com/jobs/ext/2041143-lead-solutions-architect-edwin-ai). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Lead Solutions Architect, Edwin AI

- **Company:** LogicMonitor
- **Location:** London, UK
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Software as a Service, Noise Reduction, Information Technology Operations, Data Streaming, Systems Integration, Multiplatform, Servicenow
- **Published:** August 13, 2026
- **Apply:** https://dejobs.org/x/x/91D748916A824ECFAB2479F6A562987B/job/

## About the Role

* 6+ years experience in Solutions Architecture, Professional Services, implementation consulting, enterprise SaaS delivery, technical architecture, or advanced customer engineering.
 * Strong working knowledge of service delivery, observibility/monitoring handoff points, data flows, ITSM workflows, third-party observability sources, and the broader customer operations ecosystem.
 * Deep working experience with ITSM platforms such as ServiceNow, Freshservice, and ConnectWise .
 * Experience designing integrations across multiple monitoring, observability, APM, ITOM, analytics, and workflow platforms.
 * Advanced ability to translate tasks, events, alerts, incidents, tickets, changes, escalations, and remediation steps into ITOps workflows.
 * Strong understanding of event correlation, alert noise reduction, ticket enrichment, routing, escalation, incident lifecycle design, and operational handoffs.

## Description

This role acts as a senior technical advisor, regional or domain subject-matter expert, mentor, and cross-functional delivery leader. The Lead Solutions Architect handles complex customer environments, advanced ITSM workflows, multi-platform integrations, pre-sales validation, repeatable delivery patterns, Project transition risks, and structured feedback to Product and Engineering.

This role is not simply "more implementations." The Lead Solutions Architect is expected to reduce delivery risk, improve time-to-value, mentor others, build repeatable practices, and help scale delivery beyond individual heroics. That aligns with the transcript discussion around senior roles focusing on strategic work, complex accounts, enablement, regional expertise, and process-building rather than repetitive project churn.

Here's a closer look at this key role

 * Lead complex or strategic Edwin implementations for enterprise and high-value customers.
 * Design advanced Edwin solutions that coordinate with Envision, core PS/PM ownership, ITSM workflows, third-party observability sources, FDE support, and partner-delivered work.
 * Own architecture for complex event ingestion, alert correlation, enrichment, investigation, incident creation, ticket routing, escalation, remediation, and value reporting.
 * Support major customers where continuity, regional context, Project transition planning, or advanced technical judgment is required.
 * Ensure complex implementations drive measurable time-to-value while protecting core PS capacity and customer continuity


## Related Videos

- [Mastering AI-Driven Problem Solving in Engineering with Observability](https://www.wearedevelopers.com/videos/994-mastering-ai-driven-problem-solving-in-engineering-with-observability)
- [The Dark Corners of Kotlin Multiplatform](https://www.wearedevelopers.com/videos/100143-the-dark-corners-of-kotlin-multiplatform)
- [Applying Agile Principles to Incident Management ](https://www.wearedevelopers.com/videos/101-applying-agile-principles-to-incident-management)
- [Python-Based Data Streaming Pipelines Within Minutes](https://www.wearedevelopers.com/videos/1233-python-based-data-streaming-pipelines-within-minutes)
- [AI in Production: applied AI & enterprise use cases](https://www.wearedevelopers.com/videos/100130-ai-in-production-applied-ai-enterprise-use-cases)
- [Why and when should we consider Stream Processing frameworks in our solutions](https://www.wearedevelopers.com/videos/1085-why-and-when-should-we-consider-stream-processing-frameworks-in-our-solutions)

## Related Articles

- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it)
- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)