Jobs · Finance · New York

Associate - Technology (Workday Financials)

PJT Partners · New York, United States · 1 mo ago
On-siteFinance$95k–$120k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description of company, then responsibilities, qualifications, salary. No explicit headings like "About the role", but we can infer sections: maybe "About the role" could be the introductory paragraph describing the firm and role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Intro paragraph about PJT Partners (company description). Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have responsibilities (list). We have qualifications (list). We have salary info (Pay). There's no explicit Benefits or Schedule. So we should not create Benefits or Schedule sections. We have "Expected annualized base salary of $95,000 to $120,000." That's Pay. So we can have a Pay section with that info. We also have description of company and role maybe as "About the role". Could combine the introductory paragraph describing the firm and the role's purpose. That seems appropriate. We also have "Additional Responsibilities Include" then a long list of responsibilities. So we can have Responsibilities section with

    • . Qualifications: list of bullet points (though they are semicolon separated). We'll convert to
      • . We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from responsibilities and qualifications. We must remove boilerplate: EEO statements, accommodation, California applicant privacy notice, application instructions (submit resume in PDF). Also remove duplicated lines. Also remove "PJT is an equal opportunity employer..." etc. Also remove "For more information or to request an accommodation, please contact Human Resources." etc. Also remove "California Applicants: ..." etc. Also remove "Applicant Privacy Notice ..." etc. Also remove "In order to be considered, please ensure your resume/CV is submitted in PDF format." We also need to remove any navigation/footer etc. Not present. We need to keep the company description paragraph at start. Also maybe the sentence "From the beginning, PJT Partners has firmly believed that having the best people is key to building an enduring franchise..." etc. That's part of company description; we keep. We need to keep the sentence about Workday professional role etc. That's part of responsibilities intro. We need to keep the sentence "Expected annualized base salary of $95,000 to $120,000." plus the explanation about factors. That's Pay. We need to keep the sentence about base salary being one component and may include additional rewards, incentives and benefits, including discretionary bonus component. That's also compensation info; could be part of Pay section. We should not create a Benefits section unless posting actually states them. It mentions "additional rewards, incentives and benefits, including but not limited to, a discretionary bonus component." That's a mention of benefits but vague. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (discretionary bonus component). However, it's not specific details. It says "may include additional rewards, incentives and benefits, including but not limited to, a discretionary bonus component." That's still a statement about benefits. Should we include a Benefits section? The instruction says prefer a few substantive sections over many thin ones. The benefits statement is vague; maybe we can incorporate into Pay section as part of compensation. Since they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, albeit vague. But we could still include a Benefits section with that statement. However, they also said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits statement is not filler; it's a statement that there may be discretionary bonus. So we could include a Benefits section with that sentence. But we also have Pay section with salary range and explanation. Could combine Pay and Benefits into one "Compensation" section, but headings limited to given list. We could use Pay for salary and Benefits for bonus. That seems okay. We must not include Schedule section as not present. We must not include Requirements or Skills separate if they are covered in Qualifications. The list of qualifications includes skills. We could just have Qualifications section. We need to ensure we don't repeat job title as heading. Not needed. Now produce HTML fragment:

        About the role

        ... company description and role intro ...

        Responsibilities

        • ...
        • ...

        Qualifications

        • ...
        • ...

        Pay

        Expected annualized base salary of $95,000 to $120,000. This range represents the low and high ends of the expected annualized base salary for this position. The specific base salary received by any employee will be informed by a number of factors, including but not limited to, role level and scope, location, candidate’s relevant qualifications, skills and experience. Base salary is one component of PJT Partners’ compensation structure. In addition to base salary, PJT Partners’ compensation structure may include additional rewards, incentives and benefits, including but not limited to, a discretionary bonus component.

        Benefits

        PJT Partners’ compensation structure may include additional rewards, incentives and benefits, including but not limited to, a discretionary bonus component.

        But that duplicates the benefits sentence. Better to incorporate benefits into Pay section, not create separate Benefits section. Since the instruction says prefer few substantive sections over many thin ones. So we can keep Pay section only, and include the benefits sentence within Pay. That avoids a thin Benefits section. Thus sections: About the role, Responsibilities, Qualifications, Pay. Now we need to extract the exact prose for About the role. Let's copy the introductory paragraphs up to "Responsibilities". The posting: "PJT Partners is a global advisory-focused investment bank. Our team of senior professionals delivers a wide array of strategic advisory, shareholder advisory, restructuring and special situations and private fund advisory and placement services to corporations, financial sponsors, institutional investors and governments around the world. We offer a unique portfolio of advisory services designed to help our clients achieve their strategic objectives. We also provide, through PJT Park Hill, private fund advisory and fundraising services for alternative investment managers, including private equity funds, real estate funds and hedge funds. From the beginning, PJT Partners has firmly believed that having the best people is key to building an enduring franchise. Our perspective was, and remains, that a great team brings in both top tier clients and appeals to a wide-range of diverse, talented colleagues. Fostering an inclusive culture, which welcomes differing perspectives and beliefs, enables us to provide the best advice and insights to our clients. To learn more about PJT Partners, please visit our website at www.pjtpartners.com. Responsibilities" We need to stop before "Responsibilities". So the About the role paragraph ends before "Responsibilities". Should we include the sentence "To learn more about PJT Partners, please visit our website at www.pjtpartners.com."? That's part of company description but maybe considered boilerplate? It's a link to website; not necessarily boilerplate but could be considered navigation? It's not a legal/EEO etc. It's a generic call to visit website. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The website link is not exactly navigation but could be considered generic. However, it's part of the company description; maybe we keep it. It's not a call to apply. It's just informational. I'd keep it. Thus About the role paragraph includes all that. Now Responsibilities: after "Responsibilities" there is a sentence: "The PJT Partners Technology team is responsible for creating and continuously improving a robust and secure technology foundation that supports the firm's business activities. We are seeking a Workday professional to join our dynamic team and support our Workday Financials platform. This individual will provide hands-on configuration and production support across core Workday Financials modules, partnering closely with Finance stakeholders to maintain and enhance the firm's Workday ecosystem." Then "Additional Responsibilities Include" followed by a long list separated by semicolons. We need to turn each item into
      • . The list items are separated by semicolons, some have commas inside. We need to split at semicolons. Let's extract the list: "Provide day-to-day production support for Workday Financials, triaging, diagnosing and resolving configuration or data issues; Support Workday Financials-related projects from planning through execution, ensuring alignment with business goals and timelines; Manage configuration, testing and deployment of updates across Workday Financials modules such as Financial Accounting, Procurement, Accounts Payable, Expenses and Projects, including business process configuration and security administration; Support Financials platform roll-out within various business verticals, including finance, accounting and procurement teams; Design, build and maintain business process configuration across Financials workstreams, including approval chains, conditional routing and notifications; Configure and maintain domain and business process security policies, supporting security group assignments, access reviews and audit and compliance requests; Build and maintain custom reports, calculated fields and dashboards using Workday Report Writer, partnering with Finance to translate reporting requirements into scalable designs; Partner with Finance, Accounting and other cross-functional teams to understand business needs and support the design of effective Workday Financials solutions; Support integration efforts between Workday Financials and other enterprise systems (e.g. banking platforms, expense management tools, procurement vendors), helping ensure smooth data flow and operational continuity; Support Workday release readiness activities, including reviewing new features ahead of Workday's semi-annual updates, testing impacted areas and coordinating changes with Finance stakeholders; Stay current on Workday's evolving AI and automation capabilities, and help identify opportunities to apply them to Financials processes and reporting; Help monitor day-to-day user experience and platform performance for Workday Financials, flagging issues and supporting resolution, and escalating and coordinating with Workday support or third-party consultants as needed." We need to ensure each
      • ends with a period? The original items have trailing semicolons; we can convert to sentences ending with period. Now Qualifications: after "Qualifications" there is: "PJT Partners seeks to hire individuals who are highly motivated, intelligent and have demonstrated excellence in prior endeavors. In addition, qualified candidates will possess the following:" Then list: "Bachelor's degree in Business Administration, Information Technology, Finance or a Business-related degree; 3-4 years of experience with Workday Financials, with hands-on configuration exposure to Accounts Payable, Contracts to Cash, General Ledger and

Similar jobs