Mobile Team Tech Lead, New York

We need to output HTML fragment with sections: About the role? Actually we have content: description of company, role, responsibilities, requirements, benefits? There's mention of salary range disclosure, bonus, etc. We need to include sections only if real content. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines, application instructions. We need to preserve substantive info. Let's parse content: Company intro: Lab49 is an award-winning specialist consultancy... (company description). This could be "About the company" but not required heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also have "About Lab49" maybe not listed but we can still use heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if appropriate? Probably stick to those categories. We have role description: "THE ROLE As a Mobile Team Tech Lead...". That's about the role. So heading "About the role". Then responsibilities: "What You'll Be Doing" list. Then "What Success Looks Like" maybe also responsibilities or expectations; could be part of responsibilities. Could combine. Requirements: "What You Should Have" list. Also bonus points maybe "Preferred qualifications" or "Bonus points". Could be under "Qualifications" or "Skills". We'll treat as "Requirements" for mandatory, and maybe "Preferred Qualifications" for bonus? But instruction only lists certain headings; we can still add others? Safer to stick to given headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: include description of role, leadership, on-site, etc. Responsibilities: list of duties: design, implement, deliver, test Android/iOS apps; contribute to adoption of strong architecture; improve process; stay on top of tech trends; experiment; etc. Also "What Success Looks Like" could be responsibilities or expectations; maybe treat as responsibilities. Requirements: mandatory experience: 10-12+ years experience designing/commercial-grade software, 4+ years leading Agile teams; proficiency in Kotlin, native Android tools Jetpack Compose; experience in consumer banking including account management and onboarding; familiarity with integrating RESTful APIs and third-party libraries; knowledge of agile dev methodologies; understanding of CI/CD pipelines for mobile apps; understanding of mobile UI/UX principles; excellent communication skills. Qualifications: maybe education: College degree in Computer Science or related field or equivalent experience. Also bonus points could be under Qualifications? Or Skills? Could treat bonus points as "Preferred Qualifications". But we have a heading Qualifications; we can put degree there. Bonus points maybe under "Skills"? Or we could add a separate section "Preferred Qualifications" but not in list; maybe better to put bonus under "Skills" as additional skills. Skills: list of technical skills: Kotlin, Jetpack Compose, Swift/SwiftUI/UIKit (bonus), RESTful APIs, CI/CD, mobile UI/UX, Agile, etc. Also bonus: fraud management/KYC/AML, regulatory reporting, on-device biometrics, portfolio of released apps, AppConfig community standards, enterprise app distribution, leverage AI-assisted dev tools. Benefits: mention discretionary bonus, total compensation package, salary range disclosure (NY). Also maybe "We are hiring across multiple levels for this job." Not a benefit. Could mention "Base salary is only one component of our total compensation package. Employees may be eligible for a discretionary bonus". That's benefit. Pay: salary range disclosure as required by S9427A when hiring in New York. No actual numbers given. So we cannot create Pay section if no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Base salary is only one component of our total compensation package. Employees may be eligible for a discretionary bonus, which is determined upon company and individual performance. Salary range disclosure as required by S9427A when hiring in New York." That's a statement about pay but no actual range. Is that enough to create a Pay section? It states they will disclose salary range as required, but not giving the range. Might be considered stating that they will disclose range, but not giving specifics. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (discretionary bonus, salary range disclosure). So we could include a Pay section with that info. However we should avoid filler like "commensurate with experience". This is not filler; it's actual statement about bonus and disclosure. So we can include Pay section with that text. Schedule: "This is an on-site role. 5 days/week in the WTC area in NYC." That's schedule info. So we can include Schedule section. Benefits: we have discretionary bonus, total compensation package. Also maybe "We value curiosity, judgment, and ownership." Not a benefit. Could include "We are hiring across multiple levels for this job." Not benefit. So Benefits section: mention discretionary bonus, total compensation package. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include duplicated lines. Ensure we preserve all substantive info. Let's draft:

  About the role

  Lab49 is an award-winning specialist consultancy that creates bespoke technology in partnership with the most important companies in finance. Founded in 2002 to bring Silicon Valley solutions to Wall Street’s door, Lab49 has worked on successive waves of technological change, including distributed computing, high-speed automation, enterprise UX and digital distribution, DevOps, cloud and data science. Today, Lab49 is an established partner in financial markets, having delivered hundreds of projects for clients including all the world’s tier‑one investment banks and many of the largest buy‑side firms globally.

  As a Mobile Team Tech Lead you will play a critical role on key projects for Lab49 clients, working in a collaborative and innovative project team with direct client‑facing interactions. You will design innovative applications that solve complex problems and enhance performance and productivity for marquee clients, help build and modernize large‑scale consumer banking experiences (customer onboarding, account management, money movement), and lead the development of new mobile capabilities as part of a greenfield initiative to support expansion into new markets and evolving regulatory requirements. You will own the technical direction and delivery of client engagements while multiplying the effectiveness of the engineers around you. This is a hands‑on leadership role: you will design systems, write code when it matters most, guide architectural decisions, and ensure the team delivers high‑quality outcomes even when you are not directly contributing code. You will work closely with client stakeholders, designers, product partners, and Lab49 leadership to ensure solutions are technically sound, aligned with business objectives, and delivered with excellence. This is an on‑site role, 5 days/week in the WTC area in NYC.

  Now Responsibilities:

  Responsibilities

  • Design, implement, deliver, and test innovative Android and iOS applications while understanding products from both a technical and product perspective in the context of the client’s business.
  • Actively contribute to the adoption of strong software architecture, engineering best practices, and new technologies.
  • Help improve the process of building software.
  • Bring a passion to stay on top of tech trends and experiment with and learn new technologies.
  • In the first 6‑12 months, ensure teams consistently deliver high‑quality software that meets user and client objectives.
  • Help engineers become more autonomous, capable, and effective through your leadership.
  • Earn client trust so they rely on your judgment for technical direction and clarity.
  • Demonstrate strong ownership of outcomes, proactively addressing risks before they become issues.
  • Be able to step away from day‑to‑day coding when needed without compromising delivery quality or team performance.
  Now Requirements:

  Requirements

  • 10‑12+ years of experience designing and building complex, commercial‑grade software systems.
  • 4+ years leading Agile teams.
  • Proficiency in Kotlin and experience with native Android development tools such as Jetpack Compose.
  • Experience in consumer banking including account management and onboarding.
  • Familiarity with integrating RESTful APIs and third‑party libraries.
  • Knowledge of agile development methodologies.
  • Understanding of continuous integration and continuous deployment (CI/CD) pipelines for mobile applications.
  • Understanding of mobile UI/UX principles and best practices to create intuitive and engaging user experiences.
  • Excellent communication skills with the ability to influence both technical and non‑technical stakeholders.
  Now Qualifications:

  Qualifications

  College degree in Computer Science or a related field of study, or equivalent experience.

  Now Skills (including bonus points):

  Skills

  • Exposure or hands‑on experience with Swift and native iOS development tools such as SwiftUI and UIKit (bonus).
  • Experience in fraud management/KYC/AML and regulatory reporting (bonus).
  • Experience using on‑device biometrics for authentication (bonus).
  • A strong portfolio of released applications on the Google Play Store (bonus).
  • Experience with AppConfig community standards and enterprise app distribution (bonus).
  • Leverage AI‑assisted development tools (e.g., Claude, Claude Code, Copilot) to improve team velocity and code quality, and help the team adopt them responsibly (bonus).
  Now Benefits:

  Benefits

  Base salary is only one component of the total compensation package. Employees may be eligible for a discretionary bonus, which is determined upon company and individual performance.

  Now Pay:

  Pay

  Salary range disclosure as required by S9427A when hiring in New York.

  Now Schedule:

  Schedule

  This is an on‑site role, 5 days/week in the WTC area in NYC.

  Check for any duplicated lines: we have repeated "This is an on‑site role, 5 days/week in the WTC area in NYC." both in About the role and Schedule. That's duplication; we should avoid duplication. The About the role paragraph already includes that sentence. We should remove it from Schedule or from About the role? The instruction: remove duplicated lines. So we need to keep only one occurrence. Let's keep it in Schedule section and remove from About the role. But About the role needs to mention on-site? Could keep a brief mention but not duplicate exact sentence. We can rephrase: "This is an on‑site role." without the schedule details. Let's adjust About the role paragraph to not include the exact same sentence. We'll keep a short phrase: "This is an on‑site role." and then schedule details in Schedule section. Let's edit About the role paragraph: remove the duplicated sentence and replace with "This is an on‑site role." We'll keep the rest. Now ensure we haven't lost any substantive info: we still mention on-site nature. Now check for any other duplicated content: "We are hiring across multiple levels for this job." appears twice in original; we omitted it entirely as not substantive? It's somewhat filler but could be considered meta. The instruction says remove duplicated lines. It's not essential info about role, so we can drop. Now ensure we haven't