Engineering Functional Lead - Innovation

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 specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate like EEO, navigation, cookie, legal, duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Salary Range (Pay) and mentions benefits (BBH's total rewards package). So we can include Pay and Benefits sections. Schedule not mentioned, so omit. We need sections: About the role (maybe from intro paragraph), Responsibilities (list), Qualifications (list), Skills (maybe combine with qualifications? but we can separate if content). The posting includes Qualifications list (bullet-like). Also includes "Experience in Agile frameworks", "Background in financial modeling", etc. Those could be under Skills or Qualifications. We'll follow typical: Qualifications (education, experience). Skills (technical abilities). Could also combine but better separate. We need to preserve all substantive info: The intro about BBH, partnership, Cable 5, role description. That's About the role. Responsibilities: list of bullet points under "Key Responsibilities". We'll capture each line. Qualifications: bullet list under "Qualifications". We'll capture each line. Skills: maybe we can extract from qualifications: "Strong experience with modern application architectures (cloud-native, APIs, SaaS platforms, AI/ML, Generative AI where applicable)", "Demonstrated ability to estimate complex, multi-layered projects...", "Excellent problem-solving skills...", "Intellectual curiosity and creativity...", "Comfort working in cross-functional environments...", "Comfort working with abstract concepts...", "Experience in Agile frameworks (Scrum, Kanban, SAFe)", "Background in financial modeling for technology investments or product unit economics", "Industry experience relevant to digital product innovation". Those could be skills. Benefits: paragraph about BBH's total rewards package: base salary, discretionary bonuses, profit-sharing, benefits enhancing experience: long-term savings, healthcare, income protection, professional development opportunities, time off. Also mention "Go to BBH.com to learn more about our rewards and benefits..." but that's maybe application instruction? It's about benefits. We'll include benefits paragraph. Pay: Salary Range MA: $170,000-$230,000 base salary + annual target bonus NJ: $170,000-$230,000 base salary + annual target bonus. Also note that base salaries may vary etc. We'll include that. We must not include duplicated lines. Also must not include EEO etc. Must not include "We are an equal opportunity employer..." etc. Must not include navigation etc. We must output only HTML fragment, no or . Use

headings,

• for lists,

  for prose. We need to ensure we don't create empty sections. Let's craft:

  About the role

  At BBH, Partnership is more than a form of ownership—it’s our approach to business and relationships. We know that supporting your professional and personal goals is the best way to help our clients and advance our business. With a 200-year legacy and a shared passion for what’s next, this is the right place to build a fulfilling career. Brown Brothers Harriman has a long history of transformation and evolution driven by deep expertise, a passion for solving client problems, and smart applications of technology. Our dedicated innovation practice, Cable 5, is responsible for identifying, investigating, and incubating potential future new businesses, applying a disciplined, stage-gated innovation process from idea sourcing to MVP. We are currently seeking an Engineering Functional Lead (FL) to join the Cable 5 team. This role is responsible for leading early-stage technical strategy, architecture definition, and feasibility validation for new product concepts. The Engineering FL operates at the intersection of business and engineering across early-stage concepts from idea to Product launch. They sit within an innovation design studio charged with deciding whether a product is worth building before code is written. The Engineering FL leads through technical influence in a multidisciplinary group of largely non-technical peers. As a key technical resource in our innovation discipline, this role will also support the exploration of market opportunities and act as a technical advisor in discussions with external fintechs.

  Responsibilities

  • Provide a strong engineering point of view during early-stage product design and iteration by translating ambiguous product ideas into concrete technical approaches, connecting market intent with feasible technical capabilities
  • Work collectively within a multidisciplinary group, syncing internal and external participants to keep technical direction aligned
  • Guide multiple concept teams through ambiguity, ensuring clarity on priorities, sequencing, and execution strategy
  • Assess technical implications of concept tests and product direction decisions, translating them into clear architecture strategies
  • Lead structured feasibility assessments to uncover risks, constraints, and dependencies tied to product direction
  • Explain technical choices and the reasoning behind them in clear language for non-technical peers and senior leaders
  • Develop financial models for technical aspects of a product’s business plan, including build cost, operating cost, and unit economics. Responsible for the integration into the broader build/operate cost model
  • Partner with internal and external groups to assess the state of technical capabilities across relevant sectors and determine whether our concepts have a differentiated technology-driven right to win
  • Partner with BBH enterprise architecture to ensure alignment and known divergence with broader IT and security standards
  • Support the development of prototypes, technical interfaces, and lightweight implementations to validate product concepts
  • Provide oversight and guidance of external development partners which can align to BBH innovation standards and practices
  • Collaborate closely with fellow Functional Leads (Design, Research Product, etc.) and senior leaders to ensure alignment with technical aspects of each product concept

  Qualifications

  • Bachelor’s degree in Computer Science, Engineering, or related field (or equivalent experience)
  • 10-15 years proven experience leading technical design and architecture for complex, greenfield products, ideally with extensive experience delivering cloud-based and/or enterprise-grade B2B solutions
  • Strong experience with modern application architectures (cloud-native, APIs, SaaS platforms, AI/ML, Generative AI where applicable)
  • Demonstrated ability to estimate complex, multi-layered projects and navigate uncertainty in new technology environments
  • Excellent problem-solving skills with the ability to break down complex systems and identify risks and tradeoffs
  • Intellectual curiosity and creativity, with the proven ability to communicate complex topics to non-technical and senior audiences
  • Comfort working in cross-functional environments alongside concept owners, designers, researchers, and engineers
  • Comfort working with abstract concepts, navigating ambiguity, lean testing, and agile ways of working in early-stage concept development.
  • Experience in Agile frameworks (Scrum, Kanban, SAFe)
  • Background in financial modeling for technology investments or product unit economics
  • Industry experience relevant to digital product innovation
  We could also have a Skills section but we already included many skill-like items in Qualifications. To avoid duplication, maybe we keep Qualifications as above and not create separate Skills. However the instruction says use headings for Skills if there is content. We could split: Qualifications for education/experience, Skills for technical abilities. But we already put many skill bullets in Qualifications. Might be okay to not have Skills section. But we need to ensure we preserve all substantive info; we have preserved them. It's okay to not have Skills heading if we consider them part of Qualifications. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can omit Skills if not needed. However we have skill content; but we could still keep them under Qualifications. It's acceptable. Now Benefits:

  Benefits

  BBH and its affiliates' compensation program includes base salary, discretionary bonuses, and profit-sharing. BBH's total rewards package recognizes your contributions with more than just a paycheck—providing you with benefits that enhance your experience at BBH from long-term savings, healthcare, and income protection to professional development opportunities and time off, our programs support your overall well-being.

  Pay:

  Pay

  Salary Range MA: $170,000-$230,000 base salary + annual target bonus; NJ: $170,000-$230,000 base salary + annual target bonus. The anticipated base salary range(s) shown above are only for the indicated location(s) and may differ in other locations due to cost of living and labor considerations. Base salaries may vary based on factors such as skill, experience and qualification for the role.

  We should not include Schedule. Check for any duplicated lines: We have not included the repeated "We value diverse experiences." twice? The posting had "We value diverse experiences. We value diverse experiences and transferrable skillsets." We omitted that as boilerplate? It's not exactly boilerplate but it's a duplicated line. We should remove duplicated lines. We omitted it. Good. We also omitted the "Go to BBH.com to learn more about our rewards and benefits, philanthropy, approach to sustainability or how we support you to thrive personally, physically and financially." That's more like a link; could be considered application instruction? It's not exactly instruction but it's a call to action. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is more like a promotional link; could be considered application instruction? It's not exactly instruction to apply but it's a link to learn more. Safer to omit. We also omitted the final EEO paragraph. Now ensure we didn't miss any substantive content: The intro about BBH's partnership approach, Cable 5, role description. We captured that. We captured responsibilities list exactly. We captured qualifications list exactly. We captured benefits and pay. Check if any other substantive content: "As a private partnership, every investment we make is in the relationships, technologies, products and development we believe are in the long-term interests of our clients and our people. Our long-tenured leaders are experts in their areas and are actively involved in the day-to day business, taking the time to provide guidance and mentoring to build the next generation of BBHers. Because we know, our success begins with yours." That's more about BBH culture; could be considered part of About the role? Might be considered substantive but not directly about role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. It's about BBH's partnership and leadership. Could be included in About the role section after the initial description. Let's add a paragraph after the role description: "As a private partnership, every investment we make is in the relationships, technologies, products and development we believe are in the long-term interests of our clients and our people. Our long-tenured leaders are experts in their areas and are actively involved in the day-to day business, taking the time to provide guidance and mentoring to build the next generation of BBHers. Because we know, our success begins with yours." We should not include the "Go to BBH.com..." line. Also we missed the sentence: "We believe stability is a competitive advantage, but being stable means having the knowledge, skill, and discipline to evolve, often—pushing the boundaries of innovation." That's also substantive about