Technical Support Lead (Senior Staff Engineer)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented. Remove boilerplate. We need to parse the posting. Key parts: - Intro description about Crux AI (company description). Could be "About the role"? Actually "About Crux" is a section later. The posting includes "What You'll Do", "In This Role, You Will", "Key Responsibilities", "SIGNALS OF SUCCESS", "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH", "Nice To Have (Preferred, Not Required)", "Salary Range Information", "About Crux" (benefits etc). Also "Salary Range Information" is vague (no actual numbers). It says "The annual salary range for this position has been estimated based on market data and other factors. However, a salary higher or lower than this range may be appropriate..." No actual numbers given, so we should NOT create a Pay section because no specific salary range. Similarly schedule: they mention "Hybrid schedule offering four days in-office collaboration paired with one remote workday for focused, individual work" under About Crux. That's schedule info. So we can include a Schedule section. Benefits: Under About Crux: "We offer generous base, bonus and additional incentive based compensation Health, dental, and vision coverage for you and your dependents Company-paid life insurance and disability Full suite of other optional benefits 401(k) Plan with 4% company match". That's benefits. So we can include Benefits section. Responsibilities: The "Key Responsibilities" bullet list. Also "What You'll Do" and "In This Role, You Will" maybe overlapping. We should combine into Responsibilities section with list items. Requirements/Qualifications: The "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" includes required experiences (12+ years etc). Also attributes and mindset. Could be Requirements section. Also "Nice To Have" could be Qualifications or Skills? Usually Nice To Have is separate but we can include as Qualifications or Skills? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: maybe a brief description of role? Could be from "What You'll Do" etc. But we already have Responsibilities. Could put About the role as a short paragraph summarizing role. But we must not repeat job title. We can include a short paragraph about the role: "Founding Technical Support Lead (Senior Staff Engineer) responsible for establishing technical support posture..." etc. That is substantive. - Responsibilities: list of duties. - Requirements: required experience (12+ years, hyperscale triage depth, Direct-to-Expert leadership experience, Senior technical leadership scope). Also attributes like Customer-Centric Outcome Orientation, Discipline Over Heroics, Builder Mindset & Ambiguity, AI-Agentic First. Those could be under Requirements or maybe Skills. But we can put them under Requirements. - Qualifications: maybe the Nice To Have (Preferred, Not Required) items. - Skills: maybe specific skills like TPU support, SLA mechanics, support tooling budget ownership? Those are Nice To Have. Could go under Skills. But we need to avoid thin sections. Let's decide: - About the role: short paragraph summarizing role. - Responsibilities: bullet list from Key Responsibilities plus maybe some from What You'll Do. - Requirements: bullet list of required experiences and attributes (12+ years, hyperscale triage depth, Direct-to-Expert leadership experience, Senior technical leadership scope, Customer-Centric Outcome Orientation, Discipline Over Heroics, Builder Mindset & Ambiguity, AI-Agentic First). Also maybe mention reporting to CTO etc? That's more role. - Qualifications: maybe the Nice To Have items (Hyperscaler/Neocloud leadership, Direct TPU/Frontier silicon support, Contractual SLA mechanics, Support tooling & budget ownership). Could be under Qualifications. - Skills: maybe not needed if we covered. Could combine Qualifications and Skills? But we need to follow instruction: we can include sections only if real specific content. We have content for About the role, Responsibilities, Requirements, Qualifications (Nice To Have), Benefits, Schedule. Pay: no specific numbers, so omit. Skills: maybe we could put specific technical skills under Skills (like TPU, SLA, support tooling). But those are already in Nice To Have. Could move them to Skills and keep Qualifications for experiences? Hmm. Better: Use Requirements for mandatory experience/attributes. Use Qualifications for Nice To Have (preferred). Use Skills maybe not needed; we could omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Now we need to extract exact phrasing, preserve all substantive info, not invent. Let's gather text. About the role: Could be from "What You'll Do" and "In This Role, You Will". We'll write a paragraph summarizing: "Founding Technical Support Lead (Senior Staff Engineer) in Palo Alto, CA, reporting to CTO, responsible for establishing company-wide customer technical support posture, case management architecture, and support technology stack from zero; owning technical support doctrine, customer status communications during degradations, case escalation paths, and customer technical experience during critical issues; operating Direct-to-Expert support model; building, managing, leading global technical support organization; handling first complex case escalations, triaging cluster issues alongside SRE, building support runbooks and status workflows; scaling 24x7 support operations; embedding AI-agentic first support; aligning with SLAs and executive reporting." That's a summary but we must not invent; we need to preserve original phrasing as much as possible. Better to copy relevant sentences directly. Let's extract sentences: From "What You'll Do": "Crux AI is seeking a founding Technical Support Lead (Senior Staff Engineer) in Palo Alto, California to establish and own our company-wide customer technical support posture, case management architecture, and support technology stack from zero. Reporting directly to the Chief Technical Officer (CTO), you will sit on the technical leadership team alongside the leads for Network Engineering, Hardware Operations, and Software/SRE. Serving as the primary connective tissue between our enterprise customers and backend engineering, you own the technical support doctrine, customer status communications during degradations, case escalation paths, and customer technical experience during critical issues. We operate on a Direct-to-Expert support model. Rather than routing customers through generic support tiers, your team connects enterprise AI labs directly with senior technical support engineers who stay accountable for issue resolution end-to-end." From "In This Role, You Will": "In this role, you will be responsible for building, managing, and leading the global technical support organization. However, this is a true hands-on, builder seat, not a supervisory position early on. In the initial phase, you will handle the first complex case escalations, triage cluster issues alongside SRE, and build the support runbooks and status workflows yourself before building out your team of engineers and managers. You must revel in ambiguity, act with high autonomy, and maintain a strict 'discipline over heroics' mindset, building automated support systems and 24x7 coverage that make handling the next customer escalation routine." We can combine these as About the role paragraph(s). Use

for prose. Now Responsibilities: list from "Key Responsibilities". Let's copy each bullet as

. The text: "Define Direct-to-Expert Case Architecture: Design, roll out, and govern the company-wide case triage framework, Direct-to-Expert ownership model led by senior technical support engineers, escalation boundaries, and severity definitions across Support, SRE, Network Engineering, and Google Support. Proactive Account Technical Management (TAM) & Onboarding: Provide proactive technical guidance for strategic enterprise accounts during initial cluster bring-up, model training spin-ups, job placement, and checkpointing strategies to prevent issues before they occur. Connective Tissue to Product & Engineering: Systematically aggregate ticket analytics, case trends, and postmortem findings to feed prioritized product bug fixes and platform feature requests directly to SRE, Network Engineering, and Product teams. Own Customer Status Communications & Support Stack: Own company status page messaging, incident notification channels, and customer-facing status updates during cluster degradations, while governing the selection and deployment of the support ticketing technology stack. Build & Scale 24x7 Support Operations: Recruit, structure, and manage a high-bar technical support engineering organization capable of delivering robust 24x7 operational coverage, establishing shift leads and escalation tiers as fleet capacity ramps. Embed AI-Agentic First Support: Deploy AI agents and LLM-driven diagnostic workflows as first principles across case triage, log parsing, root-cause analysis, and customer updates before scaling headcount. Customer SLA Alignment & Executive Reporting: Partner with Sales, Legal, SRE, and Product to ensure support workflows strictly align with contractual customer SLAs, delivering monthly executive reporting on case resolution velocity, friction trends, and customer health." We'll output each as

. Now Requirements: from "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH". The required experiences: - "12+ Years Experience: 12+ years in technical support, TAC, or customer-facing infrastructure/SRE operations for large-scale compute/cloud environments, including 6+ years managing technical support engineering teams and leaders." - "Deep Hyperscale Triage Depth: Hands-on ability to triage and resolve complex customer issues across high complexity large scale environments by analyzing logs, alerts, and telemetry data, through grounding in an architectural understanding of complex systems that extends far beyond executing static playbooks." - "Direct-to-Expert Leadership Experience: Track record building or operating high-touch support organizations for complex enterprise infrastructure, moving away from generic multi-tier queues toward direct-ownership models anchored by senior technical support engineers." - "Senior Technical Leadership Scope: Proven track record building a technical support function from scratch, operating as a peer to senior engineering directors, and presenting customer health metrics to executive teams." Attributes: - "Customer-Centric Outcome Orientation: Treats the customer’s workload execution as the sole definition of success, recognizing that a case marked 'resolved' while a customer's multi-thousand-node training job is still stalled is not resolved." - "Discipline Over Heroics: Rejects 'heroic all-nighters' in favor of systematic postmortems, automated runbooks, and robust escalation architectures." - "Mindset Builder Mindset & Ambiguity: High tolerance for ambiguity; comfortable operating as a hands-on lead early on, establishing order amidst rapid fleet growth, and designing scalable 24x7 organizational systems." - "AI-Agentic First: Active utilization of AI agents and automated diagnostic tools in technical operations, defaulting to agentic workflows over manual process." We'll list each as

under Requirements. Now Qualifications (Nice To Have): list: - "Hyperscaler / Neocloud Leadership: Technical support or TAC leadership at a hyperscaler (Google, AWS, Meta, Microsoft) or leading neocloud (CoreWeave, Lambda, Nebius, Nscale) during rapid customer growth." - "Direct TPU / Frontier Silicon Support: Direct experience supporting Google TPU clusters or large-scale GPU accelerator pods in production." - "Contractual SLA Mechanics: Familiarity with customer SLA terms, support tiering, maintenance windows, and service credit mechanics in enterprise cloud contracts." - "Support Tooling & Budget Ownership: Financial accountability for support platforms (Zendesk/ServiceNow/custom), status page tooling, vendor contracts, and global 24x7 shift coverage." We'll list as

under Qualifications. Now Benefits: from About Crux: "We offer generous base, bonus and additional incentive based compensation Health, dental, and vision coverage for you and your dependents Company