Direct Solutions Consultant (Investment Management)
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.
We need to decide which sections to include. The posting includes:
- Who We Are (company description)
- The Role (description of Solutions Consultants/Architects)
- Pay info: "Addepar takes a market-based approach to pay. A successful candidate’s starting pay will be determined based on the role, job-related skills, experience, qualifications, work location, and market conditions. The range displayed on each job posting reflects the minimum and maximum target base salary for roles in Colorado, California, and New York. The current range for this role is $74,000 - $93,000 (base salary) + bonus + equity + benefits. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits."
Thus we have Pay section with specific numbers.
- Benefits: Not explicitly listed beyond "bonus + equity + benefits". No detail of benefits. So we should not create a Benefits section unless posting actually states them. It only mentions "+ benefits" generically, no specifics. So we should not create Benefits section.
- Schedule: Not mentioned.
- Responsibilities: There's a "What You’ll Do" list. That's responsibilities.
- Requirements/Qualifications/Skills: There's "Who You Are" list of qualifications, plus "Professional experience..." etc. Also there are bullet points for "Bonus" etc. So we can have Requirements or Qualifications.
- About the role: Could be "The Role" description. Could be "About the role". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which headings to use based on content.
We have:
- Who We Are: company overview. Could be "About the company" but not in list. Could be omitted? The instruction says we can use those headings; but we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings for clarity. However "Who We Are" is not in that list; but we could treat it as "About the role"? Not exactly. Maybe we can omit "Who We Are" as it's not required? But we must preserve ALL substantive information. So we need to include company description somewhere. Could put it under a heading like "About the company" but not in list. The instruction says use those headings for section headings (e.g. ...). It might be okay to use other headings if needed, but better to map to given ones. "Who We Are" could be considered "About the role"? No. Could be "About the company" but not listed. Perhaps we can include it as a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but suggests using those for sections. It might be acceptable to have a heading like "About Addepar" but not in list. However to be safe, we could incorporate the "Who We Are" description into a
preceding the sections, without a heading. The instruction says "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." It doesn't forbid having a heading for company overview. But to follow the pattern, maybe we can use "About the role" heading for the role description, and put company description in a preceding
without heading. That seems okay.
Thus structure:
Who We Are ...
About the role
The Role Solutions Consultants/Architects are responsible for designing and implementing out-of-the-box solutions for new clients, ensuring that we are efficiently and effectively onboarding some of the world’s most sophisticated investors. They are focused on identifying how Addepar can unlock significant value for our clients’ businesses and regularly call upon their analytical skills in order to advise clients on how to model and examine their financial instruments and assets. They have a deep understanding of both finance and technology, take ownership of our clients’ happiness, and excel at project governance. Our ideal Solutions Consultant has a history of providing a superior client experience directly in investment management or in software deployments of a related domain. They are given discretion over their projects and work schedule and are expected to display a strong sense of self-reliance as well as the ability to collaborate with other Addepar resources within our Sales, Product, and Partnership organizations. They must be a strong project manager and possess an appreciation for our target markets (or hunger and willingness to learn). They also possess the technical skills to take a hands-on approach to teaching, learning, and developing the functions of our organization.
Responsibilities
- Demonstrate technical and industry expertise to onboard users and client data onto Addepar
- Deliver high-value client outcomes aligned with client expectations and transition seamlessly to a best-practice operating model
- Effectively and proactively manage expectations both internally and externally throughout the entire project lifecycle
- Ensure retention of clients driven by high client satisfaction and reference-ability
- Lead scope change to deliver high-value client outcomes aligned with client expectations
- 100% compliance with gold standard responsibilities and documentation
- Own historical data conversions from start-to-finish demonstrating Addepar’s best practice methodologies
- Prioritize and context-switch effectively to complete simultaneous projects, seeing each through to the finish line
- Proactively communicate project health and status to internal and external senior leadership
- Think critically about how to improve our current processes and tools both internally and externally as our client base expands
- Minimize project effort and duration through the development of scalable processes, pre-configured templates, and improved methodologies
- Own and lead delivery assurance for external, third-party engagements
- Be an expert on all things Addepar
Requirements
Professional experience in Project management, Financial Services or Consulting is preferred. Prior client-facing experience is a plus
- Candidates must have superior communication, organizational, and time-management skills
- An understanding of historical data conversion methodologies and different source systems (or willingness to learn)
- Process-oriented with an eye toward continuous improvement
- The ideal candidate must be independent, adaptable, and can thrive in a fast-paced environment
- Strong interpersonal skills to train and communicate effectively with clients via email, on the phone, and face-to-face
- Passion for technology and finance
- Occasional Travel
[Bonus] Previous experience in investment management software implementations
[Bonus] Previous experience with programming/scripting, specifically python
[Bonus] Previous experience with Salesforce
Pay
Addepar takes a market-based approach to pay. A successful candidate’s starting pay will be determined based on the role, job-related skills, experience, qualifications, work location, and market conditions. The range displayed on each job posting reflects the minimum and maximum target base salary for roles in Colorado, California, and New York. The current range for this role is $74,000 - $93,000 (base salary) + bonus + equity + benefits. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits.
We should not include Benefits, Schedule sections.
We need to remove boilerplate: EEO, equal opportunity, accommodation, phishing scam warning, etc. Also remove "Applicants must be legally authorized to work in the United States for any employer without requiring current or future visa sponsorship..." That's a requirement; it's substantive? It's about work authorization. Should we keep? It's a requirement. It's not boilerplate? It's a legal requirement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal work authorization requirement; might be considered legal boilerplate? It's specific to the job. Usually we keep work authorization requirement. It's not EEO. It's a requirement. I'd keep it. But we need to see if it's duplicated elsewhere. It's only there. We'll include it under Requirements maybe.
Add a line: "Applicants must be legally authorized to work in the United States for any employer without requiring current or future visa sponsorship (for example, employment-based visas such as H-1B, F-1/OPT, or similar), and must be authorized to begin work in the U.S. on their first day of employment."
We can add as a - under Requirements.
Now ensure we didn't miss any substantive info: The "Who We Are" paragraph includes details about Addepar: global data and AI platform, unifies portfolio, market and client data, delivers AI-powered insights, >1,400 firms in nearly 60 countries, manages $9 trillion assets, integrates with 650 partners, offices list. We need to preserve all that. We'll put that in a
before sections.
Now check for any duplicated lines: The "Who We Are" paragraph appears only once. The "The Role" paragraph appears only once. The "What You’ll Do" list we turned into responsibilities. The "Who You Are" list we turned into requirements. The bonus lines we kept as separate paragraphs maybe as
with [Bonus] prefix. Could also be
- under Requirements with a note. But we can keep as
. The instruction: Use
- for any list of duties/requirements/benefits. The bonus items are not a list but could be considered requirements. Safer to put them as
- under Requirements with a note "(Bonus)". We'll do that.
Thus Requirements
will include the bullet points plus bonus items as - with "(Bonus)" prefix.
Now check for any mention of "Occasional Travel" - we included as
- .
Now check for any mention of "Strong interpersonal skills to train and communicate effectively with clients via email, on the phone, and face-to-face" - included.
Now check for any mention of "Passion for technology and finance" - included.
Now check for any mention of
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. We need to decide which sections to include. The posting includes: - Who We Are (company description) - The Role (description of Solutions Consultants/Architects) - Pay info: "Addepar takes a market-based approach to pay. A successful candidate’s starting pay will be determined based on the role, job-related skills, experience, qualifications, work location, and market conditions. The range displayed on each job posting reflects the minimum and maximum target base salary for roles in Colorado, California, and New York. The current range for this role is $74,000 - $93,000 (base salary) + bonus + equity + benefits. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits." Thus we have Pay section with specific numbers. - Benefits: Not explicitly listed beyond "bonus + equity + benefits". No detail of benefits. So we should not create a Benefits section unless posting actually states them. It only mentions "+ benefits" generically, no specifics. So we should not create Benefits section. - Schedule: Not mentioned. - Responsibilities: There's a "What You’ll Do" list. That's responsibilities. - Requirements/Qualifications/Skills: There's "Who You Are" list of qualifications, plus "Professional experience..." etc. Also there are bullet points for "Bonus" etc. So we can have Requirements or Qualifications. - About the role: Could be "The Role" description. Could be "About the role". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which headings to use based on content. We have: - Who We Are: company overview. Could be "About the company" but not in list. Could be omitted? The instruction says we can use those headings; but we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings for clarity. However "Who We Are" is not in that list; but we could treat it as "About the role"? Not exactly. Maybe we can omit "Who We Are" as it's not required? But we must preserve ALL substantive information. So we need to include company description somewhere. Could put it under a heading like "About the company" but not in list. The instruction says use those headings for section headings (e.g. ...). It might be okay to use other headings if needed, but better to map to given ones. "Who We Are" could be considered "About the role"? No. Could be "About the company" but not listed. Perhaps we can include it as a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but suggests using those for sections. It might be acceptable to have a heading like "About Addepar" but not in list. However to be safe, we could incorporate the "Who We Are" description into a
preceding the sections, without a heading. The instruction says "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." It doesn't forbid having a heading for company overview. But to follow the pattern, maybe we can use "About the role" heading for the role description, and put company description in a preceding
without heading. That seems okay. Thus structure:
Who We Are ...
About the role
The Role Solutions Consultants/Architects are responsible for designing and implementing out-of-the-box solutions for new clients, ensuring that we are efficiently and effectively onboarding some of the world’s most sophisticated investors. They are focused on identifying how Addepar can unlock significant value for our clients’ businesses and regularly call upon their analytical skills in order to advise clients on how to model and examine their financial instruments and assets. They have a deep understanding of both finance and technology, take ownership of our clients’ happiness, and excel at project governance. Our ideal Solutions Consultant has a history of providing a superior client experience directly in investment management or in software deployments of a related domain. They are given discretion over their projects and work schedule and are expected to display a strong sense of self-reliance as well as the ability to collaborate with other Addepar resources within our Sales, Product, and Partnership organizations. They must be a strong project manager and possess an appreciation for our target markets (or hunger and willingness to learn). They also possess the technical skills to take a hands-on approach to teaching, learning, and developing the functions of our organization.
Responsibilities
- Demonstrate technical and industry expertise to onboard users and client data onto Addepar
- Deliver high-value client outcomes aligned with client expectations and transition seamlessly to a best-practice operating model
- Effectively and proactively manage expectations both internally and externally throughout the entire project lifecycle
- Ensure retention of clients driven by high client satisfaction and reference-ability
- Lead scope change to deliver high-value client outcomes aligned with client expectations
- 100% compliance with gold standard responsibilities and documentation
- Own historical data conversions from start-to-finish demonstrating Addepar’s best practice methodologies
- Prioritize and context-switch effectively to complete simultaneous projects, seeing each through to the finish line
- Proactively communicate project health and status to internal and external senior leadership
- Think critically about how to improve our current processes and tools both internally and externally as our client base expands
- Minimize project effort and duration through the development of scalable processes, pre-configured templates, and improved methodologies
- Own and lead delivery assurance for external, third-party engagements
- Be an expert on all things Addepar
Requirements
Professional experience in Project management, Financial Services or Consulting is preferred. Prior client-facing experience is a plus
- Candidates must have superior communication, organizational, and time-management skills
- An understanding of historical data conversion methodologies and different source systems (or willingness to learn)
- Process-oriented with an eye toward continuous improvement
- The ideal candidate must be independent, adaptable, and can thrive in a fast-paced environment
- Strong interpersonal skills to train and communicate effectively with clients via email, on the phone, and face-to-face
- Passion for technology and finance
- Occasional Travel
[Bonus] Previous experience in investment management software implementations
[Bonus] Previous experience with programming/scripting, specifically python
[Bonus] Previous experience with Salesforce
Pay
Addepar takes a market-based approach to pay. A successful candidate’s starting pay will be determined based on the role, job-related skills, experience, qualifications, work location, and market conditions. The range displayed on each job posting reflects the minimum and maximum target base salary for roles in Colorado, California, and New York. The current range for this role is $74,000 - $93,000 (base salary) + bonus + equity + benefits. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits.
We should not include Benefits, Schedule sections. We need to remove boilerplate: EEO, equal opportunity, accommodation, phishing scam warning, etc. Also remove "Applicants must be legally authorized to work in the United States for any employer without requiring current or future visa sponsorship..." That's a requirement; it's substantive? It's about work authorization. Should we keep? It's a requirement. It's not boilerplate? It's a legal requirement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal work authorization requirement; might be considered legal boilerplate? It's specific to the job. Usually we keep work authorization requirement. It's not EEO. It's a requirement. I'd keep it. But we need to see if it's duplicated elsewhere. It's only there. We'll include it under Requirements maybe. Add a line: "Applicants must be legally authorized to work in the United States for any employer without requiring current or future visa sponsorship (for example, employment-based visas such as H-1B, F-1/OPT, or similar), and must be authorized to begin work in the U.S. on their first day of employment." We can add as abefore sections. Now check for any duplicated lines: The "Who We Are" paragraph appears only once. The "The Role" paragraph appears only once. The "What You’ll Do" list we turned into responsibilities. The "Who You Are" list we turned into requirements. The bonus lines we kept as separate paragraphs maybe as
with [Bonus] prefix. Could also be
. The instruction: Use
- for any list of duties/requirements/benefits. The bonus items are not a list but could be considered requirements. Safer to put them as
- under Requirements with a note "(Bonus)". We'll do that.
Thus Requirements
- will include the bullet points plus bonus items as
- with "(Bonus)" prefix. Now check for any mention of "Occasional Travel" - we included as
- . Now check for any mention of "Strong interpersonal skills to train and communicate effectively with clients via email, on the phone, and face-to-face" - included. Now check for any mention of "Passion for technology and finance" - included. Now check for any mention of