Senior Data Application Engineer

We need to output HTML fragment with sections: About the role (maybe "About Cooley AI"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only if posting has real specific content. We have content: About Cooley AI (description). Position summary. Responsibilities (multiple bullet points). Required Skills and experience (list). Preferred qualifications (list). Competencies (list). Benefits (description). Pay (range). Schedule? Not mentioned explicitly; maybe full-time schedule implied but not specific. We should not create Schedule section unless posting actually states them. It says "full-time schedule" but not details. Might consider that as schedule info? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay range and benefits. So we can include Pay and Benefits sections. Schedule: not specific beyond full-time; maybe we can omit Schedule section. We must not repeat job title as heading. Do not put Job ID etc. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO, EOE, etc. Also remove application instructions, cookie/navigation/legal etc. The posting includes "Cooley LLP offers a competitive compensation and excellent benefits program. EOE." That's boilerplate; we should remove EOE line. Also "Please note that final offer amount will be dependent on geographic location, applicable experience and skillset of the candidate." That's part of pay description; we keep that as part of Pay section. Also "Senior level candidates may be considered for this position and would be eligible for a higher salary range based on experience." Keep. We need to include About Cooley AI description: "Cooley AI is the wholly-owned subsidiary of Cooley LLP. The frontier development arm of the leading technology law firm in the world. Our mission is to bring the best-in-class practices from the technology field into the legal domain to help lead our firm and the legal industry into the AI era. All employees of Cooley AI are employees of Cooley and are seconded to Cooley AI." That's about the company; could be under About the role? Probably "About Cooley AI" but heading "About the role" is suggested. However we can use "About Cooley AI" as heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict; we should follow those headings. So we should have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Preferred" could be under Qualifications or Skills. But we need to decide. We have content: Position summary (could be part of About the role). Responsibilities (list). Required Skills and experience (list). Preferred (list). Competencies (list). Benefits (description). Pay (range). We could map: - About the role: includes position summary and maybe About Cooley AI description. - Responsibilities: bullet list. - Requirements: maybe Required Skills and experience. - Qualifications: maybe Preferred qualifications. - Skills: maybe Competencies? Or we could combine. But we need to avoid thin sections. Let's think: We have several lists: Responsibilities, Required Skills and experience, Preferred qualifications, Competencies. Benefits and Pay are prose. We could create sections: About the role (prose), Responsibilities (ul), Requirements (ul) for required skills, Qualifications (ul) for preferred, Skills (ul) for competencies, Benefits (ul?) Actually benefits are prose list of benefits; we could use

  • for each benefit item. Pay:

    with range and notes. We must not invent placeholder text. Ensure we include all substantive info. Let's extract details. About Cooley AI and mission: "Cooley AI is the wholly-owned subsidiary of Cooley LLP. The frontier development arm of the leading technology law firm in the world. Our mission is to bring the best-in-class practices from the technology field into the legal domain to help lead our firm and the legal industry into the AI era. All employees of Cooley AI are employees of Cooley and are seconded to Cooley AI." Position summary: "As a leading technology law firm, Cooley is determined to become a leader in the digital practice of law. We are committed to advancing the digital practice of law through modern data applications, automation, and Lakehouse‑native tooling. The Senior Data Application Engineer plays a foundational role in building and supporting interactive data applications on the firm’s Databricks platform, enabling users to access insights, workflows, and AI‑powered capabilities more efficiently. The Senior Data Application Engineer will work closely with product owners and architects to deliver intuitive, reliable, and secure data applications built using Databricks Appkit, AI‑assisted development tools, and GitHub‑based engineering practices." We can combine these into About the role prose. Responsibilities: list bullet points from "Position Responsibilities" section. Let's extract each bullet: - Data Application Development & Support: * Build and enhance interactive data applications using Databricks Appkit, AI‑assisted coding tools (e.g., Claude Code), and optional local development in VS Code, following GitHub‑based version control and pull‑request workflows * Implement UI components, data visualizations, and user‑facing features that integrate seamlessly with Databricks data sources and Lakehouse‑native APIs * Support the development of internal tools that streamline workflows, improve data accessibility, and enhance user experience across legal and business teams * Participate in code reviews, testing, and documentation to ensure application reliability, maintainability, and adherence to firm standards * Troubleshoot application issues, perform root‑cause analysis, and implement fixes under the guidance of senior engineers * Maintain and update content‑driven applications, ensuring accuracy, usability, and compliance with firm policies * Contribute to internal documentation, user guides, and knowledge bases for supported applications - Data Integration & Pipeline Support: * Assist senior engineers in building and maintaining ingestion, transformation, and integration workflows on the Databricks platform * Write SQL queries to retrieve, validate, and prepare data for use in data apps * Monitor data jobs and application integrations, escalating issues when needed * Support data quality efforts through validation checks, structured testing, and documentation updates * Learn foundational concepts of Lakehouse architecture, Delta Lake, and Databricks‑native development practice - Cross‑Functional Collaboration: * Work with Data Platform team members to understand data consumption patterns and ensure applications present information clearly and accurately * Collaborate with Product Owners to translate business requirements into actionable development tasks and user stories * Partner with Data Architects and platform teams to ensure applications align with governance, security, and architectural standards * Engage with Technology, Security, and Legal stakeholders to ensure applications meet firm compliance and access‑control requirements * Participate in Agile ceremonies (standups, sprint planning, retrospectives) and contribute to team delivery commitments * Communicate progress, blockers, and application updates to both technical and non‑technical stakeholders - AI, Automation & Innovation: * Use AI‑assisted development tools (e.g., Claude Code) to accelerate coding, documentation, and troubleshooting * Support the development of lightweight automation workflows using Databricks, low‑code/no‑code tools, or API‑based integrations * Assist in preparing structured content and data for AI‑driven tools, internal search experiences, and RAG‑style applications * Explore emerging Databricks capabilities and bring forward ideas for improving internal processes through automation or app development * Stay current on trends in web development, data applications, and AI‑assisted engineering * All other duties as assigned or required We need to keep all these bullet points. Required Skills and experience: list: - After orientation at Cooley LLP, exhibit proficiency in the Microsoft Office suite, iManage, and other firm applications - Ability to work extended and/or weekend hours, as required - Ability to travel, as required - 5+ years of experience directly applicable experience (e.g., data engineering, data application) - Experience with front‑end development (HTML, CSS, JavaScript) - Familiarity with React, Vue, Angular or other modern JavaScript frameworks - Basic SQL skills and understanding of relational databases - Experience building or maintaining web applications, websites, or content‑driven platforms - Familiarity with using GitHub for version control, branching, and pull requests Preferred qualifications list: - Bachelor’s degree in Computer Science, Data Science, or related discipline - Experience with Python or another scripting language - Exposure to Databricks, cloud platforms (Azure/AWS/GCP), or Lakehouse concepts - Familiarity with REST APIs, JSON, and basic integration patterns - Experience with VS Code or similar development environments - Experience related to data engineering, analytics, or application development - Experience with low‑code/no‑code automation tools - Understanding of UI/UX principles and accessibility best practices - Exposure to AI‑assisted development, RAG workflows, or data‑driven application design Competencies list (many bullet points). Let's extract: - Strong problem‑solving skills and willingness to learn new technologies - Ability to collaborate effectively with cross‑functional teams in an Agile environment - Strong attention to detail and commitment to producing high‑quality work - Excellent communication skills with the ability to explain technical concepts clearly - Highly organized with the ability to manage multiple tasks and deadlines - Collaborative team player with a positive, learning‑oriented mindset - Proactive problem solver who seeks opportunities to improve processes and tools - Ability to adapt to evolving technologies and business needs - Professionalism, discretion, and the ability to handle confidential information - Curiosity and enthusiasm for growing into a data engineering or application engineering career path - Ability to drive projects to completion and achieve goals - Strong judgment - Team-player with collaborative spirit - Unwavering ability to handle and maintain confidentiality regarding firm information, projects, client data - Proactive, analytical mindset - Effective presentation skills We need to keep all. Benefits: description: "Cooley LLP offers a competitive compensation and excellent benefits program." Then later: "We offer a full range of elective benefits including medical, health savings account (with applicable medical plan), dental, vision, health and/or dependent care flexible spending accounts, pre-tax commuter benefits, life insurance, AD&D, long-term care coverage, backup care for children and/or adults and other parental support benefits. In addition to elective benefit options, benefited employees receive firm-paid life insurance, AD&D, LTD, short term medical benefits as well as 21 days of Paid Time Off (“PTO”) and 10 paid holidays each year. We provide generous parental leave and fertility benefits. New employees will attend a detailed benefit orientation to learn more about our many benefits and resources." We should turn each benefit item into

  • maybe. But we need to preserve all substantive info; we can keep as prose but better to list. The instruction: Use
    • for any list of duties/requirements/benefits. So we should list benefits as
      • . We'll split the sentence into items. Benefits list items: - medical - health savings account (with applicable medical plan) - dental - vision - health and/or dependent care flexible spending accounts - pre-tax commuter benefits - life insurance - AD&D - long-term care coverage - backup care for children and/or adults - other parental support benefits - firm-paid life insurance - AD&D (again? but we can keep) - LTD - short term medical benefits - 21 days of Paid Time Off (“PTO”) - 10 paid holidays each year - generous parental leave -