Neil Sherman
Chief Software Architect @Naviquate
Signup · Get unlimited contacts
WORK HISTORY
Chief Software Architect @Naviquate
Shaping technical direction across multiple product lines serving millions of users across web, iOS and Android. → Multi-year technology roadmaps and architecture governance → Full-stack system design: backend services, APIs, frontend, cloud infrastructure → High-performance search and complex data integration → Cloud cost optimisation, CI/CD strategy, and progressive deployment → Security architecture, resilience patterns, and disaster recovery → Legacy modernisation through incremental patterns — not rewrites → AI and agentic tooling embedded into real engineering workflows → Technical strategy presented to board-level stakeholders → Architecture reviews, coding standards, and engineering mentorship → Vendor evaluation and build-vs-buy analysis
EDUCATION
University of Southampton
Bachelor of Science, Computer Science
SKILLS
ABOUT NEIL SHERMAN
I\'ve spent twenty-five years building software that people depend on without thinking about — high-availability systems handling millions of transactions, search engines returning results in single-digit milliseconds, platforms running across web, iOS and Android from shared codebases. All of that depth at one organisation, by choice. I chose architectural maturity over job-hopping. The result is a rare combination of hands-on technical leadership and long-term strategic thinking — and skills that transfer directly to any domain where complex data meets demanding users. As a Chief Software Architect, I shape technical direction across multiple product lines: → System design and technical architecture across the full stack → Technology strategy, roadmapping, and architecture governance → High-performance search and data integration at national scale → Cloud infrastructure, CI/CD pipelines, and cost optimisation. → Security architecture, resilience patterns, and disaster recovery → Legacy modernisation — incrementally, not rewrites → AI and agentic tooling in real engineering workflows → Translating technical risk into the language the boardroom understandsJava · Spring Boot ·.NET Core · Angular · Ionic · Azure · Apache Lucene · Domain-Driven Design · CQRS · Event-Driven Architecture · Microservices · API Design · Docker · CI/CD · WCAG Accessibility I believe the best architects stay close to the code. I still read it, write it, and review it — because architectural decisions made in isolation from implementation reality are the ones that get quietly worked around. I write about software architecture, system design, and engineering practices at neilsherman.co.uk.
This profile is compiled from publicly available professional sources. Unifers is not affiliated with or endorsed by LinkedIn. Request removal of this profile.