Engineering Director - Remote
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can map content to appropriate headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? Probably we should use those headings where applicable. The posting has sections: Who We Are (company overview) maybe not needed? Could be "About the role"? Actually "About the role" is generic heading for role description. We have "What We Do" describing role. Could map to "About the role". Responsibilities: "What You’ll Do". Requirements/Qualifications/Skills: "What You’ll Bring". Benefits: "What We Offer". Pay: "Pay Range". Schedule: not present, so omit. Also we should not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove the Fair Chance statement? That's legal boilerplate; should be removed. Also remove the note about Los Angeles County etc. Also remove the statement about criminal history etc. Also remove the "Based on eligibility, First American offers a comprehensive benefits package..." we keep benefits but maybe summarize? We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the benefits description: medical, dental, vision, 401k, PTO/paid sick leave, employee stock purchase plan. Also the inclusive culture statements maybe part of benefits? Could be part of "What We Offer". We'll keep that.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
About the role
... (content from What We Do and maybe Who We Are? Actually Who We Are is company overview, not role. Might be okay to include as part of About the role? But instruction: do not repeat job title as heading; we can include company overview as a paragraph under About the role? Might be okay. However "About the role" likely expects description of role. The "What We Do" section describes role. We'll put that.
Responsibilities
- ... list each bullet from What You’ll Do.
Requirements
Maybe combine Qualifications and Skills. We'll put Requirements heading and list items from What You’ll Bring (the bullet list). Could also separate Qualifications and Skills but we prefer few substantive sections. We'll put Requirements.Benefits
- ... list benefits.
Pay
Pay Range: $197,200.00 - $263,000.00 Annually
We must not include Schedule. We must preserve all substantive information: include the details like "10+ years of software development experience, with at least 8 years in a leadership role managing engineering teams." etc. We need to ensure we don't include boilerplate like "First American will consider for employment all qualified applicants..." etc. Remove that. Also remove the "Note that the following statements only apply to candidates who will be working from an unincorporated area within Los Angeles County." and the Fair Chance statements. Also remove the "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." Actually that's benefits; we keep it but maybe rephrase as list. We need to preserve all substantive information: So we need to keep the sentence about benefits exactly? Could convert to list but must preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot change meaning; we can reformat but must keep all details. Changing to list is okay as long as we keep all items. The original sentence: "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." That's substantive. We'll keep that as amaybe. But we also have a Benefits section; we could put that sentence inside
. However we also have other benefits statements earlier: "We are proud to foster an authentic and inclusive workplace For All." etc. That's also substantive. We'll include them. Thus Benefits section could have multiple paragraphs: inclusive culture statement, and the benefits package sentence. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so okay. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's extract sections: Who We Are: Could be omitted? It's company overview, not role. Might be considered not needed for role description. But we could include as part of About the role? 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 suggests using those. Probably we should stick to those headings and include relevant content under them. The company overview may not fit any of those headings; maybe we can omit it as it's not directly about the role. However the instruction says "Preserve ALL substantive information". If we omit Who We Are, we lose substantive info about company. But maybe that's considered boilerplate? It's not boilerplate; it's substantive about company culture. Could be considered part of "About the role" or "Benefits"? Might be okay to include under About the role as a paragraph describing the company. The heading "About the role" could include company context. I'd include it.
Thus About the role: combine Who We Are and What We Do.
Let's craft:
About the role
Join a team that puts its People First! Since 1889, First American (NYSE: FAF) has held an unwavering belief in its people. They are passionate about what they do, and we are equally passionate about fostering an environment where all feel welcome, supported, and empowered to be innovative and reach their full potential. Our inclusive, people-first culture has earned our company numerous accolades, including being named to the Fortune 100 Best Companies to Work For® list for eleven consecutive years. We have also earned awards as a best place to work for women, diversity and LGBTQ+ employees, and have been included on more than 50 regional best places to work lists. First American will always strive to be a great place to work, for all. For more information, please visit www.careers.firstam.com.
We are seeking a dynamic and experienced Director of Software Engineering to lead our software development teams, drive technical excellence, and collaborate with key stakeholders to deliver innovative, scalable software solutions. As the Director, you will oversee the entire software development lifecycle, ensuring that projects are delivered on time, within budget, and aligned with business goals. This role requires a strong leader with a passion for technology, strategic thinking, and the ability to mentor and grow high-performing engineering teams.
Now Responsibilities: list from What You’ll Do. We need to capture each bullet: - Technical Strategy: Define and execute the software engineering strategy, aligning with overall business objectives. Stay abreast of emerging technologies and drive innovation within the development teams. - Collaboration: Partner with cross-functional teams, including Product, Design, and QA, to develop software that meets customer needs and business requirements. - Inspire Impact : Drive end-to-end engineering delivery by partnering with product and UX leaders, as well as cross-functional business, product, and technology teams to create meaningful impact. - Architecture & Design: Ensure that software architecture is scalable, maintainable, and follows industry best practices. Lead architecture reviews and contribute to design decisions. - Process Improvement: Implement and refine engineering processes (e.g., Agile, DevOps) to improve team efficiency and product quality. Foster a continuous improvement mindset across the engineering organization. - Hiring & Retention: Lead the recruitment and retention efforts for the software engineering team, ensuring the team is composed of top talent with the right skills to meet company goals. Note there is extra space before colon in "Inspire Impact :". We'll keep as is. Now Requirements: from What You’ll Bring. List: - 10+ years of software development experience, with at least 8 years in a leadership role managing engineering teams. - Excellent problem-solving skills and ability to dive into system architecture, design, performance metrics, code, test plans, project plans, deployments, and operations. - Exceptional leadership and team-building skills, capable of inspiring teams to pursue and realize ambitious objectives. - Proven innovation skills with an impactful track record of driving business transformation and measurable outcomes. - Proven track record of delivering and supporting large-scale enterprise products and services. - Exceptional project management skills with the ability to manage multiple concurrent projects with competing priorities. - Outstanding communication abilities, adept at engaging and swaying stakeholders across all organizational tiers through both verbal and written means. - Previous experience leading multiple geographically distributed teams. - Ideally, you will also have experience with: - C# (.NET Core, .NET Framework) - TypeScript & React / Node.js - Experience with cloud platforms (e.g., AWS, Azure, GCP) - Proven success in scaling teams and implementing best practices in software development - Knowledge of security, privacy, AI, and compliance standards in software development - Working within a highly regulated industry such as Financial Services or Healthcare We need to preserve the sub-bullets under "Ideally, you will also have experience with:" as part of the list. Could nest- ...
- ... etc. But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll keep flat list maybe with sub-items as separate
- but we need to preserve the grouping. Could keep as separate items with dash. Simpler: keep as separate
- lines, preserving the text exactly. Thus we will have many
- items. Now Benefits: we have inclusive culture statements and benefits package. We have: "What We Offer By choice, we don’t simply accept individuality – we embrace it, we support it, and we thrive on it! Our People First culture is inclusive for all employees - not just because it's the right thing to do, but because it's the key to our success. We are proud to foster an authentic and inclusive workplace For All. You are free and encouraged to bring your entire, unique self to work. First American is an equal opportunity employer in every sense of the term. Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." We need to remove EEO statement? It says "First American is an equal opportunity employer in every sense of the term." That's boilerplate EEO; should be removed per instruction: remove EEO/equal-opportunity boilerplate. So we remove that sentence. Also remove "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." That's not EEO; it's benefits info, we keep. We also have earlier "What We Offer By choice, we don’t simply accept individuality – we embrace it, we support it, and we thrive on it! Our People First culture is inclusive for all employees - not just because it's the right thing to do
- ... etc. But instruction: Use