Jobs · Engineering

Lead Engineer - Mobile & Full-Stack (Remote)

Progressive Leasing · Florida, United States · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, we need to extract sections: The posting includes: - Intro about company: "Progressive Leasing is a leading provider..." This could be "About the role"? Actually "About the role" is about the position. The intro includes company description and role description. We can treat that as "About the role" content. - Then "This role is a work from home position..." That's also about role. - Then "Employee Value Proposition (EVP): ..." That's about company culture; could be part of About the role. - Then "WE ARE: ..." etc. That's also about company. - Then "YOU ARE: A software professional who leads..." That's more about candidate expectations; could be part of Requirements or Qualifications. - Then sections: "Your Day-to-day Technical Leadership" with bullet points (actually paragraphs). Then "Delivery & Execution", "Team & Collaboration". Those are responsibilities. - Then "Required YOU'LL BRING:" list of requirements. - Then "Preferred Experience ..." list. - Then "We Offer Competitive Compensation + Bonus Potential" list of benefits. - Then "Job Required Equipment & Services Will Be Provided" maybe part of benefits. - Then EEO statement etc to be removed. - No explicit Pay or Schedule details. So we should not include Pay or Schedule sections because they are not stated. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine Required and Preferred?), Skills, Benefits. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide what goes where. We have: - About the role: company description, role remote, EVP, WE ARE, YOU ARE? Actually "YOU ARE" is more about candidate expectations; could go under Requirements/Qualifications. But we can include some of it in About the role as overview. Better: About the role: include the introductory paragraphs up to "YOU ARE:"? Might be okay. Responsibilities: include the three subsections: Your Day-to-day Technical Leadership, Delivery & Execution, Team & Collaboration. Each contains prose paragraphs; we can treat each bullet as list items? Actually they are paragraphs with multiple sentences. We can wrap each paragraph in

    . Or we could treat each bullet as list item if they are bullet-like but they are not bullet points; they are sentences separated by line breaks. We'll output

    for each. Requirements: the "Required YOU'LL BRING:" list. That's a list of items each starting with bold? Actually each line is a requirement. We'll make

    • . Qualifications: maybe we can treat "Preferred Experience ..." as Qualifications (or Preferred Qualifications). Could also be Skills. But we have separate Skills heading. Could put technical skills under Skills. However the posting includes many skill-like items: Experience with A.I. first engineering, native iOS/Android, full-stack, state management, REST/GraphQL, CI/CD, etc. Those could be Skills. The "Preferred Experience" includes LLM/AI-native, webview integration, leading teams, micro-frontend, accessibility, Expo, fintech background. Those could also be Skills or Qualifications. We need to avoid thin sections. Perhaps combine Required and Preferred into Requirements and Qualifications sections: Requirements = Required; Qualifications = Preferred. Skills could be extracted from both? But we already have skill-like items in Required. Might be redundant. Better: Use sections: About the role, Responsibilities, Requirements (covers Required), Qualifications (covers Preferred), Benefits. Skip Skills because it's covered. But instruction says we can include Skills if we have content. We could still include Skills but risk duplication. Safer to follow the posting: we have Required (technical qualifications) and Preferred (additional qualifications). We'll map Required to Requirements, Preferred to Qualifications. Benefits from "We Offer ..." plus equipment statement. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not include Pay or Schedule. Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the EEO statement at end. Also remove "Job Required Equipment & Services Will Be Provided" maybe keep as benefit? It's a benefit: equipment provided. We'll include in Benefits. Now let's extract. About the role: Let's gather paragraphs from start until before "Your Day-to-day Technical Leadership". The text: "Progressive Leasing is a leading provider of in-store and e-commerce lease-to-own solutions. With more than 20 years in FinTech, we’ve grown from start-up to industry leader by innovating, simplifying, and valuing people. We are a subsidiary of PROG Holdings (NYSE: PRG), a FinTech holding company with three business segments: Progressive Leasing, Purchasing Power (a leading employee purchase program for consumer products and services using payroll deduction), and Four, a Buy Now Pay Later (BNPL) platform. We are currently hiring a Lead Engineer - Mobile & Full-Stack (Remote) to help grow our company and ensure our mission is achieved! This role is a work from home position and can be performed remotely anywhere in the continental US or in our corporate office in Draper, Utah. Employee Value Proposition (EVP): PROG is dedicated to providing people with opportunity; opportunity for inclusive collaboration, opportunity for innovation, and opportunity for development. WE ARE: A sales organization that is dedicated to developing and executing winning sales and marketing strategies in a fun and engaging environment. We provide our employees with challenging opportunities where passion, tenacity, innovation and diligence are rewarded. We want your passion, your creativity and your mastery in rallying support for the ideas that will advance our initiatives. With your broad strategic expertise, you will plan, develop and implement highly effective sales, marketing and operational strategies, solutions and initiatives to drive market share and sell-through for our clients. YOU ARE: A software professional who leads with technical depth and delivers solutions for complex, large-scale business problems. You are equally at home in a React Native codebase, designing a BFF architecture, and mentoring engineers across time zones. You create and deliver customized experiences for customers across all channels — mobile app, webview, and website." That seems like a good About the role. Now Responsibilities: We have three sections: 1. Your Day-to-day Technical Leadership Paragraphs: - Own the architecture, quality, and delivery of the React Native mobile application and React JS web surfaces across iOS and Android - Define and enforce coding standards, patterns, and best practices across mobile and full-stack development - Drive the adoption of an A.I. first engineering mindset - Drive technical roadmap decisions and align them with product goals, timelines, and the broader engineering organization - Provide technical expertise in architecture, design, testing, and implementation — spanning native UI through BFF to backend API contracts and LLM integration patterns - Lead in-depth code reviews and conduct root cause analysis of critical production issues - Actively engage in and may influence the direction of industry groups or open-source communities These are bullet-like lines but each ends with a period. We'll treat each as
    • inside a
        under a heading? The instruction: Use
        • for any list of duties/requirements/benefits. So we can make a list. 2. Delivery & Execution Paragraphs: - Own end-to-end delivery of mobile and web features from technical scoping through App Store / Play Store release and production monitoring - Break down complex requirements into actionable engineering tasks, milestones, and clear ownership across a distributed team - Identify and proactively mitigate technical risk throughout the development lifecycle - Maintain and improve CI/CD pipelines and release management processes for both platforms - Manage the technical complexity of the webview bridge between the native app and D2C web experience — a critical integration point for our lease application flow - Develop and deploy solutions with performance, security, and accessibility in mind from the start 3. Team & Collaboration Paragraphs: - Lead and mentor a geographically distributed team across two hubs (Americas and India), fostering strong engineering culture and clear accountability across time zones - Work collaboratively with technical and business team members (Product, Design, QA, Backend) to develop and maintain business solutions following Agile principles - Initiate and lead efforts toward organizational goals; be influential in building a dynamic, productive engineering organization and continuously improving practices - Participate in hiring — reviewing resumes, conducting technical interviews, and evaluating candidates; proven experience building and mentoring world-class engineering teams - Set clear expectations for a mix of full-time employees and contractors, raising the technical bar across all contributors - Ensure software quality engineering by keeping engineers current on best practices, automated testing, alerting, and proactive production support We'll make each as
          • . Now Requirements (Required YOU'LL BRING:): List items: - Experience with A.I. first engineering and usage of Claude, Co-Pilot, and other tools - Strong understanding of native iOS (Swift / Obj-C) and Android (Kotlin / Java) sufficient to bridge gaps and work with native modules - Proven full-stack capability — comfortable owning or collaborating on BFF / API layers, not just the mobile UI - Extensive experience with cross-browser and cross-platform development including mobile and responsive UI - Experience with state management (Redux, Zustand, Recoil, or equivalent), REST APIs, GraphQL, and mobile-specific data-fetching patterns - Proven track record shipping production apps to the App Store and Google Play - Experience developing and architecting high-transaction, high-throughput systems - Demonstrated ability to lead distributed, contractor-heavy teams across time zones with strong personal accountability - Excellent problem-solving skills; meticulous, methodical, and able to translate complex business requirements into simple software solutions - Experience with CI/CD, Agile methodologies, and open-source technologies - A minimum of 10 years of software development experience, with at least 5 years focused on mobile (React Native) and full-stack development - Deep expertise in React Native, React JS, TypeScript / JavaScript, and Node.js - AI‑enabled tools are already part of how work gets done across our organization, and their use will continue to expand over time. - We value people who are curious, adaptable, and open to learning as roles and workflows evolve. Note: The last two sentences are more like statements; but they are part of the list? They appear as separate lines after the bullet list. We'll include them as list items as well. Now Qualifications (Preferred Experience ...): List items: - Experience with LLM / AI-native development patterns and integrating AI-powered features into consumer products - Familiarity with webview integration patterns and bridging native and web experiences - Experience leading teams of 5+ engineers across multiple geographies - Familiarity with micro-frontend or monorepo architectures (Nx, Turborepo) - Background in mobile accessibility (WCAG, platform accessibility APIs) - Experience with Expo or Expo EAS for managed and bare workflow projects - Background in fintech, consumer lending, or similarly regulated industries Now Benefits (We Offer Competitive Compensation + Bonus Potential): List items: - Competitive Compensation + Bonus Potential - Full Health Benefits; Medical/Dental/Vision/Life Insurance + Paid Parental Leave - Company Matched 401k - Paid Time Off + Paid Holidays + Paid Volunteer Time - Diversity Alliance Resource Groups - Employee Stock Purchase Program - Tuition Reimbursement - Charitable Gift Matching - Job Required Equipment & Services Will Be Provided We should keep the exact phrasing. Now we need to

Similar jobs