• The Technical Team Lead – Managed Services (Public Cloud) serves as a strategic technical leader, trusted advisor, and subject matter expert across Public Cloud technologies, Platform Engineering, DevOps, Automation, and Cloud Operations. • Responsible for leading the design, implementation, support, and continuous improvement of enterprise-grade cloud solutions while driving operational excellence and ensuring exceptional customer outcomes. • Provides both technical and people leadership, overseeing a team of cloud engineers responsible for delivering managed services across multi-cloud environments. • Acts as the primary escalation point for complex technical issues, ensuring rapid resolution of critical incidents while maintaining service availability, reliability, security, and performance. • Collaborates closely with customers, executive stakeholders, architects, engineering teams, project managers, and business leaders to align technology initiatives with organizational objectives. • Drives the adoption of cloud-native architectures, Infrastructure as Code (IaC), automation frameworks, DevOps and DevSecOps practices, FinOps principles, and operational best practices to improve efficiency, scalability, and business value.

• AI orchestration as a core skill: You think in agent pipelines rather than individual prompts. • You orchestrate Claude Code (and similar agentic frameworks) so that multiple agents work in parallel on features, refactorings, and tests, and you evaluate, curate, and correct their outputs deliberately. • Maximize product landscape optimization: You identify where the existing codebase (Java backend, JavaScript frontend) can be made faster, more robust, and more maintainable through AI-assisted new development and enhancements, and you implement these changes autonomously. • Architecture & quality control: You understand, validate, and safely integrate AI-generated code into existing architectures. • You define the guardrails (tests, reviews, best practices) that turn agent output into reliable software. • Technical conception within the core team: You develop new ideas and technologies for backend and frontend together with the core team and introduce AI workflows into the entire development process. • Performance & scaling: You design and implement measures for quality assurance and performance optimization. • Technical sparring partner: As a last-level support and point of contact for product owners and sales, you translate between business requirements and technical solutions.

• Own and evolve Feeld’s **React Native/mobile architecture**, setting patterns that scale across iOS and Android. • Drive **performance and quality** (rendering, startup, networking, offline/edge behavior, app size, cross‑platform parity). • Lead technical discovery and delivery for platform initiatives that unlock product teams (e.g., shared UI foundations, app infrastructure, build tooling). • Partner with Product and Design to translate goals into resilient technical plans, and help teams make good trade-offs. • Improve production ownership: instrumentation, alerting, dashboards, runbooks, and reliable release practices. • Act as a Staff-level IC leader: raise the bar through reviews, pairing, mentorship, and pragmatic decision making across the FE community.

• Own reliability outcomes across critical backend services and their integration with mobile clients (React Native). • Lead technical problem-solving during incidents: coordinate response, diagnose root causes, communicate status, and drive to resolution. • Build and evolve monitoring/observability (dashboards, alerts, tracing, logging) that enables fast detection and diagnosis. • Drive post‑incident reviews (blameless) and ensure learnings become durable fixes (tech changes, runbooks, automation, process updates). • Improve engineering safety and quality: guardrails, safer migrations, feature-flag practices, rollout strategies, and resilience patterns. • Partner with product, design, QA, and engineering early to align delivery plans with operational risk and reliability needs. • Strengthen documentation and onboarding: architecture notes, runbooks, service ownership docs, and “how we work” guides. • Mentor engineers through pairing, reviews, incident shadowing, and pragmatic coaching on production ownership.