Software Engineering Manager II, Consumer 360

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive info. Let's extract sections: - About the role / overview: The first paragraph about Credit Acceptance, culture, etc. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have description: "Credit Acceptance is proud to be an award-winning company..." That's about company culture. Could be "About the role" or maybe "About the company". We'll put under

About the role

with paragraphs. Then responsibilities: The "Outcomes and Activities:" list includes many bullet-like sentences. We'll treat as responsibilities. Then requirements: The "Requirements:" section lists bullet items. Preferred Experience: Could be under Qualifications? Actually Qualifications often includes required and preferred. We could have a Qualifications section that includes both required and preferred? But instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements (the list). We have Preferred Experience maybe under Qualifications. Knowledge and Skills maybe under Skills. We have "Competencies:" which could be under Skills or Qualifications. Might treat as Skills. We have "Target Compensation:" which is Pay. We have "Benefits" section: "INDENGLP #zip Benefits Excellent benefits package that includes 401(K) match, adoption assistance, parental leave, tuition reimbursement, comprehensive medical/ dental/vision and many nonstandard benefits that make us a Great Place to Work". Also later "Our Company Values:" maybe not needed. We have Schedule: The posting mentions "This position will work from home; occasional planned travel to an assigned Southfield, Michigan office location may be required. However, this position is permitted to work at a Southfield, Michigan office location if requested by the team member." That's schedule/location info. So we can put under Schedule. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, etc. So remove the paragraphs about Equal Opportunity Employer, CCPA, etc. Also remove "Play the video below..." etc. Also remove "Our Company Values:" maybe not needed as it's not a heading we have; but could be considered part of About the role? Might be okay to keep as paragraph under About the role? It's about values; but we can keep as part of About the role. We must preserve all substantive information. So we need to keep the company culture paragraph, the role description, responsibilities list, requirements list, preferred experience, knowledge and skills, competencies, pay, benefits, schedule. We need to format as HTML: use

for each section heading, then content: paragraphs

for prose, lists

• for any list of duties/requirements/benefits. We need to decide which content is list vs prose. Responsibilities: many sentences each starting with a verb. Could be list items. Requirements: bullet list. Preferred Experience: list. Knowledge and Skills: list. Competencies: list? It's definitions; could be list. Benefits: list of benefits. Schedule: prose. Pay: prose. Let's extract exact text. First, company overview paragraph: "Credit Acceptance is proud to be an award-winning company recognized both locally and nationally across multiple workplace categories. Our world-class culture is shaped by dedicated team members who are driven to succeed as professionals individually and together as a team. Backed by a strong product, exceptional people, and a stable financial foundation, we’ve grown into a leading provider of used and new car financing across the country. Our Engineering and Analytics Team Members utilize the latest technology to develop, monitor, and maintain complex practices that help optimize our success. Our Team Members value being challenged, are encouraged to express their ideas, and have the flexibility to enjoy work life balance. We build intrinsic value by partnering with all functions of our business to support their success and make strategic business decisions. We focus on professional development and continuous improvement while enjoying a casual work environment and Great Place to Work culture!" That's one paragraph. Then role description: "The Software Engineering Manager II leads and grows cross-functional engineering teams that build and operate distributed, API-driven, cloud-native platforms. This leader is accountable for engineering excellence, delivery outcomes, and the technical health of the products their teams own — and for bringing modern AI capability into both the products we build and the way we build them." That's prose. Then "Outcomes and Activities:" heading then list: - "This position will work from home; occasional planned travel to an assigned Southfield, Michigan office location may be required. However, this position is permitted to work at a Southfield, Michigan office location if requested by the team member." Actually that's schedule but appears under Outcomes and Activities. We'll treat schedule later. But the list after that: "Leads and mentors team members on essential agile and product mindset tenets including early learning, self-organized teams, cross functionality, customer obsession, outcome focused, incremental delivery and test driven." "Participates in work planning processes to ensure the most important work is aligned to the appropriate team, that work is broken down enough that outcomes can be delivered incrementally. Leads and mentors cross functional team members on building world class products that deliver customer delight and business value" "Designs solutions to meet requirements for initiatives involving multiple team applications as well as applications owned by other teams." "Supports delivery teams to ensure process and technology standards are consistently followed to enable consistent delivery of value." "Develops and tracks delivery metrics while monitoring technical health of the product, informs progress toward delivery goals, and provides support appropriately when needed." "Builds effective teams by ensuring you have the right people and setting clear expectations" "Monitors and evaluates team performance and continuously coach and mentor team members" "Sets up your team for operational success by having a sound understanding on the system ecosystem, architecture, technologies and system domains and how these are used to achieve business outcomes." "Is an active participant in on-call escalation and incident management" "Owns the design, delivery, and lifecycle governance of API platforms and services used across teams — driving contract-first design, versioning and deprecation discipline, reuse, and consumer experience." "Drives adoption of AI across the software development lifecycle (ADLC), establishing standards, guardrails, and measures of effectiveness for AI-assisted engineering within the team." "Guides the team in identifying, designing, and delivering AI-enabled capabilities — including agentic solutions — with appropriate evaluation, human-in-the-loop controls, observability, and responsible-use practices." We'll treat these as responsibilities list. Then "Competencies:" heading then definitions: - Customer Empathy: description. - Engineering Excellence: description. - One Team: description. - Owner’s Mindset: description. We'll treat as list. Then "Requirements:" heading then list: - Bachelor’s Degree or equivalent experience. - Minimum of 5 years’ experience leading engineering teams. - Proven experience in technical leadership, capable of providing mentorship, cross-functional project execution, setting and executing on technical vision and strategy - Extensive experience implementing Agile and DevOps practices including but not limited to test driven, incremental releases, continuous integration, and deployment pipeline automation. - Experience in microservices design strategies and implementation including migration planning, service granularity, interservice communication, traceability, orchestration, and failure isolation - Experience with Cloud migrations and working in a mixed on-prem / cloud environment (container orchestration, security, serverless) - Experience leading teams that design and operate reliable distributed services at scale, including performance, observability, failure recovery, and applying AI where it improves system capabilities or operations. - Experience creating reusable, developer-friendly platforms with self-service onboarding, API observability, and applied AI capabilities such as intelligent APIs, tool/function calling, and MCP-based integrations. - Experience building secure, scalable, and cost-efficient cloud platforms, including deployment automation and applied AI workloads such as RAG, model services, agents, and AI-enabled engineering workflows. Then "Preferred Experience:" heading then list: - 4 years’ experience of leading initiatives in a Java ecosystem - Track record of identifying opportunities to improve outcomes via new tools and approaches, evaluating and measuring candidate solutions, and successfully advocating for their adoption - Experience applying appropriate levels of transactional and race condition-resilient approaches, including database locking, distributed transactions (XA), SAGA pattern - Ability to describe and design decoupled system transaction models that are resilient to upstream and downstream outages with appropriate recovery models - Experience implementing and operationalizing rules engines - Experience modernizing or decomposing legacy monoliths into API-first, cloud-native services. - Experience introducing AI capability into an existing engineering organization — building the adoption plan, upskilling engineers, and measuring the impact on delivery speed and quality. - Exposure to AI platform and tooling ecosystems (model providers and gateways, agent frameworks, vector databases, evaluation and observability tooling for LLM-based systems). Then "Knowledge and Skills:" heading then list: - Thought leader with deep technical expertise with the proven ability to influence and partner with business to innovate and drive outcomes - Ability to communicate complex technical information (both verbal and written) to all levels, including senior leadership - Ability to solve problems at the source by offering simple, working solutions. - Anticipates the impact of a change or project across multiple systems. - Responds promptly and effectively to resolve incidents, tasks, and projects. - Demonstrated ability and motivation to teach others - Ability to gain trust of others and builds solid relationships across and vertically throughout the organization - Effectively prioritize and execute tasks in a high-pressure environment. - Able to separate durable engineering fundamentals from hype when evaluating emerging AI tools and patterns, and to make pragmatic build-vs-buy and adopt-vs-wait decisions. Then "Target Compensation:" heading then prose: "A competitive base salary range from $155,263 – $227,719. This position is eligible for an annual variable bonus of cash and equity, between 15-30%. Bonus amounts are based on individual performance. Final compensation within the range is influenced by many factors including role-specific skills, depth and experience level, industry background, relevant education and certifications. Candidates who reside in the following major metropolitan areas may be eligible for a premium on top of the posted range based on their specific zone: San Francisco, Seattle, Boston, New York City, Los Angeles and San Diego." Then "INDENGLP #zip Benefits" maybe a tag; then benefits paragraph: "Excellent benefits package that includes 401(K) match, adoption assistance, parental leave, tuition reimbursement, comprehensive medical/ dental/vision and many nonstandard benefits that make us a Great Place to Work" We'll treat as benefits list. Then "Our Company Values:" maybe not needed but could be part of About the role. We'll include as paragraph under About the role? Might be okay. But we must not include boilerplate like EEO etc. So remove the later paragraphs about Equal Opportunity Employer, CCPA, video, etc. Also remove "Required degrees must have been earned at institutions of Higher Education which are accredited by the Council for Higher Education Accreditation or equivalent." That's part of Requirements? Actually it's after the preferred experience? It's a statement about degree accreditation. Might be considered part of Requirements but it's boilerplate? It's a requirement detail; we should keep it as part of Requirements? It's not boilerplate; it's a specific requirement about accreditation. We'll keep it as a requirement item. Also "Credit Acceptance is dedicated to providing a safe and inclusive working environment for all. As part of our Culture of Compliance, we are proud to be an Equal Opportunity Employer and value our culturally