Engineering Manager

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements/Qualifications (What You'll Bring), Benefits? There's mention of compensation: "The all-in total compensation for this role is $170,500 and $176,000, and is specific to the United States. A reasonable estimate of the base salary range would be $155,000 - $160,000 plus applicable bonus/benefit offerings, etc." Also later: "The Pay Range For This Role Is 155,000 - 160,000 USD per year (New York, NY)". So we have pay info. Should we include Pay section? Yes, because posting states pay range. Should we include Benefits? Not explicit benefits listed, only mention of bonus/benefit offerings but not specifics. So we should not create Benefits section unless specific benefits listed. No schedule info. So sections: About the role (maybe we can use "About the role" heading). Responsibilities (What You'll Do). Requirements (What You'll Bring). Pay (compensation). Possibly also "Qualifications" but we can combine Requirements and Qualifications. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. So we will have About the role, Responsibilities, Requirements, Pay. Possibly also Skills? Not separate. We'll embed lists where appropriate. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, scam warning, visa sponsorship, etc. Also remove navigation, cookie, legal. Also remove "To learn more about Comply, visit comply.com" maybe part of About Us? That's boilerplate? It's part of "Who Are We". Might be considered company description; we can keep as part of About the role? Actually "Who Are We" is company overview; we could include that as part of About the role? The instruction: "About the role" heading for section headings. The company overview could be placed under About the role? Might be better to include a short paragraph under About the role describing the role and company? The posting includes "Who Are We Comply is the leading provider..." That's company overview. We should preserve that info. Where to put? Could be under About the role as introductory paragraph before responsibilities. Or we could create a separate section like "About the company" but not in allowed headings. So we incorporate into About the role section. We need to output only HTML fragment, no markdown fences. Let's extract content: Company overview: "Who Are We Comply is the leading provider of compliance SaaS and consulting services for the global financial services sector. With more than 5,000 clients and hundreds of employees across the globe, Comply empowers Chief Compliance Officers and their teams to proactively manage regulatory obligations, mitigate risk, and scale with efficiency and confidence. Comply serves thousands of global financial services clients including broker-dealers, insurers, investment banks, private funds, RIAs, and wealth managers who rely on Comply offerings to power their compliance programs. To learn more about Comply, visit comply.com" We can keep that as a paragraph under About the role. About the role paragraph: "Comply is looking for an Engineering Manager to lead and grow a high-performing software engineering team, shipping reliable, scalable software that powers compliance programs for thousands of financial services clients worldwide. In this role, you’ll own both the people and the technical direction of your team, partnering closely with product, QA, and business stakeholders to deliver against an ambitious roadmap. You’ll report to the Senior Director of Software Engineering and lead engineers based in India. Flexibility for cross-timezone collaboration is part of the rhythm, balanced by Comply’s commitment to sustainable, predictable working hours for managers. You’ll love this role if you’re energized by growing engineers, thrive in a fast-moving product environment, and want to shape the architecture of a cloud-native SaaS platform at real scale." We can combine with company overview maybe as one About the role section. Responsibilities (What You'll Do): list items: - Lead a cross-functional engineering team, including QA and offshore engineers in India. - Own everything from sprint planning and code review through deployment and production reliability. - Set and hold the technical bar by establishing coding standards, conduct meaningful code reviews, and keep the team’s work secure, scalable, and aligned to architectural best practices. - Partner with product and business stakeholders to define and prioritize delivery, ensuring every sprint connects back to customer value and product strategy. - Build and sustain a team culture of ownership, inclusion, continuous learning, and craft where engineers feel accountable and supported in equal measure. - Coach and develop engineers at all levels, run meaningful 1:1s, manage performance, and partner with recruiting to bring in the right strategic talent. - Drive the technical roadmap by balancing near-term delivery commitments with long-term platform health, innovation, and technical debt reduction. - Champion modern engineering practices across the team: CI/CD pipelines, agile methodologies, version control (Bitbucket), and AI-assisted development tools. - Collaborate across business units to provide engineering perspective on product and commercial decisions and contribute to the broader direction of Comply’s software platform. We need to preserve details exactly; we can keep as list items. What Success Looks Like In Your First 90 Days: This is maybe a subsection but not required heading; we could incorporate into Responsibilities or maybe as a separate section? Not in allowed headings; we could treat as part of Responsibilities or maybe as a separate "Expectations" but not needed. The instruction: include a section ONLY when posting has real, specific content for it. This content is specific; but we don't have a heading like "Success Metrics". Could we create a section "What Success Looks Like"? Not in allowed list. Better to incorporate into Responsibilities or maybe as a separate paragraph under Responsibilities. We'll keep as a paragraph under Responsibilities after the list? Might be okay. But we must not invent headings. So we can add a paragraph after the list: "What Success Looks Like In Your First 90 Days: ..." as prose. Now Requirements (What You'll Bring): list: Must-have: - 5+ years of engineering leadership experience, including direct people management: coaching, performance management, and team development. - Deep full-stack development background, with particular strength in C# and .NET. - Proven ability to lead through ambiguity — you can set clear goals, drive accountability, and build toward a long-term technical roadmap without waiting for perfect information. - Strong communication skills: you translate fluently between technical and non-technical audiences and can hold your own in strategic discussions with senior leadership. - Experience building and deploying scaled platforms and applications in cloud environments. - Proficiency with modern engineering practices: CI/CD pipelines, agile methodologies, and version control systems (e.g., Bitbucket). - Familiarity with relational and NoSQL databases (SQL Server, MySQL, Postgres, Elasticsearch). - Bachelor’s degree in Computer Science, Engineering, Information Technology, or a related field — or equivalent experience. Nice-to-have: - Experience in financial services or other regulated industries. - Cloud certifications: AWS (preferred), Azure, or GCP. - Hands-on experience with Kubernetes, Redis, or Jenkins. - Familiarity with AI-assisted development tools such as GitHub Copilot, Cursor.ai, or AWS Bedrock. We can combine into one list or separate? Probably just list all items; we can differentiate with subheadings? Not allowed. We'll just list all as

items. Pay section: include the compensation details. The posting says: "The all-in total compensation for this role is $170,500 and $176,000, and is specific to the United States. A reasonable estimate of the base salary range would be $155,000 - $160,000 plus applicable bonus/benefit offerings, etc., as those similarly situated within the Company. It takes into account a wide range of factors that are considered in making compensation decisions, including, but not limited to, skill sets, training, licensure and certification, and experience." Also later: "The Pay Range For This Role Is 155,000 - 160,000 USD per year (New York, NY)". We'll include that as a paragraph. We should not include fluff like "etc." but we keep as is. We must not include boilerplate: EEO, scam warning, visa sponsorship, etc. Also remove "To learn more about our values, mission and the wide-range of perks offered to employees at Comply, visit https://www.comply.com/careers/." That's boilerplate/perks link; we should remove because it's not specific benefits. Also remove "Comply is an Equal Opportunity Employer..." etc. Now produce HTML:

About the role

Who Are We Comply is the leading provider of compliance SaaS and consulting services for the global financial services sector. With more than 5,000 clients and hundreds of employees across the globe, Comply empowers Chief Compliance Officers and their teams to proactively manage regulatory obligations, mitigate risk, and scale with efficiency and confidence. Comply serves thousands of global financial services clients including broker-dealers, insurers, investment banks, private funds, RIAs, and wealth managers who rely on Comply offerings to power their compliance programs. To learn more about Comply, visit comply.com

Comply is looking for an Engineering Manager to lead and grow a high-performing software engineering team, shipping reliable, scalable software that powers compliance programs for thousands of financial services clients worldwide. In this role, you’ll own both the people and the technical direction of your team, partnering closely with product, QA, and business stakeholders to deliver against an ambitious roadmap. You’ll report to the Senior Director of Software Engineering and lead engineers based in India. Flexibility for cross-timezone collaboration is part of the rhythm, balanced by Comply’s commitment to sustainable, predictable working hours for managers. You’ll love this role if you’re energized by growing engineers, thrive in a fast-moving product environment, and want to shape the architecture of a cloud-native SaaS platform at real scale.

Responsibilities

• Lead a cross-functional engineering team, including QA and offshore engineers in India.
• Own everything from sprint planning and code review through deployment and production reliability.
• Set and hold the technical bar by establishing coding standards, conduct meaningful code reviews, and keep the team’s work secure, scalable, and aligned to architectural best practices.
• Partner with product and business stakeholders to define and prioritize delivery, ensuring every sprint connects back to customer value and product strategy.
• Build and sustain a team culture of ownership, inclusion, continuous learning, and craft where engineers feel accountable and supported in equal measure.
• Coach and develop engineers at all levels, run meaningful 1:1s, manage performance, and partner with recruiting to bring in the right strategic talent.
• Drive the technical roadmap by balancing near-term delivery commitments with long-term platform health, innovation, and technical debt reduction.
• Champion modern engineering practices across the team: CI/CD pipelines, agile methodologies, version control (Bitbucket), and AI-assisted development tools.
• Collaborate across business units to provide engineering perspective on product and commercial decisions and contribute to the broader direction of Comply’s software platform.

What Success Looks Like In Your First 90 Days You’ve built strong working relationships with your team and key cross-functional partners, and have a clear picture of team health, delivery velocity, and near-term roadmap priorities.You’re running sprints confidently, have had substantive 1:1s with every direct report, and have identified and started addressing at least one gap in