The preferred technical background may vary depending on product group assignment, but the following experience will be helpful:
- Strong experience with .NET / C#, SQL Server, APIs, integrations, and enterprise business applications.
- Experience with PHP applications, JavaScript / TypeScript, web application frameworks, and legacy modernization.
- Experience with mobile application architecture, Android / iOS development, warehouse applications, or field operations systems.
- Familiarity with NLP, computer vision, AI / ML workflows, data labeling, model evaluation, or AI-assisted business tools.
- Experience with cloud platforms such as Azure, AWS, or GCP.
- Familiarity with event-driven architecture, message queues, enterprise integration patterns, API gateways, or data pipelines.
- Experience with ERP integrations, NetSuite, finance systems, sales / purchasing workflows, warehouse workflows, or B2B transaction platforms.
- Understanding of security-by-design principles and practical application security concerns.
- Experience in electronic components, technology distribution, supply chain, logistics, manufacturing, e-commerce, or similar B2B environments.
- Experience using Azure DevOps, Jira, Git, CI/CD tooling, and technical documentation systems.
Success in the First 90 Days
Within the first 90 days, the Product Group Team Lead / Architect should be able to:
- Understand the assigned product group, users, business workflows, technical architecture, codebase, data flows, integrations, and production risks.
- Establish working relationships with Engineering Managers, Product / Delivery Managers, engineers, QA, DevOps, DBA, Infrastructure, Security, and business stakeholders.
- Identify the most important technical risks, technical debt items, single points of failure, and maintainability concerns in the assigned product group.
- Define or improve technical ownership boundaries for the assigned systems.
- Improve technical clarity of the active backlog by helping with design notes, technical breakdown, dependencies, estimates, and risks.
- Establish practical code review, design review, documentation, and release readiness expectations for the assigned product group.
- Lead at least one meaningful technical improvement, stabilization effort, or risk-reduction activity.
- Improve L3 technical escalation and production issue investigation for assigned systems.
- Create an initial technical roadmap or remediation plan aligned with product priorities and engineering capacity.
- Help onboard or mentor engineers working in the assigned product group.
What This Role Does Not Own
This role does not own formal people management for engineers. Engineering Managers remain responsible for hiring, performance management, compensation input, team structure, and capacity planning.
This role does not own business prioritization or user acceptance. Product / Delivery Managers and business stakeholders remain responsible for intake, priority alignment, backlog readiness, UAT coordination, and business acceptance.
This role does not independently commit delivery dates without alignment with Engineering Managers and Product / Delivery Managers.
This role does not act as a central enterprise architect for all Sourceability systems unless specifically assigned by GEO leadership. The primary responsibility is technical ownership of the assigned product group or platform area.