• Design, build, test, deploy, and maintain highly scalable backend services using Go. • Own critical services supporting Package Protection, Returns Protection, Claims, Orders, Tracking, and Email Parsing. • Design and evolve distributed systems and event-driven architectures that process high volumes of transactions reliably. • Build and maintain REST and GraphQL APIs used by internal products, merchants, and external partners. • Develop and improve integrations with merchant platforms, carriers, and third-party APIs. • Optimize system performance, reliability, scalability, and observability across production services. • Collaborate closely with Product Managers, Engineers, and cross-functional stakeholders to deliver impactful solutions. • Mentor engineers through technical leadership, design reviews, and knowledge sharing. • Participate in architectural decisions and continuously improve engineering standards and operational excellence.

• Act as the architecture authority – own the deterministic/AI boundary design, multi-tenant data isolation model, and LLM security posture; baseline architectural decisions in week 1 that lock the team's constraints • Technical owner from design to delivery – tailor solutions to Alpine's stated requirements (FastAPI + PostgreSQL + AWS Bedrock + ECS Fargate) while defending against scope creep and technical debt • Partner with stakeholders to capture requirements – work with client leadership to translate business and compliance needs into architectural constraints (e.g., multi-tenant isolation, run-to-run consistency guarantees, audit trails) • Assess and plan for technology insertion – evaluate architectural trade-offs (e.g., why a single bounded AI step beats two, why RLS + FORCE ROW LEVEL SECURITY beats application-layer filtering, why Pydantic schema validation is the output gate) • Manage risk identification and mitigation – surface and mitigate delivery risks (e.g., CISO golden-set availability, prompt-injection surface area, cross-tenant isolation defects) with concrete mitigation strategies • Influence and communicate vision – define the long-term product roadmap (Tools 1–5), technical vision (the 5-section Source of Truth structure, the 7-stage pipeline design), and development strategy (agentic-orchestration approach, vertical slices, always-functional milestones) • Contribute to code reviews and architectural artifacts – review critical paths (Bedrock adapter, RLS policies, Stage 4 calibration logic); document architectural decision records (ADRs) that capture the why, not just the what • Lead and mentor the team – guide the AI/LLM Lead and Backend engineers on AI reliability, security patterns, and multi-tenant design; escalate ambiguity upward rather than letting it flow down to individual engineers

• Act as the architecture authority – own the deterministic/AI boundary design, multi-tenant data isolation model, and LLM security posture; baseline architectural decisions in week 1 that lock the team's constraints • Technical owner from design to delivery – tailor solutions to Alpine's stated requirements (FastAPI + PostgreSQL + AWS Bedrock + ECS Fargate) while defending against scope creep and technical debt • Partner with stakeholders to capture requirements – work with client leadership to translate business and compliance needs into architectural constraints (e.g., multi-tenant isolation, run-to-run consistency guarantees, audit trails) • Assess and plan for technology insertion – evaluate architectural trade-offs (e.g., why a single bounded AI step beats two, why RLS + FORCE ROW LEVEL SECURITY beats application-layer filtering, why Pydantic schema validation is the output gate) • Manage risk identification and mitigation – surface and mitigate delivery risks (e.g., CISO golden-set availability, prompt-injection surface area, cross-tenant isolation defects) with concrete mitigation strategies • Influence and communicate vision – define the long-term product roadmap (Tools 1–5), technical vision (the 5-section Source of Truth structure, the 7-stage pipeline design), and development strategy (agentic-orchestration approach, vertical slices, always-functional milestones) • Contribute to code reviews and architectural artifacts – review critical paths (Bedrock adapter, RLS policies, Stage 4 calibration logic); document architectural decision records (ADRs) that capture the why, not just the what • Lead and mentor the team – guide the AI/LLM Lead and Backend engineers on AI reliability, security patterns, and multi-tenant design; escalate ambiguity upward rather than letting it flow down to individual engineers

• Act as the architecture authority – own the deterministic/AI boundary design, multi-tenant data isolation model, and LLM security posture; baseline architectural decisions in week 1 that lock the team's constraints • Technical owner from design to delivery – tailor solutions to Alpine's stated requirements (FastAPI + PostgreSQL + AWS Bedrock + ECS Fargate) while defending against scope creep and technical debt • Partner with stakeholders to capture requirements – work with client leadership to translate business and compliance needs into architectural constraints (e.g., multi-tenant isolation, run-to-run consistency guarantees, audit trails) • Assess and plan for technology insertion – evaluate architectural trade-offs (e.g., why a single bounded AI step beats two, why RLS + FORCE ROW LEVEL SECURITY beats application-layer filtering, why Pydantic schema validation is the output gate) • Manage risk identification and mitigation – surface and mitigate delivery risks (e.g., CISO golden-set availability, prompt-injection surface area, cross-tenant isolation defects) with concrete mitigation strategies • Influence and communicate vision – define the long-term product roadmap (Tools 1–5), technical vision (the 5-section Source of Truth structure, the 7-stage pipeline design), and development strategy (agentic-orchestration approach, vertical slices, always-functional milestones) • Contribute to code reviews and architectural artifacts – review critical paths (Bedrock adapter, RLS policies, Stage 4 calibration logic); document architectural decision records (ADRs) that capture the why, not just the what • Lead and mentor the team – guide the AI/LLM Lead and Backend engineers on AI reliability, security patterns, and multi-tenant design; escalate ambiguity upward rather than letting it flow down to individual engineers