Jobs · OTHR

Staff People Partner

Anaconda · United States · 1 mo ago
RemoteRemoteOTHR$162k–$211k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Anaconda", "Summary", "Why This Role Exists", "What You'll Do", "Your Impact Will Be Measured Through", "What You Need", "What Will Make You Stand Out", "Why You'll Like Working Here", plus salary and benefits info. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should only include sections when posting has real specific content. The headings we can use: "About the role" maybe corresponds to Summary? Or "About Anaconda"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings where appropriate. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must include a section only when posting has real specific content for it—never emit heading followed by filler/placeholder text. Thus we need to decide which sections to include: About the role (summary), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What You Need, What Will Make You Stand Out maybe), Benefits (benefits listed), Pay (salary range), Schedule? Not mentioned, so omit Schedule. We must not include boilerplate like EEO, privacy, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details but can format as

or

  • . Must not lose any substantive info. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, "About Anaconda" paragraph: description of company. Could be part of "About the role"? Usually "About the role" is about the role, not company. But we have a "Summary" section describing the role. So we can use "About the role" heading for the Summary paragraph (the role description). The "About Anaconda" could be considered company overview; maybe we can include as part of "About the role" or maybe we can omit because not required? The instruction: Prefer a few substantive sections over many thin ones. We could combine company overview into About the role? But the heading "About the role" expects role description. However we could still include company overview under same heading? Might be okay but risk of misalignment. Better to have separate sections? The allowed headings list includes only those examples; we could also use other headings? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; not that we cannot use others, but likely they expect those. We'll stick to those. Thus we need sections: About the role (summary), Responsibilities (What You'll Do), Requirements (What You Need), Qualifications maybe combined with Requirements? Could also have Skills (What Will Make You Stand Out). Benefits (benefits list). Pay (salary range). Possibly also "Impact" could be part of Responsibilities? But we could include as its own section? Not in list. Could omit or incorporate into Responsibilities. We must not create sections with filler. So we need to ensure each heading has substantive content. Let's extract each. **About the role** (Summary): "Anaconda is seeking an experienced Staff People Partner to help managers navigate complex people decisions and employee situations across the company. This role that primarily partners with Managers and Directors and owns complex individual employee matters across all departments at Anaconda. While our People Business Partners focus on executive partnership, organizational strategy, workforce planning, and broader talent priorities, the Staff People Partner helps translate that context into action with managers and employees. You'll coach managers through performance challenges, lead employee relations matters, support individual talent and compensation decisions, and navigate complex situations requiring strong judgment across multiple People disciplines. This role is also designed for a modern, AI-enabled People practitioner. You'll use AI as a core part of how you work; helping you synthesize information, identify patterns, prepare managers, improve documentation, accelerate research, and manage a broad portfolio of work with greater speed and quality. The goal isn't to automate human judgment or sensitive People interactions; it's to use technology to create more capacity for the work that genuinely requires coaching, judgment, and human connection. Success in this role isn't measured simply by resolving the issue in front of you. It's measured by making managers more capable, identifying patterns, improving how work gets done, and creating leverage across the People function." We'll keep that as a

    maybe multiple paragraphs but can be one. **Responsibilities** (What You'll Do): This includes several bullet-like paragraphs. We need to convert to

    • . The text includes headings: "Partnership, Organizational Insight & AI Leverage:", "Individual Talent & People Decisions", "Employee Relations & Complex Employee Situations", "Manager Coaching & Performance". Under each there are sentences. We'll extract each sentence as list items? Better to keep each bullet as a list item. We'll parse. Under Partnership, Organizational Insight & AI Leverage: - Work closely with PBPs and People specialists while maintaining sufficient organizational context to understand business priorities, leadership dynamics, talent risks, and upcoming changes - Act as a conduit of information across the People Team, translating strategy into action while surfacing patterns, emerging risks, and insights from managers and employees - Use AI extensively to synthesize information, identify patterns, prepare for complex conversations, improve documentation, accelerate research, and manage follow-through - Build repeatable AI-enabled workflows, prompts, projects, and tools that increase your own capacity, can create leverage for the broader People Team, and people managers within the organization - Continuously identify work that can be simplified, automated, or AI-enabled so that human time is concentrated on judgment, coaching, relationships, and high-impact decisions - Turn recurring friction into better manager guidance, frameworks, processes, or scalable solutions - Collaborate effectively up, down, and across the organization without creating unnecessary handoffs or dependency Individual Talent & People Decisions: - Partner with managers and PBPs on promotions, off-cycle compensation changes, retention requests, internal mobility, and other individual talent decisions - Evaluate requests against company frameworks, precedent, internal equity, business context, and employee impact - Help managers strengthen the thinking behind their recommendations rather than simply processing requests - Support the manager- and employee-level execution of broader talent and organizational decisions Employee Relations & Complex Employee Situations: - Independently lead employee relations matters requiring investigation, judgment, coaching, or intervention - Assess employee concerns, gather relevant context, develop recommendations, and drive matters through resolution - Navigate complex employee situations that may span accommodations, immigration, location changes, leaves, international employment, compensation, or other People disciplines - Bring in Legal, People specialists, PBPs, or other partners when their expertise or ownership is required while maintaining momentum toward resolution Manager Coaching & Performance: - Coach managers through performance concerns, feedback, development conversations, and performance improvement - Help managers diagnose underlying issues and distinguish between employee performance, management effectiveness, role clarity, and broader organizational factors - Prepare managers for difficult or sensitive conversations while ensuring managers retain ownership of managing their teams - Drive thoughtful, consistent, and well-documented performance decisions and recognize when complexity, risk, seniority, or organizational implications require PBP involvement We'll put all these as
    • under a single
        maybe grouped? Could also have subheadings but not allowed. We'll just list all. **Requirements** (What You Need): list of bullet-like sentences. Extract: - Demonstrated advanced use of generative AI as a core part of day-to-day work, including using AI to synthesize complex information, accelerate research and documentation, improve decision support, and materially increase personal or team capacity - Experience building reusable AI-enabled workflows, prompts, projects, agents, or tools rather than relying solely on one-off prompting - Excellent judgment regarding where AI should and should not be used, particularly with sensitive employee information and consequential People decisions - 10+ years experience in HR business partnering, People Partner, employee relations, or similarly consultative People roles - Deep experience independently coaching managers and leaders through complex performance and employee situations - Demonstrated ability to navigate sensitive, ambiguous, and high-stakes employee matters with excellent judgment - Experience partnering effectively with leaders at the Manager, Director, Senior Director, and/or VP level - Experience with individual talent decisions such as promotions, compensation changes, retention, or internal mobility - Strong systems thinking and demonstrated ability to recognize patterns and improve how work gets done, not simply resolve individual issues - Demonstrated ability to influence and collaborate effectively up, down, and across an organization without relying on formal authority - Exceptional communication, follow-through, ownership, and bias to action - You embody our values: Curious by Default, Build Together, Own It, and Lead with Guts and Heart, and our behaviors: Clarity, Care and Candor - You care deeply about fostering an environment where people of all backgrounds and experiences can flourish We'll put as
        • . **Skills** (What Will Make You Stand Out): list. - Experience operating across multiple organizations or business functions rather than within a single dedicated client group - Experience working across Legal, Compensation, People Operations, Finance, and other People specialties to resolve complex situations - Demonstrated success translating patterns from individual employee or manager situations into broader organizational insights or scalable improvements - Experience working in a distributed or global organization with complex employment considerations - A track record of increasing your own or a team's capacity through AI, systems thinking, and redesigned ways of working - Experience working in a fast-paced startup environment - Experience working in an open-source, AI, or data science-oriented company We'll put as
          • . **Benefits**: list from "In addition to base salary, we offer a comprehensive benefits package that includes:" then bullet list. - Flexible Vacation Policy - Medical, Dental, and Vision Insurance - Short Term and Long Term Disability - Paid Parental Leave - Monthly Wellness Stipend - Employee Assistance Program and Mental Health Resources We'll put as
            • . **Pay**: salary range info. We need to include the base salary range: "$162,000 - $211,250 USD for candidates in New York City and San Francisco, and $122,000 - 176,000 USD for other US-based team members, along with annual bonus potential, equity participation, and benefits." Also mention that salary ranges determined by role, level, location; individual compensation determined by various factors. We'll keep that as

              . We should not include filler like "commensurate with experience". Not present. We must not include application deadline? That's maybe considered metadata but not required; we can drop as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

              or drop it. The deadline is minor metadata; we could include in a short

              maybe under About the role? But better to drop it to keep concise. However we must preserve ALL substantive information; is deadline substantive? It's about application process; they said remove application instructions. The deadline is part of application instructions? Probably yes, we can drop. Also remove EEO, privacy, etc. Now construct HTML. We'll start with

              About the role

              then

              ... (the summary). Then

              Responsibilities

              then
              • ... etc. Then

                Requirements

                then
                  ... Then

                  Skills

                  then
                    ... Then

                    Benefits

                    then
                      ... Then

                      Pay

                      then

                      ... . Make sure to close tags. Let's craft the

Similar jobs