Jobs · Engineering · New York

Staff Software Engineer, Clean Room

LiveRamp · New York, NY · 3 wk ago
HybridEngineering$157k–$235k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must parse the job posting. First, the intro paragraphs about LiveRamp are likely not part of role description; they are company description. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." But we need to reformat a job posting into clean semantic HTML. Likely we include the role description sections: "You Will" (responsibilities), "About You" (requirements/qualifications), "Preferred Skills", "The approximate annual base compensation range", "Benefits". Also maybe "More About Us" is company info, maybe not needed but could be considered substantive? The instruction says remove boilerplate, navigation, legal, EEO, etc. The "More About Us" and diversity statement might be considered boilerplate? It's not exactly boilerplate but could be considered company info. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The diversity statement is EEO? It's about affirmative action and equal opportunity employer. That's EEO boilerplate, should be removed. Also the parts about accommodation, California privacy policy, recruitment agencies, etc. Should be removed. Thus we keep: role responsibilities, requirements/qualifications, preferred skills, pay, benefits. Possibly also a short paragraph about the team? The first paragraph about team designing core software could be considered part of role description (maybe "About the role"). We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include. We have content: - About the role: maybe a summary: "Our team designs and expands the core software that drives LiveRamp’s Clean Room ecosystem, ensuring a secure and dependable environment for data collaboration. We excel at building distributed systems engineered for privacy-focused computation and resilient platform functionality. Working closely across engineering and product disciplines, we tackle complex technical challenges to streamline developer workflows and enhance the end-user experience. Driven by a commitment to operational excellence, measurable business impact, and ethical innovation, our mission balances rapid feature delivery with long-term platform strategy." That seems like role description. - Responsibilities: list from "You Will" bullet points (though they are sentences separated by periods). We need to convert to
  • . The sentences: "You Will Design, build, and sustain scalable software and infrastructure supporting our privacy-centric data collaboration ecosystem. Lead the technical strategy and global deployment of distributed platform components and backend services. Translate high-level product requirements into tactical execution plans, engineering roadmaps, and measurable goals. Drive technical architecture reviews and champion best practices to enhance system security, maintainability, and reliability. Partner cross-functionally with security, privacy, and product stakeholders to deliver high-impact capabilities across the development lifecycle. Guide engineering talent through direct technical leadership, detailed design feedback, and code mentorship. Streamline developer efficiency by reducing friction in operational workflows, automated testing, and CI/CD deployment pipelines. Utilize system performance metrics and operational analytics to guide roadmap priorities and drive continuous product quality. Troubleshoot, resolve, and prevent operational outages to ensure high availability for mission-critical services. Exert cross-organizational technical influence to help shape future platform investments and overarching engineering strategies." We can treat each as a list item. - Requirements/Qualifications: from "About You" bullet points (list of requirements). Also maybe degree requirement. List: "8+ years of professional expertise in software engineering, with a proven track record of deploying and managing large-scale production environments. Extensive background in the architecture, implementation, and long-term maintenance of high-scale backend services and distributed systems. Demonstrated capability in spearheading technical initiatives that require coordination across multiple engineering teams or complex workstreams. Exceptional proficiency in writing robust, clean code using one or more modern programming languages. Deep understanding of advanced system architecture, comprehensive API design, data modeling techniques, and service-oriented frameworks. Commitment to engineering excellence through the application of rigorous testing, peer reviews, system observability, and operational best practices. A collaborative mindset for working cross-functionally with product stakeholders and engineering peers to ship impactful, high-stakes features. Skill in deconstructing highly ambiguous technical challenges into clear, actionable roadmaps and phased project execution plans. Articulate communication skills, both written and verbal, capable of influencing technical strategy and alignment. Degree in Computer Science, Software Engineering, or an equivalent technical field of study." We could split into Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. But we can combine if content overlaps. Better to separate: Requirements (experience, background) and Qualifications (education, skills). However the list includes both experience and skills. Could treat as Requirements (experience) and Qualifications (education + skills). But we also have a separate "Preferred Skills" section. Thus we could have:

    Requirements

    with items: 8+ years..., extensive background..., demonstrated capability..., exceptional proficiency..., deep understanding..., commitment..., collaborative mindset..., skill in deconstructing..., articulate communication skills...

    Qualifications

    with item: Degree in Computer Science, Software Engineering, or an equivalent technical field of study. Alternatively combine. But we must not create sections with filler text. All items are substantive. Then Preferred Skills: list: "A background in designing and scaling high-volume data pipelines alongside modern workflow orchestration systems. Hands-on experience building and maintaining cloud-native infrastructure and containerized deployment pipelines. Prior domain expertise in privacy-centric architectures, data clean rooms, analytical frameworks, or large-scale data platforms. Proven success in navigating strict security protocols, regulatory compliance, and privacy standards in complex environments. Demonstrated leadership in elevating engineering productivity through technical mentorship, code quality, and process refinement. Strong track record of balancing short-term product deliverables with long-term platform strategy and technical vision." Pay: we have "The approximate annual base compensation range is $156,500 to $235,000. The actual offer, reflecting the total compensation package and benefits, will be determined by a number of factors including the applicant's experience, knowledge, skills, and abilities, geography, as well as internal equity among our team." We should include Pay section with that paragraph (maybe as

    ). Not create Schedule section because no schedule info. Benefits: we have a Benefits paragraph with bullet-like sentences but not list. It says: "Benefits People: Work with talented, collaborative, and friendly people who love what they do. Fun: We host in-person and virtual events such as game nights, happy hours, camping trips, and sports leagues. Work/Life Harmony: Flexible paid time off, paid holidays, options for working from home, and paid parental leave. Comprehensive Benefits Package: LiveRamp offers a comprehensive benefits package designed to help you be your best self in your personal and professional lives. Our benefits package offers medical, dental, vision, life and disability, an employee assistance program, voluntary benefits as well as perks programs for your healthy lifestyle, career growth and more. Savings: Our 401K matching plan—1:1 match up to 6% of salary—helps you plan ahead." We could format as

    • each benefit category. Or keep as

      with sentences. The instruction: Use

      • for any list of duties/requirements/benefits. So we should turn benefits into a list. Thus Benefits section:

        Benefits

        • Work with talented, collaborative, and friendly people who love what they do.
        • We host in-person and virtual events such as game nights, happy hours, camping trips, and sports leagues.
        • Flexible paid time off, paid holidays, options for working from home, and paid parental leave.
        • Comprehensive benefits package including medical, dental, vision, life and disability, employee assistance program, voluntary benefits, and perks programs for healthy lifestyle, career growth and more.
        • 401K matching plan—1:1 match up to 6% of salary.
        We need to preserve all substantive information; we must not lose details like "People:", "Fun:", etc. We can incorporate them into list items. Now About the role: we have a paragraph describing team. Could be put under

        About the role

        ...

        . Now we need to output only HTML fragment, no /, no markdown. Thus final HTML:

        About the role

        Our team designs and expands the core software that drives LiveRamp’s Clean Room ecosystem, ensuring a secure and dependable environment for data collaboration. We excel at building distributed systems engineered for privacy-focused computation and resilient platform functionality. Working closely across engineering and product disciplines, we tackle complex technical challenges to streamline developer workflows and enhance the end-user experience. Driven by a commitment to operational excellence, measurable business impact, and ethical innovation, our mission balances rapid feature delivery with long-term platform strategy.

        Responsibilities

        • Design, build, and sustain scalable software and infrastructure supporting our privacy-centric data collaboration ecosystem.
        • Lead the technical strategy and global deployment of distributed platform components and backend services.
        • Translate high-level product requirements into tactical execution plans, engineering roadmaps, and measurable goals.
        • Drive technical architecture reviews and champion best practices to enhance system security, maintainability, and reliability.
        • Partner cross-functionally with security, privacy, and product stakeholders to deliver high-impact capabilities across the development lifecycle.
        • Guide engineering talent through direct technical leadership, detailed design feedback, and code mentorship.
        • Streamline developer efficiency by reducing friction in operational workflows, automated testing, and CI/CD deployment pipelines.
        • Utilize system performance metrics and operational analytics to guide roadmap priorities and drive continuous product quality.
        • Troubleshoot, resolve, and prevent operational outages to ensure high availability for mission-critical services.
        • Exert cross-organizational technical influence to help shape future platform investments and overarching engineering strategies.

        Requirements

        • 8+ years of professional expertise in software engineering, with a proven track record of deploying and managing large-scale production environments.
        • Extensive background in the architecture, implementation, and long-term maintenance of high-scale backend services and distributed systems.
        • Demonstrated capability in spearheading technical initiatives that require coordination across multiple engineering teams or complex workstreams.
        • Exceptional proficiency in writing robust, clean code using one or more modern programming languages.
        • Deep understanding of advanced system architecture, comprehensive API design, data modeling techniques, and service-oriented frameworks.
        • Commitment to engineering excellence through the application of rigorous testing, peer reviews, system observability, and operational best practices.
        • A collaborative mindset for working cross-functionally with product stakeholders and engineering peers to ship impactful, high-stakes features.
        • Skill in deconstructing highly ambiguous technical challenges into clear, actionable roadmaps and phased project execution plans.
        • Articulate communication skills, both written and verbal, capable of influencing technical strategy and alignment.

        Qualifications

        • Degree in Computer Science, Software Engineering, or an equivalent technical field of study.

        Preferred Skills

        • A background in designing and scaling high-volume data pipelines alongside modern workflow orchestration systems.
        • Hands-on experience building and maintaining cloud-native infrastructure and containerized deployment pipelines.
        • Prior domain expertise in privacy-centric architectures, data clean rooms, analytical frameworks, or large-scale data platforms.
        • Proven success in navigating strict security protocols, regulatory compliance, and privacy standards in complex environments.

Similar jobs

Staff Software Engineer

RelativityAlabama, United States· 3 mo ago
Engineering$174k–$262k/yrapply on kcura.wd1.myworkdayjobs.com