Lead Engineer - Mobile & Full-Stack (Remote)
Progressive Leasing · Texas, 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 must not repeat job title. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Let's extract sections:
- About the role: The initial paragraph describing Progressive Leasing, mission, remote work, etc. Could be "About the role". We'll include that as prose.
- Responsibilities: The "Your Day-to-day Technical Leadership", "Delivery & Execution", "Team & Collaboration" sections. Those are responsibilities.
- Requirements: The "Required YOU'LL BRING:" list.
- Qualifications: Possibly "Preferred" section? Could be "Qualifications" for required, and "Preferred" maybe as Skills? But we have separate Skills section. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have Required (mandatory) and Preferred (nice-to-have). Could treat Required as Requirements, Preferred as Skills? Or Qualifications could be Required? Usually Qualifications = required qualifications. Skills = specific skills. We'll decide.
We have a list of required items: Experience with AI first engineering and usage of Claude, Co-Pilot, etc. Strong understanding of native iOS/Android, proven full-stack capability, extensive experience with cross-browser/cross-platform development including mobile and responsive UI, experience with state management, REST APIs, GraphQL, mobile-specific data-fetching patterns, proven track record shipping production apps to 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, able to translate complex business requirements into simple software solutions, experience with CI/CD, Agile methodologies, open-source technologies, minimum of 10 years 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.
We also have Preferred 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.
We also have Benefits: "We Offer Competitive Compensation + Bonus PotentialFull Health Benefits; Medical/Dental/Vision/Life Insurance + Paid Parental LeaveCompany Matched 401kPaid Time Off + Paid Holidays + Paid Volunteer TimeDiversity Alliance Resource GroupsEmployee Stock Purchase ProgramTuition ReimbursementCharitable Gift MatchingJob Required Equipment & Services Will Be Provided". This is a run-on sentence but we can parse into list.
Pay: Not explicitly stated besides "Competitive Compensation + Bonus Potential". That is mention of compensation but not specific numbers. The instruction: never create Pay/Schedule sections unless posting actually states them. It says "Competitive Compensation + Bonus Potential" is stated, so we can include Pay section with that phrase. However we must avoid filler like "commensurate with experience". This is "Competitive Compensation + Bonus Potential" which is specific enough? It's still vague but it's stated. We'll include Pay.
Schedule: Not mentioned besides remote work anywhere in continental US or office in Draper, Utah. No specific schedule like full-time, hours. Not stated. So we should not create Schedule section.
Benefits: we have list.
Now we need to output HTML with headings for each section we include.
We must not include markdown fences.
We'll produce something like:
for each section we include.
We must not include markdown fences.
We'll produce something like:
About the role
Progressive Leasing is a leading provider ...
Responsibilities
- Own the architecture, quality, and delivery of the React Native mobile application and React JS web surfaces across iOS and Android ...