Technical Architect

Role:Technical Architect
Experience: 16+ years, including 4+ years in an architect-level role on Java/cloud-native platforms
The Technical Architect owns end-to-end architecture for the scalable, secure, Java-based and AI-enabled RTR platform, including the multi-agent pipeline invoked via AWS Bedrock. This role bridges business, product, data science, and engineering, and is accountable for the platform's architecture, security, and delivery quality end to end.
Location: Noida
Package: 40 LPA max
Notice period: 15-30days
ResponsibilitiesArchitecture & Design
● Own end-to-end architecture for the Java-based, AI-enabled RTR platform, including the 5-agent Bedrock pipeline (Extraction, Enrichment, Validation, Anomaly Detection, Posting).
● Define reference architectures, design standards, and best practices.
● Design scalable solutions using microservices, APIs, event-driven architecture, and cloud-native patterns.
● Ensure architecture aligns with enterprise NFRs (scalability, availability, security, performance).
● Evaluate and recommend AI/ML integration approaches (LLM invocation via AWS Bedrock, model ARN versioning, token and cost governance).
Implementation Leadership
● Lead hands-on implementation and guide engineering teams through complex technical decisions.
● Review and approve low-level designs, code architecture, and integration patterns.
● Mentor senior engineers and technical leads; drive CI/CD, DevSecOps, and automation best practices.
● Troubleshoot and resolve complex production issues and performance bottlenecks.
AI, Security & Stakeholder Collaboration
● Enable AI-led capabilities responsibly — data privacy, bias mitigation, and compliance.
● Embed security-by-design principles across the platform.
● Work closely with Product Owners, Business Leaders, and Enterprise Architects.
Minimum QualificationsCore Technologies
● Strong, hands-on Java (11+/17): Spring Boot, Spring Cloud, RESTful APIs, JSON, OpenAPI/Swagger, microservices — deep coding ability expected, not just design-level familiarity.
● Strong, hands-on Python: FastAPI, Pandas, Boto3, async/await, GenAI/Bedrock service integration — this role is expected to be genuinely fluent in both Java and Python, not just one.
● AWS platform fundamentals as a primary requirement: IAM, EC2, RDS, S3, CloudWatch, Secrets Manager, VPC, in addition to AWS Bedrock (Claude) invocation — IAM role scoping, model ARN management, token budgeting, guardrails, and RAG/vector-database patterns.
● Containers: Docker; Kubernetes for orchestration.
● Cloud platform requirement: AWS is the primary and required cloud platform for this role. Azure is not required for this role — Azure is scoped to the DevOps Engineer role only. GCP familiarity is optional / a nice-to-have, never mandatory.
● SAP S/4HANA API integration (BAPI/OData/RFC) /Workday/Oracle for the ERP posting layer.
● CI/CD (Jenkins/GitHub Actions/Azure Code Pipeline or equivalent), IaC (Terraform/CloudFormation), observability, and performance tuning.
Event-driven architecture (Kafka/RabbitMQ); MLOps; Amazon RDS PostgreSQL; externalized rules engines (Drools).
● OKTA / SSO and OAuth2 architecture; Amazon ECR/EC2 deployment pipelines.
● Optional, not required: Azure or GCP exposure. This role's required cloud platform is AWS.

Work arrangement
No