Engineering Manager - New York
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 include sections only if they have real content. The posting includes: About Us, About You, Responsibilities, Must Haves (which is like Requirements/Qualifications), Additional Information (some legal stuff), Pay ($170,000 - $215,000 a year). Also mention "Periodically work outside standard business hours..." which could be schedule? It's not a schedule but mention of occasional outside hours. Not a defined schedule. Probably we shouldn't create Schedule section unless explicit schedule. The posting does not give explicit schedule like full-time, hours. So we skip Schedule.
Benefits: not mentioned. So skip Benefits.
Pay: yes we have salary range. So include Pay section.
We need to remove EEO boilerplate, legal stuff like "Additional Information This job description is intended..." and "Equal Opportunity Employer" etc. Also remove "We may use artificial intelligence (AI) tools..." maybe that's not boilerplate? It's about hiring process; could be considered part of Additional Information but it's not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools note is not exactly EEO but could be considered part of hiring process; not sure if we should keep. It's not application instructions; it's about process. Might keep as part of Additional Information? But Additional Information also includes the at-will employment statement etc. Those are legal boilerplate; we should remove them. The instruction says remove legal/EEO boilerplate. So we should drop the Additional Information paragraph that includes at-will, exempt classification, etc. Also drop the Equal Opportunity Employer paragraph. Also drop the AI tools note? It's not EEO but maybe considered part of hiring process; not explicitly prohibited. However it's not a core job description; could be considered boilerplate but not explicitly listed. Safer to keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI note is not exactly those categories; it's about hiring process. Might be okay to keep. But we could also drop it as it's not substantive about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The AI note is not substantive about the role; it's about hiring process. Could be considered boilerplate but not explicitly listed. I'd lean to keep it? However the instruction says "Prefer a few substantive sections over many thin ones." If we keep it, we might need a section for Additional Information. But that section would be thin (just a note about AI). Might be better to drop it as it's not essential. The instruction says remove duplicated lines and application instructions. The AI note is not application instructions but could be considered part of hiring process. I'd drop it to keep sections substantive.
Thus we will have sections: About Us, About You, Responsibilities, Requirements (or Qualifications), Pay.
We need to use
for each section heading.
Inside sections, we need to use
for prose, and
- for lists.
We need to preserve all substantive information. Let's extract content.
About Us paragraph: "Versana is an industry-backed data and technology company on a mission to make the syndicated loan market better. By digitally capturing agent banks’ data on a real-time basis and centralizing it onto a single platform, Versana provides unprecedented transparency into loan level details and portfolio positions, bringing efficiency and velocity to the entire market. Through our platform, participants can rest assured they are accessing the loan market’s most credible source of deal information."
About You paragraph: "The Engineering Manager is a strategic and operational leader responsible for driving high-performing engineering teams, enabling technical excellence, and delivering high-impact products and platforms. This role partners closely with Product, Architecture, and cross-functional stakeholders to define technical strategy, mature engineering practices, and ensure predictable, high-quality delivery. The ideal candidate is both a strong people manager and a seasoned technologist who can elevate engineering capabilities across the organization."
Responsibilities: multiple bullet points under headings: People Leadership & Team Development, Technical Leadership & Execution, Operational Excellence, Stakeholder & Cross-Functional Collaboration, plus "Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve." and "Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases."
We need to turn these into list items. The headings within responsibilities could be treated as list items with subpoints? The instruction: Use
- for any list of duties/requirements/benefits. So we can make a
with each responsibility as - . For sub-bullets, we could nest
inside - . But we need to preserve all detail. Let's capture each bullet.
People Leadership & Team Development:
- Lead, mentor, and develop individual contributors across multiple teams.
- Build a culture of ownership, accountability, collaboration, and continuous improvement.
- Drive career growth frameworks, performance management, and succession planning.
- Foster an inclusive, high-trust environment that supports well-being and sustained productivity.
Technical Leadership & Execution:
- Provide strategic technical direction in partnership with architecture and product leadership.
- Guide teams in designing scalable, secure, and high-quality systems aligned with long-term business goals.
- Champion engineering best practices, including code quality, observability, automation, and DevOps maturity.
- Lead efforts to modernize technology, simplify architecture, and reduce technical debt.
Operational Excellence:
- Establish and monitor KPIs for engineering performance, quality, and reliability.
- Lead continuous improvement initiatives across the engineering organization.
- Optimize team structures, resource allocations, and processes for scale.
- Oversee vendor or contract engineering relationships when relevant.
Stakeholder & Cross-Functional Collaboration:
- Act as a senior partner to Product, Design, Data, Security, and Infrastructure teams.
- Communicate technical decisions, trade-offs, and risks clearly to executive leadership.
- Ensure engineering alignment with organizational goals and compliance requirements.
Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve.
Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases.
We could combine the last two as list items.
Now Must Haves (Requirements):
- 8+ years of engineering experience
- Proven track record scaling engineering teams and delivering complex, high-impact software systems.
- Strong technical foundation in software architecture, cloud technologies, and modern development practices.
- Demonstrated ability to balance technical depth with strategic leadership.
- Exceptional communication, organizational, and stakeholder-management skills.
- Experience in a matrix organization with both direct and dotted-line structures.
- Background working in Agile environments—Scrum, Kanban, or hybrid models.
- Familiarity with platform engineering, developer experience tooling, or productivity enablement.
We could also include "Additional Information" but we decided to drop.
Pay: "$170,000 - $215,000 a year"
We need to output HTML fragment only.
Thus:
About Us
Versana is an industry-backed data and technology company on a mission to make the syndicated loan market better. By digitally capturing agent banks’ data on a real-time basis and centralizing it onto a single platform, Versana provides unprecedented transparency into loan level details and portfolio positions, bringing efficiency and velocity to the entire market. Through our platform, participants can rest assured they are accessing the loan market’s most credible source of deal information.
About You
The Engineering Manager is a strategic and operational leader responsible for driving high-performing engineering teams, enabling technical excellence, and delivering high-impact products and platforms. This role partners closely with Product, Architecture, and cross-functional stakeholders to define technical strategy, mature engineering practices, and ensure predictable, high-quality delivery. The ideal candidate is both a strong people manager and a seasoned technologist who can elevate engineering capabilities across the organization.
Responsibilities
- People Leadership & Team Development
- Lead, mentor, and develop individual contributors across multiple teams.
- Build a culture of ownership, accountability, collaboration, and continuous improvement.
- Drive career growth frameworks, performance management, and succession planning.
- Foster an inclusive, high-trust environment that supports well-being and sustained productivity.
- Technical Leadership & Execution
- Provide strategic technical direction in partnership with architecture and product leadership.
- Guide teams in designing scalable, secure, and high-quality systems aligned with long-term business goals.
- Champion engineering best practices, including code quality, observability, automation, and DevOps maturity.
- Lead efforts to modernize technology, simplify architecture, and reduce technical debt.
- Operational Excellence
- Establish and monitor KPIs for engineering performance, quality, and reliability.
- Lead continuous improvement initiatives across the engineering organization.
- Optimize team structures, resource allocations, and processes for scale.
- Oversee vendor or contract engineering relationships when relevant.
- Stakeholder & Cross-Functional Collaboration
- Act as a senior partner to Product, Design, Data, Security, and Infrastructure teams.
- Communicate technical decisions, trade-offs, and risks clearly to executive leadership.
- Ensure engineering alignment with organizational goals and compliance requirements.
- Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve.
- Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases.
Requirements
- 8+ years of engineering experience
- Proven track record scaling engineering teams and delivering complex, high-impact software systems.
- Strong technical foundation in software architecture, cloud technologies, and modern development practices.
- Demonstrated ability to balance technical depth with strategic leadership.
- Exceptional communication, organizational, and stakeholder-management skills.
- Experience in a matrix organization with both direct and dotted-line structures.
- Background working in Agile environments—Scrum, Kanban, or hybrid models.
- Familiarity with platform engineering, developer experience tooling, or productivity enablement.
Pay
$170,000 - $215,000 a year
We need to ensure no extra text. Output only HTML.
Check for any leftover boilerplate: we removed EEO, legal, AI note, etc.
Make sure we didn't include
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 include sections only if they have real content. The posting includes: About Us, About You, Responsibilities, Must Haves (which is like Requirements/Qualifications), Additional Information (some legal stuff), Pay ($170,000 - $215,000 a year). Also mention "Periodically work outside standard business hours..." which could be schedule? It's not a schedule but mention of occasional outside hours. Not a defined schedule. Probably we shouldn't create Schedule section unless explicit schedule. The posting does not give explicit schedule like full-time, hours. So we skip Schedule. Benefits: not mentioned. So skip Benefits. Pay: yes we have salary range. So include Pay section. We need to remove EEO boilerplate, legal stuff like "Additional Information This job description is intended..." and "Equal Opportunity Employer" etc. Also remove "We may use artificial intelligence (AI) tools..." maybe that's not boilerplate? It's about hiring process; could be considered part of Additional Information but it's not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools note is not exactly EEO but could be considered part of hiring process; not sure if we should keep. It's not application instructions; it's about process. Might keep as part of Additional Information? But Additional Information also includes the at-will employment statement etc. Those are legal boilerplate; we should remove them. The instruction says remove legal/EEO boilerplate. So we should drop the Additional Information paragraph that includes at-will, exempt classification, etc. Also drop the Equal Opportunity Employer paragraph. Also drop the AI tools note? It's not EEO but maybe considered part of hiring process; not explicitly prohibited. However it's not a core job description; could be considered boilerplate but not explicitly listed. Safer to keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI note is not exactly those categories; it's about hiring process. Might be okay to keep. But we could also drop it as it's not substantive about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The AI note is not substantive about the role; it's about hiring process. Could be considered boilerplate but not explicitly listed. I'd lean to keep it? However the instruction says "Prefer a few substantive sections over many thin ones." If we keep it, we might need a section for Additional Information. But that section would be thin (just a note about AI). Might be better to drop it as it's not essential. The instruction says remove duplicated lines and application instructions. The AI note is not application instructions but could be considered part of hiring process. I'd drop it to keep sections substantive. Thus we will have sections: About Us, About You, Responsibilities, Requirements (or Qualifications), Pay. We need to use
for each section heading. Inside sections, we need to use
for prose, and
- for lists.
We need to preserve all substantive information. Let's extract content.
About Us paragraph: "Versana is an industry-backed data and technology company on a mission to make the syndicated loan market better. By digitally capturing agent banks’ data on a real-time basis and centralizing it onto a single platform, Versana provides unprecedented transparency into loan level details and portfolio positions, bringing efficiency and velocity to the entire market. Through our platform, participants can rest assured they are accessing the loan market’s most credible source of deal information."
About You paragraph: "The Engineering Manager is a strategic and operational leader responsible for driving high-performing engineering teams, enabling technical excellence, and delivering high-impact products and platforms. This role partners closely with Product, Architecture, and cross-functional stakeholders to define technical strategy, mature engineering practices, and ensure predictable, high-quality delivery. The ideal candidate is both a strong people manager and a seasoned technologist who can elevate engineering capabilities across the organization."
Responsibilities: multiple bullet points under headings: People Leadership & Team Development, Technical Leadership & Execution, Operational Excellence, Stakeholder & Cross-Functional Collaboration, plus "Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve." and "Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases."
We need to turn these into list items. The headings within responsibilities could be treated as list items with subpoints? The instruction: Use
- for any list of duties/requirements/benefits. So we can make a
- with each responsibility as
- . For sub-bullets, we could nest
- inside
- . But we need to preserve all detail. Let's capture each bullet.
People Leadership & Team Development:
- Lead, mentor, and develop individual contributors across multiple teams.
- Build a culture of ownership, accountability, collaboration, and continuous improvement.
- Drive career growth frameworks, performance management, and succession planning.
- Foster an inclusive, high-trust environment that supports well-being and sustained productivity.
Technical Leadership & Execution:
- Provide strategic technical direction in partnership with architecture and product leadership.
- Guide teams in designing scalable, secure, and high-quality systems aligned with long-term business goals.
- Champion engineering best practices, including code quality, observability, automation, and DevOps maturity.
- Lead efforts to modernize technology, simplify architecture, and reduce technical debt.
Operational Excellence:
- Establish and monitor KPIs for engineering performance, quality, and reliability.
- Lead continuous improvement initiatives across the engineering organization.
- Optimize team structures, resource allocations, and processes for scale.
- Oversee vendor or contract engineering relationships when relevant.
Stakeholder & Cross-Functional Collaboration:
- Act as a senior partner to Product, Design, Data, Security, and Infrastructure teams.
- Communicate technical decisions, trade-offs, and risks clearly to executive leadership.
- Ensure engineering alignment with organizational goals and compliance requirements.
Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve.
Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases.
We could combine the last two as list items.
Now Must Haves (Requirements):
- 8+ years of engineering experience
- Proven track record scaling engineering teams and delivering complex, high-impact software systems.
- Strong technical foundation in software architecture, cloud technologies, and modern development practices.
- Demonstrated ability to balance technical depth with strategic leadership.
- Exceptional communication, organizational, and stakeholder-management skills.
- Experience in a matrix organization with both direct and dotted-line structures.
- Background working in Agile environments—Scrum, Kanban, or hybrid models.
- Familiarity with platform engineering, developer experience tooling, or productivity enablement.
We could also include "Additional Information" but we decided to drop.
Pay: "$170,000 - $215,000 a year"
We need to output HTML fragment only.
Thus:
About Us
Versana is an industry-backed data and technology company on a mission to make the syndicated loan market better. By digitally capturing agent banks’ data on a real-time basis and centralizing it onto a single platform, Versana provides unprecedented transparency into loan level details and portfolio positions, bringing efficiency and velocity to the entire market. Through our platform, participants can rest assured they are accessing the loan market’s most credible source of deal information.
About You
The Engineering Manager is a strategic and operational leader responsible for driving high-performing engineering teams, enabling technical excellence, and delivering high-impact products and platforms. This role partners closely with Product, Architecture, and cross-functional stakeholders to define technical strategy, mature engineering practices, and ensure predictable, high-quality delivery. The ideal candidate is both a strong people manager and a seasoned technologist who can elevate engineering capabilities across the organization.
Responsibilities
- People Leadership & Team Development
- Lead, mentor, and develop individual contributors across multiple teams.
- Build a culture of ownership, accountability, collaboration, and continuous improvement.
- Drive career growth frameworks, performance management, and succession planning.
- Foster an inclusive, high-trust environment that supports well-being and sustained productivity.
- Technical Leadership & Execution
- Provide strategic technical direction in partnership with architecture and product leadership.
- Guide teams in designing scalable, secure, and high-quality systems aligned with long-term business goals.
- Champion engineering best practices, including code quality, observability, automation, and DevOps maturity.
- Lead efforts to modernize technology, simplify architecture, and reduce technical debt.
- Operational Excellence
- Establish and monitor KPIs for engineering performance, quality, and reliability.
- Lead continuous improvement initiatives across the engineering organization.
- Optimize team structures, resource allocations, and processes for scale.
- Oversee vendor or contract engineering relationships when relevant.
- Stakeholder & Cross-Functional Collaboration
- Act as a senior partner to Product, Design, Data, Security, and Infrastructure teams.
- Communicate technical decisions, trade-offs, and risks clearly to executive leadership.
- Ensure engineering alignment with organizational goals and compliance requirements.
- Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve.
- Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases.
Requirements
- 8+ years of engineering experience
- Proven track record scaling engineering teams and delivering complex, high-impact software systems.
- Strong technical foundation in software architecture, cloud technologies, and modern development practices.
- Demonstrated ability to balance technical depth with strategic leadership.
- Exceptional communication, organizational, and stakeholder-management skills.
- Experience in a matrix organization with both direct and dotted-line structures.
- Background working in Agile environments—Scrum, Kanban, or hybrid models.
- Familiarity with platform engineering, developer experience tooling, or productivity enablement.
Pay
$170,000 - $215,000 a year
We need to ensure no extra text. Output only HTML. Check for any leftover boilerplate: we removed EEO, legal, AI note, etc. Make sure we didn't include - People Leadership & Team Development
- . But we need to preserve all detail. Let's capture each bullet.
People Leadership & Team Development:
- Lead, mentor, and develop individual contributors across multiple teams.
- Build a culture of ownership, accountability, collaboration, and continuous improvement.
- Drive career growth frameworks, performance management, and succession planning.
- Foster an inclusive, high-trust environment that supports well-being and sustained productivity.
Technical Leadership & Execution:
- Provide strategic technical direction in partnership with architecture and product leadership.
- Guide teams in designing scalable, secure, and high-quality systems aligned with long-term business goals.
- Champion engineering best practices, including code quality, observability, automation, and DevOps maturity.
- Lead efforts to modernize technology, simplify architecture, and reduce technical debt.
Operational Excellence:
- Establish and monitor KPIs for engineering performance, quality, and reliability.
- Lead continuous improvement initiatives across the engineering organization.
- Optimize team structures, resource allocations, and processes for scale.
- Oversee vendor or contract engineering relationships when relevant.
Stakeholder & Cross-Functional Collaboration:
- Act as a senior partner to Product, Design, Data, Security, and Infrastructure teams.
- Communicate technical decisions, trade-offs, and risks clearly to executive leadership.
- Ensure engineering alignment with organizational goals and compliance requirements.
Additional duties and responsibilities as may be reasonably assigned from time to time as operational needs evolve.
Periodically work outside standard business hours, such as during infrastructure upgrades and/or releases.
We could combine the last two as list items.
Now Must Haves (Requirements):
- 8+ years of engineering experience
- Proven track record scaling engineering teams and delivering complex, high-impact software systems.
- Strong technical foundation in software architecture, cloud technologies, and modern development practices.
- Demonstrated ability to balance technical depth with strategic leadership.
- Exceptional communication, organizational, and stakeholder-management skills.
- Experience in a matrix organization with both direct and dotted-line structures.
- Background working in Agile environments—Scrum, Kanban, or hybrid models.
- Familiarity with platform engineering, developer experience tooling, or productivity enablement.
We could also include "Additional Information" but we decided to drop.
Pay: "$170,000 - $215,000 a year"
We need to output HTML fragment only.
Thus:
- . For sub-bullets, we could nest
- for any list of duties/requirements/benefits. So we can make a