Mobile Team Tech Lead, New York, Contractor

We need to output HTML fragment with sections: About the role? The posting includes description of company, role, responsibilities, requirements, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse content: Company description: "Lab49 is an award-winning specialist consultancy...". That's about the company. Could be "About the role"? Actually "About the role" is for role description. But we could have "About Lab49" maybe not required heading; but we can include as prose under maybe no heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have: - About the role: description of role, what you'll do, success looks like, etc. - Responsibilities: list of duties (Design, implement, deliver, test... etc). Could be under Responsibilities. - Requirements/Qualifications/Skills: The "What You Should Have" list includes experience, proficiency, etc. Could be split into Requirements and Skills. But we can combine. - Bonus points: could be under Skills or Qualifications as extra. - Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section. - Pay: Not mentioned. So no Pay section. - Schedule: Mentioned: "This is an on-site role. 5 days/week in the WTC area in NYC." That's schedule info. So we can have Schedule section. We also have "Why Lab49" section: could be about company culture; maybe we can include as "About Lab49" but not in list. Could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it. We have content for Why Lab49 (culture, values). Could be placed under maybe "About Lab49" but not in prescribed headings. However we could treat it as part of "About the role" or maybe we can create a section "About Lab49" but not in the list; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use other headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. "Why Lab49" could be part of "About the role" or maybe we can omit. But we should preserve all substantive information; we can include it as a paragraph under maybe "About the role" or as a separate paragraph without heading? The instruction says use

for section headings (e.g. ...). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and put "Why Lab49" content under maybe "About the role" as a paragraph. Also we have "THE ROLE" heading in original; we can treat that as About the role. Let's extract sections: About the role: includes description of role, what you'll do, success looks like, why Lab49? Actually "What Success Looks Like" and "Why Lab49" could be part of About the role. Responsibilities: bullet list from "What You'll Be Doing": Design, implement, deliver, and test innovative Android and iOS applications while understanding our products from both a technical and product perspective in the context of our client’s business. Actively contribute to the adoption of strong software architecture, engineering best practices, and new technologies. We are always improving the process of building software; we’ll need your help to do that. Bring a passion to stay on top of tech trends. Experiment with and learn new technologies. That's a list of duties. Requirements/Qualifications/Skills: "What You Should Have" list: 10-12+ years of experience designing and building complex, commercial-grade software systems, with 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; Experience with agile development methodologies; Knowledge 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. Bonus points: Exposure or hands-on experience with Swift and native iOS development tools such as SwiftUI, and UIKit; Experience in fraud management/KYC/AML and regulatory reporting; Experience using on device biometrics for authentication; A strong portfolio of released applications on the Google Play Store; Experience with AppConfig community standards and enterprise app distribution; College degree in Computer Science or related field of study or equivalent experience; 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. We could put bonus points under Skills or Qualifications as extra bullet points. Schedule: "This is an on-site role. 5 days/week in the WTC area in NYC." We should not include duplicated lines. Ensure we preserve all substantive info. Now produce HTML fragment:

About the role

... paragraphs ...

Then

Responsibilities

• ... each duty as li

Then

Requirements

• ... each requirement

Maybe also

Skills

for bonus? But we could combine. But instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including qualifications and skills), Schedule. We can put bonus points under Requirements as well. Let's craft About the role paragraph: combine role description, success looks like, why Lab49. Role description: "Lab49 is currently looking for a Mobile Team Tech Lead who 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 have an opportunity to apply your skills and expertise to design innovative applications that solve complex problems and enhance performance and productivity at our marquis clients. You will help build and modernize large-scale consumer banking experiences, focusing on areas such as customer onboarding, account management, and money movement. As part of a greenfield initiative, you will lead the development of new mobile capabilities designed to support expansion into new markets and evolving regulatory requirements." Then "THE ROLE As a Mobile Team Tech Lead at Lab49 you are a true project leader. You 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." Actually schedule part we will move to Schedule section. Then "What Success Looks Like" bullet points: "Your teams consistently deliver high-quality software that meets user and client objectives. Engineers around you become more autonomous, capable, and effective because of your leadership. Clients trust your judgment and rely on you for technical direction and clarity. You demonstrate strong ownership of outcomes, proactively addressing risks before they become issues. You can step away from day-to-day coding when needed without compromising delivery quality or team performance." Then "Why Lab49" paragraph: "At Lab49, you'll work on complex, meaningful challenges alongside talented engineers, designers, and consultants. You'll gain exposure to a wide range of technologies, business domains, and client environments while continuing to grow your career. We value curiosity, judgment, and ownership. If you care about quality, enjoy helping others succeed, and want your work to have a meaningful impact, Lab49 is a place where you can thrive. Lab49/ION is committed to maintaining a supportive and inclusive environment for people with diverse backgrounds and experiences. We respect the varied identities, abilities, cultures, and traditions of the individuals who comprise our organization and recognize the value that different backgrounds and points of view bring to our business. Lab49/ION adheres to an equal employment opportunity policy that prohibits discriminatory practices or harassment against applicants or employees based on any legally impermissible factor." But note: we must remove EEO/equal-opportunity boilerplate. The last sentence about equal employment opportunity is boilerplate; we should remove it. Also the earlier sentence about supportive and inclusive environment may be considered EEO? It's about diversity; might be considered boilerplate but it's substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO statement. The supportive and inclusive environment might be considered part of EEO? It's about diversity; could be considered EEO-related. Safer to remove that sentence as well. However we need to preserve substantive info; but the EEO statement is likely boilerplate. We'll remove the sentences about supportive and inclusive environment and equal employment opportunity policy. Thus Why Lab49 paragraph becomes: "At Lab49, you'll work on complex, meaningful challenges alongside talented engineers, designers, and consultants. You'll gain exposure to a wide range of technologies, business domains, and client environments while continuing to grow your career. We value curiosity, judgment, and ownership. If you care about quality, enjoy helping others succeed, and want your work to have a meaningful impact, Lab49 is a place where you can thrive." Now schedule: "This is an on-site role. 5 days/week in the WTC area in NYC." Now responsibilities list: we have four bullet points? Actually the paragraph includes multiple sentences; we can split each sentence as li. Sentences: - Design, implement, deliver, and test innovative Android and iOS applications while understanding our products from both a technical and product perspective in the context of our client’s business. - Actively contribute to the adoption of strong software architecture, engineering best practices, and new technologies. - We are always improving the process of building software; we’ll need your help to do that. - Bring a passion to stay on top of tech trends. - Experiment with and learn new technologies. That's five. Now requirements list: from "What You Should Have" plus bonus points. Let's list each: - 10-12+ years of experience designing and building complex, commercial-grade software systems, with 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 - Experience with agile development methodologies - Knowledge 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 Bonus points (could be separate list but we can include as additional items): - Exposure or hands-on experience with Swift and native iOS development tools such as SwiftUI, and UIKit - Experience in fraud management/KYC/AML and regulatory reporting - Experience using on device biometrics for authentication - A strong portfolio of released applications on the Google Play Store