- Technical Lead Architect, technical decision-maker, and connective tissue of the CoLab Seniority Senior / Staff-level engineer stepping into a lead role Experience 10+ years in software engineering; 3+ years leading teams or owning architecture Tenure signal 2–4+ years of average tenure per role — enough to have owned systems end-to-end, not just shipped features Focus areas Agentic AI, knowledge graphs, oData APIs, solution architecture Engagement Hands-on lead — expected to code, review, and set technical direction
PROFILE SUMMARY A pragmatic senior/staff engineer who can architect end-to-end solutions and act as the technical anchor of the pod. They combine strong exposure to Octave products (or the proven ability to ramp on a new, evolving product quickly) with real depth in agentic AI. Just as importantly, they are the bridge between SMEs, engineers, and front-end developers — translating domain needs into technical design and keeping the CoLab moving in an agile rhythm. MUST-HAVE SKILLS & EXPERIENCE • Solution architecture: demonstrated experience architecting non-trivial systems end-to-end — making and defending trade-offs across data, services, APIs, and delivery. • Agentic AI: hands-on experience designing and building agentic AI systems — orchestration, tool use, multi-agent or single-agent patterns, evaluation, and guardrails. • Knowledge graphs: practical experience modeling, building, or querying knowledge graphs (e.g., ontology/schema design, graph databases, semantic layers) and connecting them to applications. • oData APIs: experience designing and/or integrating oData APIs — query semantics, entity modeling, and consuming/exposing oData services. • Product & agile fluency: strong exposure to Octave products, or a clear track record of ramping quickly on new products; comfortable operating in agile delivery and shaping backlog with the team. • Bridging role: proven ability to act as the connective link between different roles — SMEs, data/agent engineers, and front-end — aligning them around a shared technical vision. NICE-TO-HAVE / DIFFERENTIATORS • Domain understanding: familiarity with the customer/business domain the CoLab serves, enough to challenge and refine requirements. • Platform breadth: cloud architecture, event-driven design, or data-platform experience that complements the agentic work. • Mentorship: history of raising the bar for engineers around them through review, pairing, and design leadership. WHAT THEY'LL DO IN THE COLAB • Translate SME and customer needs into concrete technical designs, and translate technical constraints back into terms the rest of the pod understands. • Set standards for agentic flows, knowledge-graph usage, and API integration, and keep the team aligned to them. • Stay hands-on — prototype the hard parts, review critical code, and unblock engineers. TYPICAL BACKGROUND Typically a senior or staff engineer from a product-focused or platform team who has grown into architecture and technical leadership. Often has shipped AI/ML-enabled products, has worked close to data (graphs, APIs, integrations), and is used to being the person a cross-functional team turns to for the “how.” SIGNALS OF A STRONG FIT • Can whiteboard an agentic solution and its data model in a first conversation. • Talks about trade-offs and failure modes • Comfortable being the translator in a room of specialists.