Jobs · Information Technology · California

Senior Staff Business Systems Analyst – Legal Technology

Intuit · San Diego, CA · 1 mo ago
On-siteInformation Technology$188k–$254k/yrFull-time
We need to output HTML fragment with sections: About the role? The overview is about role. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes Overview (which can be About the role). Responsibilities section present. Qualifications present. Pay info present. Benefits? It mentions "Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs". That's generic but still mentions benefits. Should we include Benefits? It says "competitive compensation package ... may be eligible for a cash bonus, equity rewards and benefits". That's somewhat generic but still mentions benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (cash bonus, equity rewards and benefits). So we can include Benefits section with that content. Schedule not mentioned, so omit. Skills? The qualifications include many skill items; we could put Skills section maybe but we have Qualifications covering. The instruction: Prefer a few substantive sections over many thin ones. We could combine Qualifications and Skills? But we have Qualifications already. Could also include Skills as separate but might be thin. Better to have About the role, Responsibilities, Qualifications, Pay, Benefits. Possibly also Requirements? The posting includes "Qualifications" but not separate Requirements. Could treat Qualifications as Requirements. We'll follow headings: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. The posting includes some boilerplate like "Intuit provides a competitive compensation package..." that's not boilerplate but part of benefits. Also includes "Pay offered is based on factors such as job-related knowledge..." and "Expected Base Pay Range...". Keep that. We need to ensure we don't repeat job title as heading. Not include Job ID. Let's extract content. Overview paragraph: "The Intuit FLP (Finance, Legal, and Privacy) Tech team builds Intuit’s core capabilities across enterprise finance, legal, and privacy applications. Our stakeholders include Intuit’s finance team, the Legal, Compliance, and Policy Organization (LCPO), segment business unit leaders, and all Intuit employees. As Intuit consolidates and standardizes backend processes onto common capabilities, we evaluate every solution through a rigorous Build vs. Buy lens. LCPO is in the middle of the most significant technology transformation — consolidating a fragmented estate onto a modern service delivery platform, building a knowledge and data spine underneath it, and moving from AI-assisted professionals toward agentic orchestration of legal work. FLP Tech is hiring a Staff Business Systems Analyst for Legal Technology to own that transformation end to end. This is not a requirements-taking role. You will own the Legal Technology portfolio and roadmap: partnering with LCPO Solutions & Strategy and the legal practice groups to envision where legal technology should go over the next two to three years, converting that vision into a prioritized, sequenced roadmap, and working with FLP Tech engineering and cross-functional technology teams across Intuit to deliver it. The role sits deliberately at the intersection of product management and business systems analysis. You will be as comfortable defending a multi-year platform strategy to senior leaders as you are writing the acceptance criteria for a single intake workflow. You are accountable for the outcome, not the artifact — if the workflow ships and nobody adopts it, that is your problem to solve." That's About the role. Responsibilities: list bullet points from "Vision, Portfolio & Roadmap." etc. We need to capture each bullet. Let's parse responsibilities section: "Vision, Portfolio & Roadmap. Define and own the multi-year Legal Technology roadmap and the single authoritative view of Legal Tech investment — initiatives, sequencing, dependencies, capacity, and status. Run the operating rhythm that keeps it honest: portfolio and roadmap reviews with LCPO and FLP Tech leadership, and clear escalation with recommended paths when something is off track.Stakeholder Partnership & Requirements. Act as the primary partner to Legal Practice Groups (Privacy, Corporate Affairs, Litigations, Regulatory, Compliance & Risk, etc.) to gather requirements, conduct user research, and translate insights into technical requirements. .Unified Orchestration. Own the roadmap for the unified legal front door — omni-channel intake from Slack, email, Jira and web, smart triage and routing, SLA management and status transparency — and the migration of legacy workflows onto the target platform without losing capability, integrations or audit history.Build vs. Buy Governance. Apply an 80% configure / 20% build lens across the LCPO estate. Run structured vendor evaluations end to end — scoring rubrics, demos, proofs of concept, reference checks, security and privacy review, total cost of ownership — build the business case, drive it to a decision with senior stakeholders, and own the implementation you recommended.Solution Design & Integration. Lead fit-gap analysis and design the integrations that connect the service delivery layer with CLM, eDiscovery, matter management and outside counsel billing, procurement, identity, and the enterprise data platform. You do not need to write production code, but you must understand APIs, data models and authentication well enough to design realistic solutions and call out unrealistic ones.AI Innovation & Prototyping. Build prototypes and run pilots for Generative AI, knowledge management and agentic workflows that eliminate repetitive legal work and institutionalize legal expertise. Critically evaluate AI capabilities inside vendor platforms, and define where human-in-the-loop oversight, evaluation and audit controls belong.Data & Measurement. Establish a baseline and a target for every initiative before work begins. Partner with data engineering and analytics to build the reporting that shows portfolio health, adoption, cycle time and toil reduction — and use that data to reprioritize.Delivery, Adoption & Craft Leadership. Drive end-to-end delivery with FLP Tech engineering and architecture, and with systems integrators where they are engaged — helping shape the statement of work and holding delivery to it. As a Staff-level individual contributor, set the craft standard for requirements, solution design and business cases across the Legal Tech team, including contingent workers and partner teams." We need to turn each into

  • items. Could group under
      . Qualifications: list bullet points from "Qualifications". Let's extract. "Qualifications 10+ years delivering enterprise software products or business systems solutions as a business systems analyst, technical product manager, or solution owner — including meaningful time supporting a legal, compliance, finance or other regulated business function.Portfolio & Roadmap Ownership: You have built and executed a multi-year roadmap balancing new capability, platform health and run-the-business demand, and can show how you made prioritization trade-offs and defended them.Business Analysis Craft: Requirements elicitation, process mapping and redesign, use case and user story writing, data mapping, test strategy and UAT. You write specifications that engineers and non-technical stakeholders can both act on without losing fidelity.Legal Domain Expertise: Familiarity with legal workflows — matter intake and triage, Contract Lifecycle Management, eDiscovery and legal holds, regulatory monitoring, outside counsel management and accruals, intellectual property, marketing compliance, and privacy operations. Legal Tech Stack Expertise Orchestration / Low-Code: ServiceNow, Tonkean, Workato or similar — with hands-on configuration experience, not just oversight.Legal-Specific Tools: Ironclad, Legal Tracker, Exterro, or comparable CLM, matter management and eDiscovery platforms.Data & Analytics: data lake (e.g.AWS, GCP) and BI solutions (e.g.Databricks, Qlik, Tableau).Emerging Legal AI: Harvey, Hebbia, Eudia or similar, and the evaluation judgment to separate capability from demo. Staff-Level Craft Technical Acumen: strong understanding of API strategies, integration patterns, identity and access, and AI/ML workflows with human-in-the-loop design.Analytical Thinking: uses data to find the bottleneck and proposes the scalable, automated fix.Decision Ownership: sets the evaluation criteria, makes the technology call, and owns the consequences.AI Fluency: an active, critical user of AI tools (Claude, Gemini, ChatGPT) in your own delivery work, with a clear view of where AI creates leverage and where it does not. Soft Skills & Leadership Master Translator: bridges legal counsel and engineering without losing fidelity in either direction, and communicates complex trade-offs to senior executives through compelling narrative.Ambiguity Navigator: thrives on a blank slate; creates the roadmap where none exists.Influence Without Authority: builds trust quickly across Legal, Engineering, Architecture, Security, Privacy and Procurement, and moves decisions forward when nobody in the room reports to you.Education: BS in Computer Science, Information Systems, Business or equivalent work experience is preferred. A background in Legal Operations is a significant plus." We need to turn each into
    • . Could group similar. Pay: "Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs (see more about our compensation and benefits at Intuit®: Careers | Benefits). Pay offered is based on factors such as job-related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender. The Expected Base Pay Range For This Position Is Mountain View $187,500 - $253,500 San Diego, CA $172,500- $233,000" We need to keep that as prose maybe with

      . Could also list ranges as

        but it's fine as prose. Benefits: The sentence about cash bonus, equity rewards and benefits. Could be included in Benefits section. We should not duplicate. Perhaps Benefits section includes that sentence. Let's craft HTML. Structure:

        About the role

        ...overview text...

        Responsibilities

        • Define and own the multi-year Legal Technology roadmap and the single authoritative view of Legal Tech investment — initiatives, sequencing, dependencies, capacity, and status. Run the operating rhythm that keeps it honest: portfolio and roadmap reviews with LCPO and FLP Tech leadership, and clear escalation with recommended paths when something is off track.
        • Act as the primary partner to Legal Practice Groups (Privacy, Corporate Affairs, Litigations, Regulatory, Compliance & Risk, etc.) to gather requirements, conduct user research, and translate insights into technical requirements.
        • Own the roadmap for the unified legal front door — omni-channel intake from Slack, email, Jira and web, smart triage and routing, SLA management and status transparency — and the migration of legacy workflows onto the target platform without losing capability, integrations or audit history.
        • Apply an 80% configure / 20% build lens across the LCPO estate. Run structured vendor evaluations end to end — scoring rubrics, demos, proofs of concept, reference checks, security and privacy review, total cost of ownership — build the business case, drive it to a decision with senior stakeholders, and own the implementation you recommended.
        • Lead fit-gap analysis and design the integrations that connect the service delivery layer with CLM, eDiscovery, matter management and outside counsel billing, procurement, identity, and the enterprise data platform. You do not need to write production code, but you must understand APIs, data models and authentication well enough to design realistic solutions and call out unrealistic ones.
        • Build prototypes and run pilots for Generative AI, knowledge management and agentic workflows that eliminate repetitive legal work and institutionalize legal expertise. Critically evaluate AI capabilities inside vendor platforms, and define where human-in-the-loop oversight, evaluation

Similar jobs