AVP, Software & AI Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings.
We have:
- About the role: could be "WHY THIS ROLE IS VALUABLE" description. That's about role. So we can have About the role
with paragraph(s) summarizing that section.
- Responsibilities: "Key Responsibilities" list.
- Requirements/Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into Requirements section? The instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have Requirements (maybe Required Qualifications) and Preferred Qualifications could be under Skills? Or we could have Qualifications heading for required, and Skills for preferred? But better to follow typical: Requirements (required qualifications) and Qualifications (maybe preferred). However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to include.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements: we have Required Qualifications (list). So we can put under Requirements
.
- Qualifications: we have Preferred Qualifications (list). Could put under Qualifications
.
- Skills: maybe we could extract skills from responsibilities? But we already have qualifications. Could also put technical skills under Skills. But we might not need Skills if we already covered. However they said prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred into Requirements and Qualifications? Or we could have Requirements (required) and Skills (preferred). But they'd like to see sections only when posting has real specific content. We have both required and preferred, so we can include both.
- Benefits: we have Benefits section and also Perks for You (which includes benefits like health insurance, 401k, work-life balance). So we can include Benefits heading with combined content.
- Pay: we have Base Compensation Range and Total Direct Compensation (bonus). So we can include Pay heading.
- Schedule: we have Hybrid Work Policy, Productivity Hours, Summer Fridays, Work From Anywhere Month. That's schedule/flexibility. So we can include Schedule heading.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, privacy notice, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format as lists or paragraphs.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Who We Are section: description of company. Could be considered "About the company" but not required heading. The instruction says use headings for sections like About the role, Responsibilities, etc. Not required to include About the company. But we could include it under About the role? Actually About the role is separate. The "Who We Are" is company overview; maybe we could include it as a paragraph before sections? Not required but we can include as a
maybe under no heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow that pattern. Could include a About the company
but not in list. Safer to include it as a
without heading? But they said use
for section headings (e.g. About the role, ...). It implies we should use those headings for sections; we can also have other headings but not required. However to be safe, we can include a About the company
as it's substantive. But they didn't list that as example; but they said "e.g." meaning examples, not exhaustive. So we can include.
But we need to preserve all substantive information. So we should include the "Who We Are" paragraph(s). Also "What We Value: Our Culture" etc. That's also substantive. Could be under a heading like "Our Culture" or "Values". Not in examples but we could include as Our Culture
. However they said prefer a few substantive sections over many thin ones. So maybe we combine culture into About the role? Not ideal.
Better to follow the instruction: Use headings for the listed categories; we can also include other headings if needed but they'd be thin. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections. It doesn't forbid others, but we should aim to use those.
Thus we can map:
- About the role: combine "WHY THIS ROLE IS VALUABLE" plus maybe "Who We Are"? Actually About the role should describe the role, not company. So we put the WHY THIS ROLE IS VALUABLE content there.
- Responsibilities: Key Responsibilities.
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe we can extract skills from responsibilities? But we already have qualifications. Could put technical skills under Skills: e.g., Python, Azure, Databricks, Snowflake, etc. But that would duplicate. Might be okay but risk of duplication. However we must preserve all substantive information; duplication is okay as long as we don't lose info. But we should avoid unnecessary duplication? Not prohibited. However they said do not invent or summarize away detail. Duplication is not summarizing away; it's repeating. Might be okay but could be considered filler? Not sure.
Better to not create Skills section if we don't have distinct skill list beyond qualifications. However we could treat "Skills" as the technical skills mentioned in responsibilities and qualifications. But we already have them in Requirements and Qualifications. Could combine them under Skills and not have Requirements/Qualifications? But then we lose distinction between required and preferred. The instruction didn't require that distinction; just need to preserve all substantive info. So we could have a single Skills section that lists all required and preferred qualifications. But then we lose the labeling of required vs preferred. However the info is still there (the items). Might be acceptable.
But they gave examples of headings: Requirements, Qualifications, Skills. So they expect possibly separate sections for each. Let's follow that: Requirements (required), Qualifications (preferred), Skills (maybe technical skills like Python, Azure, etc). But we already have technical skills in those lists. Could still create Skills section summarizing the technical competencies: e.g., "Python, Azure, Databricks, Snowflake, Docker, Kubernetes, CI/CD, REST APIs, event-driven architecture, serverless, LLMs, RAG, AI/ML, monitoring, observability". That would be a summary, which might be considered summarizing away detail? It's extracting from the lists, not inventing. It's okay as long as we preserve all detail? If we create a summary, we might lose some nuance like "7+ years of experience". That's not a skill but a requirement. So we need to keep that somewhere. So better to keep Requirements and Qualifications sections as they are, and maybe omit Skills to avoid thin section. Since they said prefer a few substantive sections over many thin ones, we can skip Skills if not needed.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Also maybe include About the company and Our Culture as paragraphs without headings? Could include them as
before sections. But we need to preserve all substantive information: Who We Are, What We Value (Our Culture), Grow your career with us, etc. That's a lot. If we omit headings for them, we can still include them as paragraphs. That's fine. Let's extract each piece. **Who We Are** paragraph(s): "Revantage, a Blackstone Real Estate portfolio company, is a global provider of corporate services. With a corporate purpose of ‘In Pursuit of Better,’ Revantage delivers value-added services and world-class talent for Blackstone Real Estate portfolio companies, spanning diverse asset classes, including residential, logistics, office, hospitality and retail sectors. Headquartered in Chicago, the company’s footprint extends across North America, Europe and Asia Pacific. Rooted in a commitment to collaboration and inclusivity, Revantage goes beyond traditional corporate services and acts as a trusted partner. Across offerings that include finance, technology, human resources and operations, Revantage proactively anticipates stakeholder needs, recruits exceptional talent and enables its business partners to thrive." **What We Value: Our Culture**: "Our people are our most important asset, enabling Blackstone portfolio companies and investments to scale and thrive. Together, we foster a workplace where everyone can be themselves, enabling them to do their best work. At Revantage, we have exceptional people who live our values and help us pursue better every day. We offer dynamic and meaningful work, competitive compensation, benefits and flexibility. We listen and take action to ensure our organization evolves to reflect our employees’ voices and support an inclusive culture. Our demonstrated commitment to our people and collaborative culture have earned us numerous awards as a top employer. Our culture is built on our shared core values and commitment to be: Learners – We learn from our challenges and successesLeaders – We commit to continuous improvementEnthusiasts – We face challenges with optimism and believe anything is possibleAchievers – We expect high standards for ourselves and enable the success of our teamsPartners – We deliver value and positive impact to our partners Grow your career with us. As a member of our team, you'll gain hands-on experience in the real estate industry and benefit from a supportive environment that fosters personal and professional growth." Note there is no spacing between some items (e.g., "Learners – We learn from our challenges and successesLeaders –"). We'll keep as is. **WHY THIS ROLE IS VALUABLE** (About the role): "The AVP, Forward Deployed Engineer is responsible for partnering directly with business stakeholders, portfolio companies, and technology teams to design and deliver scalable AI, data, and cloud solutions that solve complex business challenges. This role sits at the intersection of software engineering, data engineering, and consulting, translating business requirements into production-ready solutions that drive measurable outcomes. The ideal candidate combines strong Python engineering expertise with experience building modern cloud-native solutions on Azure. They are comfortable working directly with end users, rapidly prototyping solutions, developing scalable data pipelines, and deploying AI-enabled applications using modern data platforms such as Databricks and Snowflake." **Required Qualifications** (list): - Bachelor's degree in Computer Science, Engineering, Data Science, or related field - 7+ years of experience in software, data, or platform engineering - Advanced Python development experience with strong software engineering fundamentals - Experience designing and deploying cloud-native solutions in Azure - Experience building and supporting distributed, scalable applications and microservices - Experience developing and consuming REST APIs - Strong understanding of event-driven architectures and serverless computing - Experience with CI/CD pipelines, automated testing, and DevOps best practices - Strong communication and stakeholder management skills - Proven ability to translate business requirements into technical solutions **Preferred Qualifications** (list): - Hands-on experience with Databricks and modern data engineering frameworks - Experience with Snowflake data warehousing and analytics platforms - Experience building AI/ML-enabled applications and solutions - Familiarity with Large Language