Jobs · OTHR · California

Director ( Commercial Due Diligence )

Stax · San Francisco, CA · 1 mo ago
OTHR$230k–$300k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Why Grant Thornton | Stax Transactions" which is like an intro. Then "Your Day‑to‑Day May Include" (responsibilities). Then "Required" (requirements/qualifications). Then "Preferred". Then "Locations: ..." (maybe schedule? Actually location). Then "Compensation & Benefits". Also mention hybrid work model: in-person attendance three days per week. That could be schedule? It's about work model. Could be under Schedule? But schedule is not explicit; we have location and hybrid requirement. According to rules: include a section ONLY when posting has real, specific content for it. We have Compensation & Benefits (specific salary range, benefits). We have Locations (specific cities). We have hybrid work model (in-person three days per week) - could be under Schedule? But schedule is about work hours/days; we could treat as Schedule section. However the rule says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (intro), Responsibilities (day-to-day), Requirements (required qualifications), Preferred (maybe under Skills? but we can have a Skills section? Actually we have technical skills etc. Could combine Required and Preferred into Requirements and Skills? But we need to preserve all substantive info. We could have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits, Pay, Schedule (hybrid). However we must not create sections with filler like "commensurate with experience" etc. Pay section: we have base salary range $230k-$300k plus target annual bonus. That's specific, so we can have Pay section. Benefits: we have comprehensive benefits list. So Benefits section. Schedule: we have hybrid work model requiring in-person attendance three days per week at a firm office or client site. That's specific, so Schedule section. Locations: Could be under Schedule? Not exactly. There's no explicit heading for Locations in the list of allowed headings, but we could treat as part of About the role or maybe as a separate section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Locations. However we could embed location info in About the role or maybe in Schedule? But schedule is about days, not location. Could we create a custom 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 exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a Locations heading; we should fold location info into another section, maybe About the role or Responsibilities. Probably About the role is appropriate: include location info there. Thus sections: About the role (includes why GT|Stax, locations, hybrid model? Actually hybrid model is schedule, but we could still mention location there and schedule separate). We'll keep schedule separate. Responsibilities: from "Your Day‑to‑Day May Include" bullet list. Requirements: from "Required" bullet list (technical skills, qualifications, abilities). Could also include "Required" as heading. Preferred: maybe under Skills? But we have a Skills heading allowed. Could put preferred under Skills. However we also have Required technical skills etc. Could combine Required and Preferred into Requirements and Skills sections. Let's think: The posting has "Required You have the following technical skills, qualifications, and abilities:" then list. Then "Preferred Private equity or investment committee‑facing experience Advanced degree (MBA or equivalent) Experience supporting post‑close value creation or growth strategy". So we could have Requirements section for required qualifications, and Skills section for preferred? But Skills could also include both required and preferred skills. However we need to preserve all info; we can have Requirements (required) and Skills (preferred). Or we could have Requirements (required) and Qualifications (preferred). But Qualifications heading is allowed. Let's use Requirements for required, Qualifications for preferred. That seems fine. Thus sections: - About the role: includes intro paragraph about why GT|Stax, work with PE, etc., plus locations (Chicago, Boston, NYC) and hybrid model? Actually hybrid model is schedule; we could mention location only here. - Responsibilities: bullet list from Day-to-Day. - Requirements: bullet list from Required. - Qualifications: bullet list from Preferred. - Benefits: list from benefits paragraph. - Pay: base salary range and target annual bonus. - Schedule: hybrid work model requiring in-person attendance three days per week. We must not repeat job title as heading. No Job ID etc. We must output only HTML fragment, no markdown fences. We need to use

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

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: EEO, equal opportunity, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal etc. The posting includes an EEO statement and San Francisco Fair Chance Ordinance; we must remove those. Also remove "Other duties as assigned" maybe? It's part of responsibilities? It's a generic line; we could keep? It's substantive but generic; maybe we keep it as part of responsibilities? It's not boilerplate; it's a duty. We'll keep. Now craft HTML. Let's extract content. About the role: The intro paragraphs: "Why Grant Thornton | Stax Transactions Work directly with leading private equity firms, growth investors, and Fortune 500 executives on high-stakes strategic and transaction decisions. Lead high-impact engagements with real ownership—Directors shape the work, drive client outcomes, and influence investment decisions from day one. Experience the best of both worlds: the entrepreneurial culture and agility of a boutique consulting firm combined with the scale, reach, and platform of Grant Thornton. Gain broad exposure across industries, transaction types, and growth challenges in a model designed to accelerate commercial judgment and leadership development. Operate in lean, collaborative teams where senior leaders are accessible, mentorship is real, and contributions are visible. Help build a rapidly growing platform post-acquisition, with opportunities to shape capabilities, develop new offerings, and contribute to firm-wide growth initiatives. Deliver meaningful client impact without the traditional road-warrior consulting lifestyle through a more sustainable, low-travel operating model. Join a high-performance culture that values intellectual curiosity, initiative, collaboration, and merit-based advancement." Then later: "As a Commercial Due Diligence Director, you’ll play a leadership role in Grant Thornton | Stax Transactions , partnering with corporate leaders and private equity investors to evaluate growth potential, downside risk, and value creation opportunities across transactions. You’ll combine deep commercial diligence expertise, strong client leadership, and business development acumen—serving as a trusted advisor while helping grow the firm’s Commercial Due Diligence capability." We could combine these into About the role. Also include locations: "Locations: Chicago, Boston, and NYC." We'll add that as a sentence. We'll not include hybrid model here; that goes to Schedule. Now Responsibilities: bullet list from "Your Day‑to‑Day May Include". Let's list each bullet: - Lead complex buy‑side and sell‑side due diligence engagements for corporate and private equity clients - Evaluate market opportunity, growth sustainability, customer behavior, competitive positioning, and revenue risk - Translate analyses into executive‑level and investment‑committee‑ready insights that influence deal decisions - Serve as a senior client advisor, building long‑term relationships and managing executive stakeholder expectations - Drive integrated diligence delivery, partnering closely with Financial DD, Value Creation, IT, and Human Capital leaders - Oversee engagement economics, quality, and delivery across multiple concurrent transactions - Lead and contribute to business development, including proposals, client presentations, and account expansion - Develop thought leadership, methodologies, and go‑to‑market materials aligned to Commercial DD and Value Creation - Recruit, mentor, and develop managers and team members; provide career coaching and performance feedback - Contribute to firm‑building initiatives and practice growth efforts - Other duties as assigned We'll put each as

  • . Requirements: from "Required You have the following technical skills, qualifications, and abilities:" then list: - Bachelor’s degree in business, Economics, Finance, Strategy, or a related field - Typically, 8–10+ years of experience in commercial due diligence, strategy consulting, transaction advisory, or private equity - Proven experience leading PE‑backed and corporate M&A diligence engagements - Strong expertise in: - Market sizing and growth assessment - Customer and revenue analysis - Competitive and industry dynamics - Demonstrated ability to influence executive and investor decision‑making - Track record of managing teams, client relationships, and complex engagements - Exceptional communication, leadership, and stakeholder management skills Note: The "Strong expertise in:" includes sub-bullets. We need to represent as nested list? The instruction: use
    • for any list of duties/requirements/benefits. For sub-items, we can nest
        inside
      • . That's fine. Qualifications (Preferred): list: - Private equity or investment committee‑facing experience - Advanced degree (MBA or equivalent) - Experience supporting post‑close value creation or growth strategy Benefits: from "We also offer a comprehensive benefits package, including medical, dental, and vision coverage for you and your family; expanded family planning benefits; a 401(k) plan with company contributions regardless of your own; open vacation policy; life and disability insurance; generous parental leave; pre-tax transit benefits; mobile phone stipend; wellness reimbursement; charitable gift matching; and more." We'll list each benefit as
      • . Pay: "This role offers competitive compensation, including a base salary range of $230,000–$300,000, plus a target annual bonus. Grant Thornton Stax follows a pay-for-performance compensation philosophy, base salary is commensurate with experience, and total cash compensation may vary based on individual and firm performance." We need to avoid filler like "commensurate with experience" and "may vary". Those are somewhat vague but they are part of the description. The rule says: 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. It says we should not create a Pay section if the content is just filler like "commensurate with experience". However we do have concrete base salary range. The sentence also includes "base salary is commensurate with experience, and total cash compensation may vary based on individual and firm performance." That's somewhat filler but we still have concrete range. We can include the range and mention target annual bonus. We could possibly omit the vague parts? But we must preserve ALL substantive information; we cannot invent or summarize away detail. However we can maybe rephrase but must keep the info. The phrase "base salary is commensurate with experience" is substantive? It's a statement about how base salary is determined. It's not placeholder; it's actual policy. It's not "commensurate with experience" as placeholder; it's a description. The rule example of filler includes "commensurate with experience" as placeholder text to avoid. But here it's actual statement. However the rule says: 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. It seems they want to avoid sections where the only content is vague like "commensurate with experience". Since we have actual

Similar jobs