Application Development Manager
for section headings. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like equal opportunity etc. Also remove navigation/legal etc. We must preserve all substantive info, not invent. Include sections only when posting has real specific content. So we need sections: About the role? The intro "Strong Roots..." is about company, maybe we can treat as "About the role" or "About the company"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings where appropriate. The posting includes "Why This Role Matters" (could be About the role). "What You Will Do" -> Responsibilities. "How You Will Contribute" maybe also part of Responsibilities or maybe Qualifications? But we can treat as "How You Will Contribute" as part of Responsibilities? Better to keep as separate? The instruction says prefer a few substantive sections over many thin ones. So we could combine "What You Will Do" and "How You Will Contribute" under Responsibilities. "What You Will Bring" -> Requirements/Qualifications. "Position Details" maybe not needed as heading? Could be omitted if not standard heading; but we could include as a short p under maybe "About the role"? But we need to preserve all substantive info. Could include a
for Position Details after the sections. "Compensation Details" -> Pay. "Benefits" -> Benefits. Also maybe "Schedule" not present, so omit. We need to use
- for any list of duties/requirements/benefits. So we need to convert lists to
- . The responsibilities are a long paragraph with many items separated by periods. We could break into list items. Similarly requirements list.
We must not invent or summarize away detail. Must preserve all substantive information. So we need to include each bullet as a list item preserving the text.
We need to remove cookie/navigation/legal/EEO etc. At end there is "Indiana Farmers Insurance is an equal opportunity employer..." remove that.
Also remove "Explore careers at Indiana Farmers Insurance." maybe not needed? It's a call to action; could be considered boilerplate? It's not legal but maybe we can keep? It's not substantive about role. Probably remove as it's like application instruction. The instruction says remove application instructions. So remove that line.
Also remove "Explore careers at Indiana Farmers Insurance." and maybe "Join us and help write the next chapter..." That's promotional but maybe keep as part of About the role? It's fluff but still substantive? Might be considered boilerplate. Safer to keep only sections with concrete info.
Let's extract content:
Intro paragraph: "Strong Roots. Forward Thinking.For nearly 150 years, Indiana Farmers Insurance has earned trust by helping members protect what matters most. Our history as a mutual insurance company provides stability, but it does not keep us from looking ahead. We continue to improve how we serve our members, partner with independent agencies, and support our associates. Guided by our ICARE values of Innovation, Collaboration, Accountability, Respect, and Empowerment, you will be encouraged to ask questions, contribute ideas, build your skills, and take an active role in shaping what comes next."
That's about company culture; could be under About the role.
"Why This Role Matters" paragraph: "Technology plays an important role in how Indiana Farmers Insurance serves members, supports agency partners, and operates effectively. As Manager, Application Development, you will lead application development teams responsible for scalable, secure, and reliable software solutions. You will combine people leadership, software delivery oversight, technical guidance, and business partnership to improve customer experience, operational efficiency, regulatory compliance, and long-term technology effectiveness."
That's about role importance.
"What You Will Do" list: many items separated by periods. Let's extract each sentence:
- Lead application development associates, including recruiting, onboarding, goal setting, coaching, feedback, performance evaluation, associate development, succession planning, and performance management.
- Align application development priorities with company goals and business needs, and oversee delivery plans, resource allocation, dependencies, risks, timelines, scope, quality, and commitments.
- Partner with business, product, architecture, security, vendor, and technical teams to communicate progress, resolve issues, make informed trade-offs, and support successful adoption of technology solutions.
- Guide solution design with architects and senior developers to help ensure applications are robust, scalable, secure, supportable, and aligned with enterprise standards.
- Strengthen development and testing practices and advance Agile, DevOps, automation, and continuous delivery to improve software quality, collaboration, and delivery reliability.
- Oversee incident management and recovery for supported applications, using monitoring, logs, metrics, tracing, and other observability practices to support service health, diagnosis, resilience, and performance improvement.
- Coordinate application security, data protection, identity and access, vulnerability management, and compliance practices with technology and security partners to reduce operational, cybersecurity, and governance risk.
- Evaluate technical alternatives, emerging technologies, industry trends, tools, and methods based on feasibility, cost, risk, scalability, and supportability.
- Partner with business teams and vendors to evaluate, onboard, and manage third-party software and services so external solutions support stakeholder needs and organizational goals.
- Identify and apply AI-enabled tools, including agentic AI capabilities, to improve efficiency, decision-making, quality, and business outcomes while maintaining appropriate human oversight, security, transparency, and governance.
That's 10 items.
"How You Will Contribute" paragraph: "You will be successful by building capable teams, creating clarity around priorities and delivery commitments, and making thoughtful decisions that balance business needs, technical quality, risk, and long-term impact. This role calls for a collaborative leader who communicates effectively with technical and non-technical partners, adapts as conditions change, follows through on commitments, and empowers associates to take ownership."
That's more about success factors; could be part of Responsibilities or maybe a separate section like "Success Factors". But we can incorporate into Responsibilities as additional bullet? Might be thin. Could create a section "How You Will Contribute" as its own heading? The instruction says prefer few substantive sections over many thin ones. This is a paragraph, not a list. Could be included under Responsibilities as a paragraph. But we need to use
for prose. So we could have a
after the list. "What You Will Bring" list: extract each bullet: - A bachelor’s degree in computer science, information technology, software engineering, or a closely related field; equivalent relevant experience may be considered. - Three or more years of project management experience leading projects using software development lifecycle (SDLC) and/or Agile methodologies. - Five to seven years of experience developing web-based applications, preferably with .NET technologies. - Experience supervising, leading, or managing software development associates or project team members. - Knowledge of .NET web development, service-oriented architecture, software design principles, and modern development toolsets. - Knowledge of application security practices, including threat modeling, secure coding, identity and access controls, vulnerability management, and security control frameworks. - Experience with delivery planning methods such as estimation, capacity planning, dependency mapping, prioritization, and risk tracking for complex technology work. - Knowledge of reliability and performance engineering, including resilience patterns, failure analysis, service-level objectives, high-availability design, capacity planning, and observability practices. - Property and casualty insurance industry experience is preferred; mobile development experience is also preferred. - Strong leadership, systems thinking, technical assessment, collaboration, communication, judgment, adaptability, accountability, learning agility, empowerment, and strategic perspective. That's 10 items. "Position Details": paragraphs: - Department: Information Technology - Reports to: Director, Application Development - Work environment: Work may be performed in-office, remotely, or in a hybrid arrangement, consistent with company policy, based on business needs and role requirements. - Additional considerations: Remote associates are expected to travel to the Home Office periodically, with occasional additional travel for meetings, training, conferences, or other business needs. Work involves extended periods of sitting and frequent computer use, requiring sustained visual concentration. We can keep as a
maybe under a heading "Position Details"? Not in standard list but we could include as a section heading "Position Details". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those headings. Position Details could be folded into About the role or maybe omitted? But we need to preserve all substantive info. Could include as a
after the sections without a heading. That's allowed. "Compensation Details": paragraph: - Anticipated Hiring Range: $107,000 to $128,000 annually - This is the expected hiring range for the position. Actual starting salary may vary based on qualifications, experience, internal equity, and market factors. The range may not reflect the position’s full salary range or future earning potential. Eligible positions may also include bonus or incentive compensation and the benefits described below. We need Pay section. Use
Pay
and thenwith that info. "Benefits": list: - Free Health insurance (Associate Only) - Free Dental insurance (Associate Only) - Free Vision insurance (Associate Only) - Free Life insurance - Free Short-Term & Long-Term Disability insurance - 2% 401k Company Match - 11% 401k Company Contribution - Excellent Paid Time Off - Generous paid time for Parental Leave - Day of Service - We promote from within our widely talented workforce regularly and consistently offer opportunities to learn and grow - Student Loan Assistance Program - Educational Incentive Program - Employee Assistance Programs for you and your family - Matching funds of up to $100 annually are available from the company for your favorite charitable organization - Associate recognition awards, fun gatherings, and opportunities to make friends are part of our culture - An on-site fitness center at our home office in Carmel, Indiana as well as free and convenient parking We need Benefits section with
- .
Now we need to output HTML fragment only, no /, no markdown.
Structure:
About the role
Intro paragraph + Why This Role Matters? Could combine.
Maybe better:About the role
Strong Roots... (intro) ... shaping what comes next.
Technology plays an important role ... long-term technology effectiveness.
Then Responsibilities:Responsibilities
- ... each item
You will be successful by building capable teams...
(the How You Will Contribute paragraph) Then Requirements/Qualifications:Qualifications
- ... each item
Pay
Anticipated Hiring Range: $107,000 to $128,000 annually...
Then Benefits:Benefits
- ... each benefit
after Benefits or before Pay? Could add a
Position Details
but not in list. Might be okay but instruction says prefer few substantive sections; adding another section may be thin. Could incorporate into About the role as a paragraph. Let's add aafter Benefits for Position Details. Now ensure we don't include any boilerplate like equal opportunity. Check for any repeated lines:
- .
Now we need to output HTML fragment only, no /, no markdown.
Structure:
- . The responsibilities are a long paragraph with many items separated by periods. We could break into list items. Similarly requirements list.
We must not invent or summarize away detail. Must preserve all substantive information. So we need to include each bullet as a list item preserving the text.
We need to remove cookie/navigation/legal/EEO etc. At end there is "Indiana Farmers Insurance is an equal opportunity employer..." remove that.
Also remove "Explore careers at Indiana Farmers Insurance." maybe not needed? It's a call to action; could be considered boilerplate? It's not legal but maybe we can keep? It's not substantive about role. Probably remove as it's like application instruction. The instruction says remove application instructions. So remove that line.
Also remove "Explore careers at Indiana Farmers Insurance." and maybe "Join us and help write the next chapter..." That's promotional but maybe keep as part of About the role? It's fluff but still substantive? Might be considered boilerplate. Safer to keep only sections with concrete info.
Let's extract content:
Intro paragraph: "Strong Roots. Forward Thinking.For nearly 150 years, Indiana Farmers Insurance has earned trust by helping members protect what matters most. Our history as a mutual insurance company provides stability, but it does not keep us from looking ahead. We continue to improve how we serve our members, partner with independent agencies, and support our associates. Guided by our ICARE values of Innovation, Collaboration, Accountability, Respect, and Empowerment, you will be encouraged to ask questions, contribute ideas, build your skills, and take an active role in shaping what comes next."
That's about company culture; could be under About the role.
"Why This Role Matters" paragraph: "Technology plays an important role in how Indiana Farmers Insurance serves members, supports agency partners, and operates effectively. As Manager, Application Development, you will lead application development teams responsible for scalable, secure, and reliable software solutions. You will combine people leadership, software delivery oversight, technical guidance, and business partnership to improve customer experience, operational efficiency, regulatory compliance, and long-term technology effectiveness."
That's about role importance.
"What You Will Do" list: many items separated by periods. Let's extract each sentence:
- Lead application development associates, including recruiting, onboarding, goal setting, coaching, feedback, performance evaluation, associate development, succession planning, and performance management.
- Align application development priorities with company goals and business needs, and oversee delivery plans, resource allocation, dependencies, risks, timelines, scope, quality, and commitments.
- Partner with business, product, architecture, security, vendor, and technical teams to communicate progress, resolve issues, make informed trade-offs, and support successful adoption of technology solutions.
- Guide solution design with architects and senior developers to help ensure applications are robust, scalable, secure, supportable, and aligned with enterprise standards.
- Strengthen development and testing practices and advance Agile, DevOps, automation, and continuous delivery to improve software quality, collaboration, and delivery reliability.
- Oversee incident management and recovery for supported applications, using monitoring, logs, metrics, tracing, and other observability practices to support service health, diagnosis, resilience, and performance improvement.
- Coordinate application security, data protection, identity and access, vulnerability management, and compliance practices with technology and security partners to reduce operational, cybersecurity, and governance risk.
- Evaluate technical alternatives, emerging technologies, industry trends, tools, and methods based on feasibility, cost, risk, scalability, and supportability.
- Partner with business teams and vendors to evaluate, onboard, and manage third-party software and services so external solutions support stakeholder needs and organizational goals.
- Identify and apply AI-enabled tools, including agentic AI capabilities, to improve efficiency, decision-making, quality, and business outcomes while maintaining appropriate human oversight, security, transparency, and governance.
That's 10 items.
"How You Will Contribute" paragraph: "You will be successful by building capable teams, creating clarity around priorities and delivery commitments, and making thoughtful decisions that balance business needs, technical quality, risk, and long-term impact. This role calls for a collaborative leader who communicates effectively with technical and non-technical partners, adapts as conditions change, follows through on commitments, and empowers associates to take ownership."
That's more about success factors; could be part of Responsibilities or maybe a separate section like "Success Factors". But we can incorporate into Responsibilities as additional bullet? Might be thin. Could create a section "How You Will Contribute" as its own heading? The instruction says prefer few substantive sections over many thin ones. This is a paragraph, not a list. Could be included under Responsibilities as a paragraph. But we need to use