Business Development Associate- Philadelphia
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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 parse the posting.
Key info:
- Employment Type: Full-Time – Business Development Associate/ Manager
- Compensation: $80,000 – $100,000 base salary Plus performance bonus.
- Philadelphia-Based/Primarily remote with in-person requirements:?Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events.
- Who We Are: description.
- Ready to join our team? We offer excellent benefits including Medical, Dental, Vision, and Life insurance, and 401(k), with lots of room for growth.
- About the Role: description.
- Key Responsibilities: list of responsibilities (multiple bullet-like sentences).
- Skills, Education, And Experience: list of qualifications.
- Benefits Provided But Not Limited To The Following: list of benefits.
- Why Join Us? description.
- Core Values: list.
- Philanthropy Opportunities: description.
- New York City Equal Pay Disclaimer: mention salary estimate $65,000 - $70,000 per annum (contradicts earlier compensation). This is likely boilerplate; but it's a specific content about compensation. However we need to decide: Should we include Pay section? The posting states compensation: $80,000 – $100,000 base salary plus performance bonus. Also later a disclaimer says estimated salary $65,000 - $70,000 per annum. That seems contradictory; but we must preserve ALL substantive information. The Pay section should be included if posting actually states them. It does state compensation. So we should include a Pay section with that info. However we must avoid filler like "commensurate with experience". The compensation is specific numbers, so we can include.
- Schedule: Not explicitly stated. There's mention "Willingness to work a flexible schedule, including some evening events". That's about schedule but not explicit schedule like "Monday-Friday 9-5". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Does it state schedule? It mentions willingness to work flexible schedule including some evening events. That's somewhat schedule info. But is that enough to create a Schedule section? It says "Willingness to work a flexible schedule, including some evening events, to build relationships and pursue new business opportunities." That's a statement about schedule expectations. Could be considered schedule info. However we need to decide if we should create a Schedule section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about schedule (flexible schedule, some evening events). So we could include a Schedule section with that info. However we need to avoid filler like "varies" or "TBD". This is specific enough: flexible schedule including some evening events. So we can include.
- Benefits: definitely present.
- About the Role: present.
- Responsibilities: present.
- Skills, Education, And Experience: present.
- Qualifications: maybe same as Skills etc. We could combine.
We need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which headings to use based on content.
We have:
- About the Role: we have a paragraph.
- Responsibilities: we have a list of responsibilities (multiple sentences). Could be turned into
- .
- Requirements: maybe we have "Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events." That's a requirement. Also maybe "0-2 years of experience..." etc. But those are more skills/qualifications. We could treat Requirements as location requirement.
- Qualifications: maybe we have education/experience etc.
- Skills: maybe we have communication, organizational, CRM, etc.
But we should avoid too many thin sections. Prefer a few substantive sections over many thin ones. So we could combine some.
We could have sections: About the Role, Responsibilities, Qualifications (including skills, education, experience), Benefits, Pay, Schedule.
We need to follow the instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not mandatory list. We can choose which to include.
We must not repeat job title as heading. So no heading for Business Development Associate/Manager.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Equal Opportunity Disclaimer, New York City Equal Pay Disclaimer (though it's about pay, but it's a disclaimer; we might keep the pay info but not the disclaimer text). Also remove the "Attention: Infinite Consulting Corp applicants..." etc. Also remove the "Why Join Us?" maybe we can keep as part of About the Role or separate? It's substantive but could be considered boilerplate? It's about culture; maybe we can keep as a paragraph under About the Role or separate section like "Why Join Us?" but not in the heading list. However we could incorporate into About the Role or a separate section like "Company Culture". But the instruction says prefer few substantive sections over many thin ones. So we could merge "Why Join Us?" and "Core Values" and "Philanthropy Opportunities" into a section like "About the Company" or "Culture". But we already have "Who We Are:" earlier. So we could combine Who We Are, Why Join Us?, Core Values, Philanthropy Opportunities into a single section maybe "About the Company". However the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings, but we should follow the pattern. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we need to map content to those headings.
Thus:
- About the role: include the paragraph under "About the Role:" plus maybe the "Who We Are:"? Actually "Who We Are:" is about the company, not the role. But we could treat that as part of About the role? Might be odd. Better to keep About the role as the description of the role. The "Who We Are:" could be omitted or placed elsewhere? But we must preserve ALL substantive information. So we need to include that info somewhere. If we only have headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, we need to fit "Who We Are:" into one of those. Perhaps we can put it under About the role as a preamble? Or we could create a separate heading like "About the Company" but that's not in the list. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed, but we should prefer few substantive sections. Adding a separate "About the Company" section would be another section, increasing count. But we could incorporate that info into About the role section as a brief intro. That would preserve the info without extra heading.
Thus About the role section could contain: "Who We Are: Infinite Consulting Corp..." plus the "About the Role:" paragraph. That would be substantive.
Responsibilities: list of responsibilities.
Requirements: maybe the location requirement: "Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events." Also maybe "Willingness to work a flexible schedule, including some evening events" could go under Schedule instead.
Qualifications: maybe education/experience etc.
Skills: maybe communication, interpersonal, organizational, CRM, etc.
Benefits: list.
Pay: compensation info.
Schedule: flexible schedule including some evening events.
We need to avoid duplication.
Let's extract substantive content:
From posting:
- Employment Type: Full-Time – Business Development Associate/ Manager (we can note as prose maybe not heading).
- Compensation: $80,000 – $100,000 base salary Plus performance bonus.
- Philadelphia-Based/Primarily remote with in-person requirements: Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events.
- Who We Are: Infinite Consulting Corp. is a project, program, and construction management firm established in 2009 specializing in safety management, quality management, project and construction management, and project controls. We proudly provide the highest level of service and support at each phase of our clients' projects. Our client's success is our success. Together we fulfill our goal of “SAFELY BUILDING TOMORROW."
- Ready to join our team? We offer excellent benefits including Medical, Dental, Vision, and Life insurance, and 401(k), with lots of room for growth.
- About the Role: This is a unique opportunity to join our team as a Business Development Associate and help drive the growth of our public sector client base. In this role, you will be responsible for proactively identifying and pursuing new business opportunities, with a focus on building relationships with public agencies and key stakeholders. You will also represent the company at industry events, client meetings, and other business development initiatives. This role is perfect for someone with a “can-do” attitude, industry awareness, and the ambition to grow into a strategic business development leader.
- Key Responsibilities: (list)
1. Identify and pursue new business opportunities within the public sector by building relationships with public agencies, key stakeholders, and target organizations.
2. Ideal candidates will have client-facing experience in AEC consulting or professional services environments, with a strong business development mindset and the ability to help win work and grow client relationships. (This seems more like a qualification but appears under responsibilities; we need to keep as is.)
3. Represent the company at industry events, conferences, and client meetings, building brand awareness, generating leads, and strengthening relationships with potential and existing clients.
4. Conduct market research to stay informed on industry trends, competitor activities, and client needs in the private development sector, providing insights to inform business development efforts.
5. Collaborate with proposal team to respond to RFPs and submit competitive bids for private sector projects, dedicating a significant portion of your time to these efforts.
6. Leverage CRM tools to track and manage your pipeline of opportunities, ensuring follow-up on leads and documenting client interactions.
7. Regularly update the leadership team on progress, challenges, and goals.
8. Develop and execute outreach strategies to foster long-term relationships with private sector clients and identify opportunities for cross-selling and up-selling the full suite of services.
9. Support the development of marketing materials (e.g., case studies, proposals, collateral) to assist in business development and strengthen the company’s position in the market.
- Skills, Education, And Experience:
- 0-2 years
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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 parse the posting. Key info: - Employment Type: Full-Time – Business Development Associate/ Manager - Compensation: $80,000 – $100,000 base salary Plus performance bonus. - Philadelphia-Based/Primarily remote with in-person requirements:?Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events. - Who We Are: description. - Ready to join our team? We offer excellent benefits including Medical, Dental, Vision, and Life insurance, and 401(k), with lots of room for growth. - About the Role: description. - Key Responsibilities: list of responsibilities (multiple bullet-like sentences). - Skills, Education, And Experience: list of qualifications. - Benefits Provided But Not Limited To The Following: list of benefits. - Why Join Us? description. - Core Values: list. - Philanthropy Opportunities: description. - New York City Equal Pay Disclaimer: mention salary estimate $65,000 - $70,000 per annum (contradicts earlier compensation). This is likely boilerplate; but it's a specific content about compensation. However we need to decide: Should we include Pay section? The posting states compensation: $80,000 – $100,000 base salary plus performance bonus. Also later a disclaimer says estimated salary $65,000 - $70,000 per annum. That seems contradictory; but we must preserve ALL substantive information. The Pay section should be included if posting actually states them. It does state compensation. So we should include a Pay section with that info. However we must avoid filler like "commensurate with experience". The compensation is specific numbers, so we can include. - Schedule: Not explicitly stated. There's mention "Willingness to work a flexible schedule, including some evening events". That's about schedule but not explicit schedule like "Monday-Friday 9-5". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Does it state schedule? It mentions willingness to work flexible schedule including some evening events. That's somewhat schedule info. But is that enough to create a Schedule section? It says "Willingness to work a flexible schedule, including some evening events, to build relationships and pursue new business opportunities." That's a statement about schedule expectations. Could be considered schedule info. However we need to decide if we should create a Schedule section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about schedule (flexible schedule, some evening events). So we could include a Schedule section with that info. However we need to avoid filler like "varies" or "TBD". This is specific enough: flexible schedule including some evening events. So we can include. - Benefits: definitely present. - About the Role: present. - Responsibilities: present. - Skills, Education, And Experience: present. - Qualifications: maybe same as Skills etc. We could combine. We need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which headings to use based on content. We have: - About the Role: we have a paragraph. - Responsibilities: we have a list of responsibilities (multiple sentences). Could be turned into
- .
- Requirements: maybe we have "Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events." That's a requirement. Also maybe "0-2 years of experience..." etc. But those are more skills/qualifications. We could treat Requirements as location requirement.
- Qualifications: maybe we have education/experience etc.
- Skills: maybe we have communication, organizational, CRM, etc.
But we should avoid too many thin sections. Prefer a few substantive sections over many thin ones. So we could combine some.
We could have sections: About the Role, Responsibilities, Qualifications (including skills, education, experience), Benefits, Pay, Schedule.
We need to follow the instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not mandatory list. We can choose which to include. We must not repeat job title as heading. So no heading for Business Development Associate/Manager. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Equal Opportunity Disclaimer, New York City Equal Pay Disclaimer (though it's about pay, but it's a disclaimer; we might keep the pay info but not the disclaimer text). Also remove the "Attention: Infinite Consulting Corp applicants..." etc. Also remove the "Why Join Us?" maybe we can keep as part of About the Role or separate? It's substantive but could be considered boilerplate? It's about culture; maybe we can keep as a paragraph under About the Role or separate section like "Why Join Us?" but not in the heading list. However we could incorporate into About the Role or a separate section like "Company Culture". But the instruction says prefer few substantive sections over many thin ones. So we could merge "Why Join Us?" and "Core Values" and "Philanthropy Opportunities" into a section like "About the Company" or "Culture". But we already have "Who We Are:" earlier. So we could combine Who We Are, Why Join Us?, Core Values, Philanthropy Opportunities into a single section maybe "About the Company". However the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings, but we should follow the pattern. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we need to map content to those headings. Thus: - About the role: include the paragraph under "About the Role:" plus maybe the "Who We Are:"? Actually "Who We Are:" is about the company, not the role. But we could treat that as part of About the role? Might be odd. Better to keep About the role as the description of the role. The "Who We Are:" could be omitted or placed elsewhere? But we must preserve ALL substantive information. So we need to include that info somewhere. If we only have headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, we need to fit "Who We Are:" into one of those. Perhaps we can put it under About the role as a preamble? Or we could create a separate heading like "About the Company" but that's not in the list. However the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed, but we should prefer few substantive sections. Adding a separate "About the Company" section would be another section, increasing count. But we could incorporate that info into About the role section as a brief intro. That would preserve the info without extra heading. Thus About the role section could contain: "Who We Are: Infinite Consulting Corp..." plus the "About the Role:" paragraph. That would be substantive. Responsibilities: list of responsibilities. Requirements: maybe the location requirement: "Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events." Also maybe "Willingness to work a flexible schedule, including some evening events" could go under Schedule instead. Qualifications: maybe education/experience etc. Skills: maybe communication, interpersonal, organizational, CRM, etc. Benefits: list. Pay: compensation info. Schedule: flexible schedule including some evening events. We need to avoid duplication. Let's extract substantive content: From posting: - Employment Type: Full-Time – Business Development Associate/ Manager (we can note as prose maybe not heading). - Compensation: $80,000 – $100,000 base salary Plus performance bonus. - Philadelphia-Based/Primarily remote with in-person requirements: Qualified applicants should reside in the Philadelphia area to facilitate client site visits and attendance at events. - Who We Are: Infinite Consulting Corp. is a project, program, and construction management firm established in 2009 specializing in safety management, quality management, project and construction management, and project controls. We proudly provide the highest level of service and support at each phase of our clients' projects. Our client's success is our success. Together we fulfill our goal of “SAFELY BUILDING TOMORROW." - Ready to join our team? We offer excellent benefits including Medical, Dental, Vision, and Life insurance, and 401(k), with lots of room for growth. - About the Role: This is a unique opportunity to join our team as a Business Development Associate and help drive the growth of our public sector client base. In this role, you will be responsible for proactively identifying and pursuing new business opportunities, with a focus on building relationships with public agencies and key stakeholders. You will also represent the company at industry events, client meetings, and other business development initiatives. This role is perfect for someone with a “can-do” attitude, industry awareness, and the ambition to grow into a strategic business development leader. - Key Responsibilities: (list) 1. Identify and pursue new business opportunities within the public sector by building relationships with public agencies, key stakeholders, and target organizations. 2. Ideal candidates will have client-facing experience in AEC consulting or professional services environments, with a strong business development mindset and the ability to help win work and grow client relationships. (This seems more like a qualification but appears under responsibilities; we need to keep as is.) 3. Represent the company at industry events, conferences, and client meetings, building brand awareness, generating leads, and strengthening relationships with potential and existing clients. 4. Conduct market research to stay informed on industry trends, competitor activities, and client needs in the private development sector, providing insights to inform business development efforts. 5. Collaborate with proposal team to respond to RFPs and submit competitive bids for private sector projects, dedicating a significant portion of your time to these efforts. 6. Leverage CRM tools to track and manage your pipeline of opportunities, ensuring follow-up on leads and documenting client interactions. 7. Regularly update the leadership team on progress, challenges, and goals. 8. Develop and execute outreach strategies to foster long-term relationships with private sector clients and identify opportunities for cross-selling and up-selling the full suite of services. 9. Support the development of marketing materials (e.g., case studies, proposals, collateral) to assist in business development and strengthen the company’s position in the market. - Skills, Education, And Experience: - 0-2 years