Senior Android Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We need to be careful not to omit any specifics like "Participation in our incentive programs (which may include eligible cash, equity, or commissions). Plus paid vacation, holidays, sick time, parental leave, and recharge leave; medical, tele-health, dental and vision benefits; 401(k) plan; flexible spending accounts (FSAs); commuter program; life and disability insurance; Maven (a support system for new parents); Carrot (fertility benefits); UrbanSitter (caregiver referral network); Employee Assistance Program; and pet insurance."
Also "Bonuses and restricted stock units may be provided as part of the compensation package, in addition to a full range of benefits."
Also "Base pay is based on market location. Minimum wage for the position will always be met."
Also "Compensation: The base pay range for this position is $131,000-$197,000; however, base pay offered may vary depending on job-related knowledge, skills, and experience."
We need to include that in Pay section.
Now, we need to decide sections.
Potential sections:
- About the role (company mission, role description)
- Responsibilities (What You Will Do + earlier paragraphs)
- Qualifications (What We Look For)
- Skills (maybe separate but could be part of Qualifications; but we have enough content for Skills: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform, RESTful services, Scrum/Agile, etc.)
- Benefits (Perks That You Need To Know About + bonuses etc.)
- Pay (Compensation details)
We should not create Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now, we need to extract lists.
Responsibilities list: Let's gather bullet points from "What You Will Do" and earlier paragraphs.
Earlier paragraphs before "What You Will Do":
"You will be one of the technical leaders in your immediate team. You will work with other engineers and your Product and Design counterparts to take projects from idea to done with a high degree of autonomy and ownership. You will be responsible for understanding Product requirements and the customer problems they are aiming to solve, distilling them into manageable subparts that can be divided across other engineers on the project. During a project’s execution, you will act as a leader ensuring any technical questions and trade offs are considered pragmatically, with a well-reasoned and understood solution being executed upon. You will guide more junior engineers with technical problems, ensuring that they follow best practices from an engineering and operational excellence perspective. Your influence won’t end once a project ships: you will be relied upon by Product and Design to give an engineering perspective on how we can iteratively improve a product to better benefit our customers. Outside of product-driven projects, you will work with other engineers to determine how to push our platform forward, devising engineering-led initiatives that ensure we can work quickly and efficiently while maintaining a high standard of operational excellence. You will also act as a mentor for more junior engineers, helping them grow from both a technical and career perspective."
Then "What You Will Do" list:
- Work in a startup-like environment building agile products and services
- Collaborate closely with engineers on your team, engineers on other teams, as well as your product and design counterparts to successfully launch projects which solve real-world customer problems
- Act as a strategic partner to Product and Design, using technical insights to influence the product roadmap and proactively suggesting architectural changes that enable new categories of user experiences
- Guide the team to make technical trade offs necessary to bring product initiatives to fruition, weighing different approaches and arriving to a recommended solution, detailing its pros and cons
- Independently define, decompose, and lead delivery of complex projects, may lead other engineers
- Modularization and Architecture. Architect and lead the transition toward a highly modularized codebase to improve build speeds and team fungibility, ensuring our architecture scales with our growing engineering organization.
- Perform code reviews, design reviews, and write high quality tests
- Have a strong stance and advocate for efficient, scalable, and extensible approaches that solve technical problems in a manner that stands the test of time
- Hold yourself and the team to a high standard of code quality and operational rigor, ensuring that code is well-tested, and your systems have appropriate monitoring, alerting, and runbooks implemented
- Become the subject matter expert for one or more services in your domain
- Create clear and concise documentation (diagrams, service descriptions, decisions, runbooks)
- Identify and remove bottlenecks to address inefficiencies in the developer experience
- Oversee and mentor junior engineers on the team, building their technical skills and ensuring that they understand best practices around engineering and operational excellence
We need to include all these as list items under Responsibilities.
Now Qualifications list from "What We Look For":
- BS in CS or equivalent practical experience
- 9+ years of professional Android development experience using Kotlin and shipping apps to the Play Store
- 3+ years of experience with modern Kotlin development practices, such as Jetpack Compose and Flow.
- Experience with Kotlin Multiplatform is a plus but not mandatory
- Ability to collaborate with Product, Design and Engineering stakeholders to implement solutions which surprise and delight our customers
- Master Computer Science fundamentals and Android design patterns and best practices
- A sheer eye for design and attention to detail, the products you build should not merely be functional but should take in context and anticipate our customer’s needs in a beautiful way
- Experience leading the development of a project from planning to release, dispatching work among a team, mentoring and guiding junior engineers
- Experience with AI tools
- Experience integrating with RESTful server-side services
- Experience with Scrum/Agile development methodologies
- Excellent verbal and written communication skills
- Passion about mentoring and helping more junior engineers to grow
We need to keep all.
Now Skills: Could extract technical skills: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform, RESTful services, Scrum/Agile, AI tools, etc. But we might combine Skills with Qualifications; but we have both sections. To avoid duplication, we could put Skills as a separate list of technical competencies: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful services, Scrum/Agile, AI tools, etc. However, the Qualifications already includes many of those. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create a separate Skills section if it would be thin. But we have enough content for Skills? Let's see: we could list: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful services, Scrum/Agile, AI tools. That's maybe 7 items. Could be okay. But we risk duplication with Qualifications. However, we could treat Qualifications as education/experience, and Skills as technical abilities. That seems reasonable.
But we must not invent or summarize away detail. If we put Skills, we need to ensure we include all skills mentioned. The posting mentions: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful server-side services, Scrum/Agile, AI tools. Also "modern Kotlin development practices". Also "Computer Science fundamentals and Android design patterns". Also "design and attention to detail". But those are more qualitative.
We could decide to not have a separate Skills section and instead include technical skills under Qualifications or Responsibilities. Since we already have Qualifications covering many, we could keep only About the role, Responsibilities, Qualifications, Benefits, Pay. That's 5 sections. That seems substantive enough.
Thus we will not create Skills section.
Now Benefits: list from "Perks That You Need To Know About" plus bonuses etc.
We need to list each benefit as
- . The text: "Participation in our incentive programs (which may include eligible cash, equity, or commissions). Plus paid vacation, holidays, sick time, parental leave, and recharge leave; medical, tele-health, dental and vision benefits; 401(k) plan; flexible spending accounts (FSAs); commuter program; life and disability insurance; Maven (a support system for new parents); Carrot (fertility benefits); UrbanSitter (caregiver referral network); Employee Assistance Program; and pet insurance."
Also "Bonuses and restricted stock units may be provided as part of the compensation package, in addition to a full range of benefits."
We should include bonuses and RSUs as part of benefits.
Thus Benefits list items:
- Participation in incentive programs (eligible cash, equity, or commissions)
- Paid vacation
- Paid holidays
- Paid sick time
- Parental leave
- Recharge leave
- Medical benefits
- Tele-health benefits
- Dental benefits
- Vision benefits
- 401(k) plan
- Flexible spending accounts (FSAs)
- Commuter program
- Life and disability insurance
- Maven (support system for new parents)
- Carrot (fertility benefits)
- UrbanSitter (caregiver referral network)
- Employee Assistance Program
- Pet insurance
- Bonuses
- Restricted stock units (RSUs)
We need to keep the exact phrasing? We can keep concise but preserve all info. Not invent.
Now Pay section: We need to include base pay range, note about variation, bonuses and RSUs (but we already listed them under benefits; but we can mention again? The instruction: preserve ALL substantive information; we can include in Pay section the base pay range and note that base pay offered may vary depending
for prose. We must not repeat job title as heading. Not include Job ID. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to be careful not to omit any specifics like "Participation in our incentive programs (which may include eligible cash, equity, or commissions). Plus paid vacation, holidays, sick time, parental leave, and recharge leave; medical, tele-health, dental and vision benefits; 401(k) plan; flexible spending accounts (FSAs); commuter program; life and disability insurance; Maven (a support system for new parents); Carrot (fertility benefits); UrbanSitter (caregiver referral network); Employee Assistance Program; and pet insurance." Also "Bonuses and restricted stock units may be provided as part of the compensation package, in addition to a full range of benefits." Also "Base pay is based on market location. Minimum wage for the position will always be met." Also "Compensation: The base pay range for this position is $131,000-$197,000; however, base pay offered may vary depending on job-related knowledge, skills, and experience." We need to include that in Pay section. Now, we need to decide sections. Potential sections: - About the role (company mission, role description) - Responsibilities (What You Will Do + earlier paragraphs) - Qualifications (What We Look For) - Skills (maybe separate but could be part of Qualifications; but we have enough content for Skills: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform, RESTful services, Scrum/Agile, etc.) - Benefits (Perks That You Need To Know About + bonuses etc.) - Pay (Compensation details) We should not create Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now, we need to extract lists. Responsibilities list: Let's gather bullet points from "What You Will Do" and earlier paragraphs. Earlier paragraphs before "What You Will Do": "You will be one of the technical leaders in your immediate team. You will work with other engineers and your Product and Design counterparts to take projects from idea to done with a high degree of autonomy and ownership. You will be responsible for understanding Product requirements and the customer problems they are aiming to solve, distilling them into manageable subparts that can be divided across other engineers on the project. During a project’s execution, you will act as a leader ensuring any technical questions and trade offs are considered pragmatically, with a well-reasoned and understood solution being executed upon. You will guide more junior engineers with technical problems, ensuring that they follow best practices from an engineering and operational excellence perspective. Your influence won’t end once a project ships: you will be relied upon by Product and Design to give an engineering perspective on how we can iteratively improve a product to better benefit our customers. Outside of product-driven projects, you will work with other engineers to determine how to push our platform forward, devising engineering-led initiatives that ensure we can work quickly and efficiently while maintaining a high standard of operational excellence. You will also act as a mentor for more junior engineers, helping them grow from both a technical and career perspective." Then "What You Will Do" list: - Work in a startup-like environment building agile products and services - Collaborate closely with engineers on your team, engineers on other teams, as well as your product and design counterparts to successfully launch projects which solve real-world customer problems - Act as a strategic partner to Product and Design, using technical insights to influence the product roadmap and proactively suggesting architectural changes that enable new categories of user experiences - Guide the team to make technical trade offs necessary to bring product initiatives to fruition, weighing different approaches and arriving to a recommended solution, detailing its pros and cons - Independently define, decompose, and lead delivery of complex projects, may lead other engineers - Modularization and Architecture. Architect and lead the transition toward a highly modularized codebase to improve build speeds and team fungibility, ensuring our architecture scales with our growing engineering organization. - Perform code reviews, design reviews, and write high quality tests - Have a strong stance and advocate for efficient, scalable, and extensible approaches that solve technical problems in a manner that stands the test of time - Hold yourself and the team to a high standard of code quality and operational rigor, ensuring that code is well-tested, and your systems have appropriate monitoring, alerting, and runbooks implemented - Become the subject matter expert for one or more services in your domain - Create clear and concise documentation (diagrams, service descriptions, decisions, runbooks) - Identify and remove bottlenecks to address inefficiencies in the developer experience - Oversee and mentor junior engineers on the team, building their technical skills and ensuring that they understand best practices around engineering and operational excellence We need to include all these as list items under Responsibilities. Now Qualifications list from "What We Look For": - BS in CS or equivalent practical experience - 9+ years of professional Android development experience using Kotlin and shipping apps to the Play Store - 3+ years of experience with modern Kotlin development practices, such as Jetpack Compose and Flow. - Experience with Kotlin Multiplatform is a plus but not mandatory - Ability to collaborate with Product, Design and Engineering stakeholders to implement solutions which surprise and delight our customers - Master Computer Science fundamentals and Android design patterns and best practices - A sheer eye for design and attention to detail, the products you build should not merely be functional but should take in context and anticipate our customer’s needs in a beautiful way - Experience leading the development of a project from planning to release, dispatching work among a team, mentoring and guiding junior engineers - Experience with AI tools - Experience integrating with RESTful server-side services - Experience with Scrum/Agile development methodologies - Excellent verbal and written communication skills - Passion about mentoring and helping more junior engineers to grow We need to keep all. Now Skills: Could extract technical skills: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform, RESTful services, Scrum/Agile, AI tools, etc. But we might combine Skills with Qualifications; but we have both sections. To avoid duplication, we could put Skills as a separate list of technical competencies: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful services, Scrum/Agile, AI tools, etc. However, the Qualifications already includes many of those. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create a separate Skills section if it would be thin. But we have enough content for Skills? Let's see: we could list: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful services, Scrum/Agile, AI tools. That's maybe 7 items. Could be okay. But we risk duplication with Qualifications. However, we could treat Qualifications as education/experience, and Skills as technical abilities. That seems reasonable. But we must not invent or summarize away detail. If we put Skills, we need to ensure we include all skills mentioned. The posting mentions: Kotlin, Jetpack Compose, Flow, Kotlin Multiplatform (plus), RESTful server-side services, Scrum/Agile, AI tools. Also "modern Kotlin development practices". Also "Computer Science fundamentals and Android design patterns". Also "design and attention to detail". But those are more qualitative. We could decide to not have a separate Skills section and instead include technical skills under Qualifications or Responsibilities. Since we already have Qualifications covering many, we could keep only About the role, Responsibilities, Qualifications, Benefits, Pay. That's 5 sections. That seems substantive enough. Thus we will not create Skills section. Now Benefits: list from "Perks That You Need To Know About" plus bonuses etc. We need to list each benefit as