Senior Android Engineer
Compass · Aventura, FL · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes mission, description, responsibilities, requirements, perks/benefits. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines.
We need to parse the posting.
Let's extract sections:
- Intro: "At Compass, our mission is to help everyone find their place in the world. Founded in 2012, we’re revolutionizing the real estate industry with our end-to-end platform that empowers residential real estate agents to deliver exceptional service to seller and buyer clients. We are looking for an experienced Android engineer to help Compass build a platform that makes the home buying or selling experience delightful." This is about the role/company. Could be "About the role" or maybe "About Compass". We'll use "About the role".
- Then responsibilities: "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 there is a heading "What You Will Do" with bullet-like sentences. Those are also responsibilities. We'll combine.
List of responsibilities (maybe bullet list). We'll create
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines.
We need to parse the posting.
Let's extract sections:
- Intro: "At Compass, our mission is to help everyone find their place in the world. Founded in 2012, we’re revolutionizing the real estate industry with our end-to-end platform that empowers residential real estate agents to deliver exceptional service to seller and buyer clients. We are looking for an experienced Android engineer to help Compass build a platform that makes the home buying or selling experience delightful." This is about the role/company. Could be "About the role" or maybe "About Compass". We'll use "About the role".
- Then responsibilities: "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 there is a heading "What You Will Do" with bullet-like sentences. Those are also responsibilities. We'll combine.
List of responsibilities (maybe bullet list). We'll create - for each duty.
Let's extract bullet points from "What You Will Do":
- 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
Also earlier responsibilities: "You will be one of the technical leaders..." etc. Could be merged but we can keep them as part of responsibilities list.
Now requirements/qualifications: "What We Look For" list:
- 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 can categorize as Requirements (maybe Qualifications). We'll use "Requirements" heading.
Now Benefits/Perks: "Perks That You Need To Know About" list:
- 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 later: "Do your best work, be your authentic self..." that's culture, not benefit. Also "As an equal opportunity employer..." is boilerplate to remove.
Also "Notice for California Applicants Los Angeles County Fair Chance Notice" is legal boilerplate to remove.
Pay and Schedule: Not mentioned. So we should NOT include Pay or Schedule sections.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to output HTML fragment only, no or . Use
for each heading, then content:
for prose,
- for lists.
We need to preserve all substantive info, not invent.
Let's craft.
About the role: combine intro paragraph(s). Could be two paragraphs: mission statement and looking for Android engineer. We'll put as
.
Responsibilities: list items. We'll combine earlier responsibilities and the "What You Will Do" list into one
. Ensure no duplication. Some items may overlap (e.g., mentor junior engineers appears both). We'll keep unique.
Let's compile unique responsibilities:
From first paragraph:
- Be one of the technical leaders in your immediate team.
- Work with other engineers and Product/Design counterparts to take projects from idea to done with high autonomy and ownership.
- Understand Product requirements and customer problems, distilling them into manageable subparts that can be divided across other engineers.
- Act as a leader ensuring technical questions and trade-offs are considered pragmatically, with well-reasoned solution executed.
- Guide more junior engineers with technical problems, ensuring they follow best practices from engineering and operational excellence perspective.
- Influence Product and Design post-ship to give engineering perspective on iterative product improvements.
- Work with other engineers outside product-driven projects to push platform forward, devising engineering-led initiatives for quick, efficient work while maintaining operational excellence.
- Act as a mentor for more junior engineers, helping them grow technically and career-wise.
From "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 merge duplicates: "Guide more junior engineers..." vs "Oversee and mentor junior engineers..." similar. We'll keep both but maybe combine? Better to keep unique but not duplicate. We'll keep both but maybe rephrase? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines should be removed. So we need to detect duplicate lines. The two are similar but not identical; one says "Guide more junior engineers with technical problems, ensuring that they follow best practices from an engineering and operational excellence perspective." The other says "Oversee and mentor junior engineers on the team, building their technical skills and ensuring that they understand best practices around engineering and operational excellence." They are not identical but convey similar idea. Are they considered duplicated? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines means exact duplicate lines. These are not exact duplicates, so we keep both.
Now list responsibilities as - .
Now Requirements: list items as
- .
Now Benefits: list items as
- .
We need to ensure we don't include headings with empty content.
Now produce HTML.
Let's craft.
About the role: maybe two paragraphs: mission and looking for Android engineer.
Paragraph1: "At Compass, our mission is to help everyone find their place in the world. Founded in 2012, we’re revolutionizing the real estate industry with our end-to-end platform that empowers residential real estate agents to deliver exceptional service to seller and buyer clients."
Paragraph2: "We are looking for an experienced Android engineer to help Compass build a platform that makes the home buying or selling experience delightful."
Now responsibilities list.
Now requirements list.
Now benefits list.
Let's write.
Check for any leftover boilerplate: "Do your best work, be your authentic self." That's culture but not a benefit; could be considered part of About the role? It's a statement about culture. Might be considered substantive? It's not a boilerplate; it's about culture. Could be included in About the role as another paragraph. However the instruction: "Prefer a few substantive sections over many thin ones." We could add to About the role. It's not a heading. We'll add as a paragraph after the second.
Also "Our collaborative, energetic culture is grounded in our Compass Entrepreneurship Principles and our commitment to diversity, equity, inclusion, growth and mobility." That's also culture. Could be added.
But we need to decide if we include them. They are substantive info about company culture. Not boilerplate. So we should preserve.
Thus About the role may
for each heading, then content:
for prose,
- for lists.
We need to preserve all substantive info, not invent.
Let's craft.
About the role: combine intro paragraph(s). Could be two paragraphs: mission statement and looking for Android engineer. We'll put as
. Responsibilities: list items. We'll combine earlier responsibilities and the "What You Will Do" list into one
- . Ensure no duplication. Some items may overlap (e.g., mentor junior engineers appears both). We'll keep unique.
Let's compile unique responsibilities:
From first paragraph:
- Be one of the technical leaders in your immediate team.
- Work with other engineers and Product/Design counterparts to take projects from idea to done with high autonomy and ownership.
- Understand Product requirements and customer problems, distilling them into manageable subparts that can be divided across other engineers.
- Act as a leader ensuring technical questions and trade-offs are considered pragmatically, with well-reasoned solution executed.
- Guide more junior engineers with technical problems, ensuring they follow best practices from engineering and operational excellence perspective.
- Influence Product and Design post-ship to give engineering perspective on iterative product improvements.
- Work with other engineers outside product-driven projects to push platform forward, devising engineering-led initiatives for quick, efficient work while maintaining operational excellence.
- Act as a mentor for more junior engineers, helping them grow technically and career-wise.
From "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 merge duplicates: "Guide more junior engineers..." vs "Oversee and mentor junior engineers..." similar. We'll keep both but maybe combine? Better to keep unique but not duplicate. We'll keep both but maybe rephrase? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines should be removed. So we need to detect duplicate lines. The two are similar but not identical; one says "Guide more junior engineers with technical problems, ensuring that they follow best practices from an engineering and operational excellence perspective." The other says "Oversee and mentor junior engineers on the team, building their technical skills and ensuring that they understand best practices around engineering and operational excellence." They are not identical but convey similar idea. Are they considered duplicated? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines means exact duplicate lines. These are not exact duplicates, so we keep both.
Now list responsibilities as
- .
Now Requirements: list items as
- .
Now Benefits: list items as
- . We need to ensure we don't include headings with empty content. Now produce HTML. Let's craft. About the role: maybe two paragraphs: mission and looking for Android engineer. Paragraph1: "At Compass, our mission is to help everyone find their place in the world. Founded in 2012, we’re revolutionizing the real estate industry with our end-to-end platform that empowers residential real estate agents to deliver exceptional service to seller and buyer clients." Paragraph2: "We are looking for an experienced Android engineer to help Compass build a platform that makes the home buying or selling experience delightful." Now responsibilities list. Now requirements list. Now benefits list. Let's write. Check for any leftover boilerplate: "Do your best work, be your authentic self." That's culture but not a benefit; could be considered part of About the role? It's a statement about culture. Might be considered substantive? It's not a boilerplate; it's about culture. Could be included in About the role as another paragraph. However the instruction: "Prefer a few substantive sections over many thin ones." We could add to About the role. It's not a heading. We'll add as a paragraph after the second. Also "Our collaborative, energetic culture is grounded in our Compass Entrepreneurship Principles and our commitment to diversity, equity, inclusion, growth and mobility." That's also culture. Could be added. But we need to decide if we include them. They are substantive info about company culture. Not boilerplate. So we should preserve. Thus About the role may
- .
Now Benefits: list items as
- .
Now Requirements: list items as