Senior Software Engineer - iOS
or drop it." The recruiter line is minor metadata; we could fold into a short
under Pay or drop. Probably better to include a short
under Pay: "Your recruiter can share more information about the salary range specific to your working location and other factors during the hiring process." That's okay. Now schedule: "This role will be in-office on a hybrid schedule — Team Members will be expected to work in the office 3 days per week on Mondays, Wednesdays, and Thursdays. Lyft considers working in the office at least 3 days per week to be an essential function of this hybrid role. Additionally, hybrid roles have the flexibility to work from anywhere for up to 4 weeks per year." Also "#Hybrid" tag maybe ignore. Thus schedule section with that content. Benefits: list items: Great medical, dental, and vision insurance options with additional programs available when enrolled; Mental health benefits; Family building benefits; Child care and pet benefits; 401(k) plan to help save for your future; In addition to 12 observed holidays, salaried team members have discretionary paid time off, hourly team members have 15 days paid time off; 18 weeks of paid parental leave. Biological, adoptive, and foster parents are all eligible; Subsidized commuter benefits; Lyft Pink - Lyft team members get an exclusive opportunity to test new benefits of our Ridership Program. We need to put each as
- .
Now Experience/Qualifications: The "Experience" section includes bullet points: Code Quality: Experienced in delivering high-quality code. Experience working with designers and on internal developer productivity teams or projects. Strong experience with Swift. Experience with UIKit, declarative UI development and creating shared components. Familiarity with current design and prototyping tools (Figma, etc). Ability to work with a low-ego, highly collaborative, cross-functional team. Excited about working in a fast-paced, dynamic environment. You take pride in writing clean, maintainable, and scalable code, prioritizing clear design principles for reliability, and ensuring good code quality. Strong problem-solving skills and a passion for tackling difficult challenges. A strong sense of ownership for the things you build and a commitment to continuous improvement. Excellent presentation and documentation skills. Experience mentoring and supporting other Mobile Engineers. Demonstrated ability to lead a project from initial concept through to successful completion. Bonus Points: contributions to open source projects, experience with SwiftUI, experience with unidirectional and reactive programming.
We need to decide sections: Could have "Qualifications" (or "Requirements") covering Experience and Bonus Points. Or separate "Skills" and "Qualifications". The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Experience and Bonus Points into a single "Qualifications" section with
- ... ...
- list.
But we also have "Who Are You" which is more about traits; could be part of Qualifications as well. However "Who Are You" is a paragraph of traits; we could incorporate into Qualifications as list items? But it's not bullet list; it's sentences. Could treat as
under Qualifications. However we already have a separate "Who Are You" heading in original; but we need to decide sections. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have sections: About the role (intro), Responsibilities, Qualifications (combining Who Are You, Experience, Bonus Points), Benefits, Pay, Schedule. We must not repeat job title as heading. Good. Now we need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
...
Responsibilities
Qualifications
Who Are You: ...
maybe combine? Or we could make a- for qualifications but we have paragraphs. Could do
for the Who Are You paragraph(s) and then
- for Experience and Bonus Points.
But we need to preserve all substantive information. Let's extract.
First, About the role paragraph: combine all intro sentences into one
. Ensure we don't lose any detail. Let's copy the intro exactly: "At Lyft, our purpose is to serve and connect. We aim to achieve this by cultivating a work environment where all team members belong and have the opportunity to thrive. Our Client Infrastructure team is dedicated to building software that addresses challenges at a large scale, ensuring that our mobile applications are stable, scalable, and efficient. As a Mobile Engineer on the Mobile Foundations team, you will create and maintain foundational systems that all Lyft mobile engineers rely on, enabling teams across Lyft to deliver rich experiences that connect people and places. You will build scalable infrastructure, helping developers move fast and innovate, while ensuring Lyft's mobile developer experience remains at the forefront. Your work will have a multiplicative effect across Engineering and contribute directly to Lyft's overall stability. Our apps are used by millions of people, and we take great pride in our work, which means adhering to excellent development practices, careful code architecture, and an organization built around rapid releases. Our codebase is written entirely in Swift, utilizing modern design patterns and coding standards. We rely on third-party libraries and actively contribute back to the community, including the Swift language itself." Now Responsibilities list: bullet points: - Develop and maintain reliable mobile infrastructure, including networking, architecture, and UI frameworks (Lyft Product Language and DeclarativeUI library), to enable Lyft iOS engineers to deliver high-quality mobile experiences. - Collaborate with cross-functional partners (designers, Android engineers, Web engineers, and other Mobile Infrastructure teams) to strategically define the future of mobile UI and architecture, ensuring an innovative mobile developer experience at Lyft. - Support iOS engineers from across the organization as they use the tools we build and leverage these interactions to improve our roadmaps and offerings. - Bring new ideas to the table that aim to ease developer friction and keep our codebase joyful to develop in while continuously improving the codebase through refactoring. Now Qualifications: We'll include Who Are You paragraph(s) as
maybe multiple sentences. Let's capture the "Who Are You" block: "You are an enthusiastic and experienced mobile developer looking to use your engineering skills to improve developers’ ability to ship new features quickly.You get excited about new Swift features and compile improvements.You find delight in building the foundations and frameworks to accelerate the development of others, hiding away the complexities of the system.You are a diplomat who looks at the landscape and aligns engineers from different teams around a common pattern.You are excited about scaling millions of lines of Swift code to hundreds of mobile developers.You take initiative to identify and improve processes and solve problems proactively.You take pride in writing clean, maintainable, and scalable code with well-designed APIs, prioritizing clear design principles for reliability.You are passionate about collaborating with other teams and helping / supporting other iOS engineers." Note there are no spaces after periods; but we can keep as is. Then Experience list: - Code Quality: Experienced in delivering high-quality code. - Experience working with designers and on internal developer productivity teams or projects. - Strong experience with Swift. - Experience with UIKit, declarative UI development and creating shared components. - Familiarity with current design and prototyping tools (Figma, etc). - Ability to work with a low-ego, highly collaborative, cross-functional team. - Excited about working in a fast-paced, dynamic environment. - You take pride in writing clean, maintainable, and scalable code, prioritizing clear design principles for reliability, and ensuring good code quality. - Strong problem-solving skills and a passion for tackling difficult challenges. - A strong sense of ownership for the things you build and a commitment to continuous improvement. - Excellent presentation and documentation skills. - Experience mentoring and supporting other Mobile Engineers. - Demonstrated ability to lead a project from initial concept through to successful completion. Bonus Points: - contributions to open source projects - experience with SwiftUI - experience with unidirectional and reactive programming We could combine Experience and Bonus Points into a single
- list, but maybe better to keep as separate
- under Qualifications? However instruction: prefer few substantive sections over many thin ones. Having two lists under same section may be okay. Could just make one
- with all items, including bonus points as items. That would be fine.
Thus Qualifications section:
Who Are You: ...
then- list of experience and bonus points.
But we need to preserve the "Who Are You" as prose; we could just put it as a
without heading. That's fine. Now Benefits section: list items as above. Pay section: include the pay range sentence and maybe the recruiter line. Pay range: "The expected base pay range for this position in the San Francisco area is $148,000-$185,000 USD. Salary ranges