Search by job, company or skills

Senior Technical Architect

Senior Technical Architect

ThoughtFocus
15-17 Years
Not Disclosed
  • Posted 25 minutes ago
  • Be among the first 10 applicants

Job Description

Role: Senior Technical Architect

Location: Kochi/Hyderabad

Notice Period: Immediate to 30days

Experience: 15+ years overall; 5+ years as a technical architect or solution lead

Architecture and delivery

  • Define and evolve the solution architecture for claims applications on Azure and .NET, including ASP.NET, C# Web API, Vue.js, React.js, TypeScript, and Kendo UI.
  • Design the claims platform as microservices: service boundaries around FNOL, documents, vendor orders, payments, and notifications; synchronous APIs versus Service Bus events; and data ownership so services do not share one database.
  • Define Node.js services where they sit beside the .NET estate, including API boundaries, shared contracts, and how Node services call Azure SQL or PostgreSQL.
  • Define the mobile architecture on .NET MAUI and Blazor, including shared UI, shared business logic, offline behavior, and how mobile clients call the same Web APIs as the web apps.
  • Define infrastructure as code with Terraform for resource groups, networking, data services, container registries, and application runtimes so environments can be rebuilt, not hand-configured.
  • Produce architecture decision records, integration designs, and non-functional designs for security, performance, availability, and observability across web and mobile.
  • Guide squads from design through release. Review pull requests and designs so the implementation matches the agreed architecture.
  • Set standards for APIs, front-end structure, mobile packaging, configuration, and secrets. Keep environments consistent across dev, test, and production.
  • The candidate should have practical experience working with Azure AI services, Document Intelligence, Large Language Models (LLMs), OCR, prompt engineering, and structured data extraction from complex documents.
  • Hands-on experience with Azure OpenAI and other LLM platforms.

Domain

  • Apply working knowledge of US property insurance claims: FNOL, coverage and policy interpretation at a solution level, loss adjustment, reserves, payments, subrogation, catastrophe surges, and regulatory expectations that shape system design.
  • Shape mobile claims journeys for field use: photo and document capture, FNOL intake, status checks, and offline work when connectivity is poor after a catastrophe.
  • Challenge requirements when they conflict with claims process, data lineage, or audit needs. Translate adjuster and operations workflows into technical scope.
  • Partner with business analysts, product owners, and client SMEs so technical choices protect claims cycle time and data integrity.

Third-party property claims services

  • Design and govern integrations with property-claims vendors used in inspection, roof and exterior measurement, imagery, and materials pricing. Required experience includes EagleView, Hover, ITEL, and Nearmap, plus the judgment to onboard similar vendors.
  • Define how vendor orders, imagery, measurements, material pricing, and reports attach to the claim file without becoming a second system of record.
  • Set patterns for partner APIs through API Management: authentication, throttling, retries, idempotency, callbacks, and failure handling when a vendor is slow or unavailable during a catastrophe.
  • Decide what field users capture on device versus what is ordered from EagleView, Hover, Nearmap, or ITEL, including cost, cycle time, and data-quality tradeoffs.
  • Keep vendor payloads, images, and pricing artifacts in Blob Storage with retention and access rules that match claims audit needs.

Identity and security

  • Design single sign-on with Microsoft Entra ID for web and mobile, including app registrations, conditional access alignment, token lifetimes, and role claims consumed by ASP.NET, the Vue or React front end, Node.js services, and MAUI or Blazor clients.
  • Define secure token storage and session handling on device. Keep secrets, vendor credentials, and certificates in Azure Key Vault. Define access patterns for App Service, Function Apps, containers, and integration runtimes.

Azure platform (must have)

  • Design and operate workloads that use App Service, Function Apps, Application Insights, Azure Monitor and alerts, Key Vault, resource groups, Blob Storage, Logic Apps, Service Bus, API Management, Azure Container Registry, Azure SQL, and PostgreSQL on Azure.
  • Use API Management as the front door for internal, partner, mobile, and vendor APIs. Use Service Bus for claims eventing, vendor callbacks, and asynchronous processing. Use Logic Apps where a low-code integration is the right fit, and Function Apps where code is required.
  • Use Azure Container Registry for container images consumed by the claims platform. Define image naming, retention, and how pipelines publish and promote images.
  • Choose and govern the data platform: Azure SQL for relational claims workloads that fit the Microsoft data stack, and PostgreSQL where the service or product standard requires it. Define connectivity, backups, and which system owns each data set.
  • Define resource-group structure, naming, tagging, and environment separation so cost, access, and release boundaries stay clear.
  • Instrument web, mobile, Node.js, and vendor-integration paths with Application Insights. Define alert rules and action groups so claims-critical failures page the right team.

Platform products in the landscape

  • Architect integrations and extension points for NopCommerce, SurveyJS, Salesforce, Titan Forms, and WordPress where those products sit in the client landscape.
  • Define how survey, commerce, CRM, and content flows exchange data with the claims core without duplicating the system of record.
  • Shape data-warehouse feeds from operational claims systems and vendor outputs: grain, keys, slowly changing attributes, and reconciliation with source systems.

Engineering leadership

  • Mentor technical leads and senior developers across web, API, mobile, Node.js, and integration squads. Run design reviews and architecture forums.
  • Estimate technical effort with delivery managers. Surface risk early when scope, vendor readiness, skills, or environment readiness.
  • Support production incidents as the technical authority. Drive root-cause fixes, not only workarounds.

Must-have skills

Application engineering

  • Strong .NET: C#, ASP.NET, and Web API, including modern .NET (not only .NET Framework).
  • Front end: Vue.js, React.js, TypeScript, and Kendo UI in production applications.
  • Node.js for APIs or integration services in a production landscape.
  • Microservices design in production: bounded contexts, API contracts, event-driven integration, independent deployment, and failure isolation.
  • Mobile development with .NET: .NET MAUI and Blazor, including Blazor Hybrid where a MAUI host embeds Blazor UI.
  • Practical judgment on what to share between MAUI, Blazor, and the Web API, and what must stay platform-specific.
  • SSO with Microsoft Entra ID, including securing APIs, SPAs, Node.js services, and mobile clients.

Data

  • Azure SQL.
  • PostgreSQL.
  • Clear ownership of which store is the system of record, and how data moves to the warehouse.

Azure (all required)

  • App Service
  • Function App
  • Application Insights
  • Monitor and alerts
  • Key Vault
  • Resource groups
  • Blob Storage
  • Logic Apps
  • Service Bus
  • API Management (APIM)
  • Azure Container Registry
  • Terraform for Azure infrastructure

Ways of working

  • Ability to write and present architecture that a client architect and a delivery manager can both use.
  • Clear written and spoken English for US client forums.

Good to have

DevOps

  • Azure DevOps Repos
  • Azure Pipelines
  • Azure DevOps Releases (or YAML multi-stage pipelines that replaced classic releases)
  • Mobile build and distribution through Azure Pipelines, including signing and store or enterprise distribution
  • Pipeline steps that build images and push them to Azure Container Registry

Adjacent platforms

  • NopCommerce
  • SurveyJS
  • Data warehousing (modeling, ETL or ELT patterns, and claims reporting marts)
  • Salesforce
  • Titan Forms
  • WordPress
  • Additional property-claims vendors beyond EagleView, Hover, ITEL, and Nearmap
  • Azure certifications (AZ-305 or equivalent) are useful, not a substitute for delivery evidence.

Domain

  • Hands-on or solution-level experience on US property insurance claims systems or equivalent P&C claims platforms serving US carriers or TPAs.
  • Comfort discussing FNOL, claim lifecycle states, payments, documents, and catastrophe volume with both engineers and business stakeholders.
  • Working experience integrating third-party property claims services, including EagleView, Hover, ITEL, and Nearmap or equivalent imagery, measurement, and materials-pricing vendors.

More Info

Job Type:
Industry:
Function:
Employment Type:

About Company