Staff Prototyping Engineer, Android

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Salesforce, About Slack, The Team, The Role, What You'll Do, What We're Looking For, Preferred Qualifications, Unleash Your Potential, Benefits (salary range). We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should only include sections when posting has real specific content. We need to map content to appropriate headings. We have: - About Salesforce (company overview) – could be "About the role"? Actually "About the role" is a heading for role description. But we have separate "About Salesforce" is company description; maybe we can treat as "About the role"? Not exactly. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those standard headings. We need to decide which sections map. We have content: "About Salesforce", "About Slack", "The Team", "The Role", "What You'll Do", "What We're Looking For", "Preferred Qualifications", "Unleash Your Potential", benefits (salary range). Also mention accommodations etc but we should remove boilerplate. We need to produce sections only when there is real specific content. Potential sections: - About the role: could combine "About Salesforce", "About Slack", "The Team", "The Role". But maybe better to have separate sections: "About the role" (role description), "Responsibilities" (What You'll Do), "Requirements" (What We're Looking For), "Qualifications" (Preferred Qualifications), "Skills" (maybe combine), "Benefits" (salary range and benefits), "Pay" (salary range), "Schedule" (not present). We should not create empty sections. We have salary range info: "The typical base salary range for this position is $197,300 - $313,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $237,700 - $344,700 annually." That's pay info. Also benefits: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." So we have benefits. Thus we can have sections: - About the role (company/team overview) - Responsibilities (What You'll Do) - Requirements (What We're Looking For) - Qualifications (Preferred Qualifications) - Benefits (benefits list) - Pay (salary range) We should not include Schedule as not present. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like bullet points. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus for each section we need to decide if content is prose or list. Let's extract content: About Salesforce: paragraph about Salesforce being #1 AI CRM etc. About Slack: paragraph about Slack being Digital HQ. The Team: paragraph about Slack Mobile team. The Role: paragraph describing role as Staff Engineer/Prototyping Engineer. What You'll Do: list of bullet points starting with "You will:" then bullet points each starting with a verb. We need to convert those bullet points to

  • . What We're Looking For: list of bullet points (starting with "8+ years..." etc). Also includes "A related technical degree required." maybe as separate bullet. Preferred Qualifications: list of bullet points. Benefits: list of benefits (time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program). Also maybe mention accommodations? but we remove boilerplate. Pay: salary range paragraphs. We need to ensure we don't include filler like "commensurate with experience". Not present. We must not include duplicated lines. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the accommodations paragraph, AI tools statement, Privacy Statement, Posting Statement about equal opportunity, etc. Also remove "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months..." etc. Also remove "Job Category Software Engineering". Also remove "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's promotional but maybe considered boilerplate? It's part of "Unleash Your Potential". Might be considered substantive? It's more marketing but still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Unleash Your Potential" is not exactly those; it's a motivational section. Might keep? But we need to decide if we want a section for it. Could be part of "About the role" or separate "Overview". But we have limited headings. Could incorporate into About the role. Better to keep only sections we defined. Thus we will produce:

    About the role

    About Salesforce ... About Slack ... The Team ... The Role ...

    maybe combine into paragraphs. But we need to preserve all substantive information; we can't omit details. So we need to include all those paragraphs. We can separate into multiple

    elements. Thus:

    About the role

    About Salesforce: Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.

    About Slack: Slack is your Digital HQ — bringing people, apps, customers, and AI agents together in one place. Millions of people use Slack every day to communicate, collaborate, and get work done. As work becomes increasingly distributed and AI-powered, Slack is redefining how teams operate and achieve at scale. In this AI era, Slack’s mission remains making people’s work lives simpler, more pleasant, and more productive.

    The Team: The Slack Mobile team builds Slack's mobile experiences, from core messaging to AI and everything in between. We operate at the intersection of product innovation, mobile platform excellence, and large-scale engineering. The features and systems we build support millions of daily users and require deep investments in performance, reliability, accessibility, and user experience.

    The Role: We’re looking for a Staff Engineer to help shape the future of Slack’s mobile product. As a Prototyping Engineer, you’ll embed as a leader on greenfield, zero-to-one initiatives. You’ll influence product and design direction through engineering work that builds and ships the first versions of newly-imagined, fully working product features. You’ll work closely with Product, Design, Backend, and fellow mobile engineers to help innovate some of the biggest new product opportunities for Slack, with experiences that are intuitive, performant, and reliable for millions of users worldwide.

    Then Responsibilities:

    Responsibilities

    • Shape the future of Slack on mobile by leading the engineering development of experiences used by millions of users every day, spanning multiple teams and the broader organization.
    • Lead the most complex, ambiguous, cross-functional initiatives from early technical exploration through production rollout and long-term evolution.
    • Lead feature prototyping to define the mobile user experience for Slack’s biggest opportunities.
    • Partner closely with Product and Design to shape experiences that balance user needs, technical constraints, and long-term maintainability.
    • Influence engineering decisions beyond your immediate team through technical leadership, product reviews, and mentorship.
    • Set and evangelize best practices for mobile feature development and operational excellence across the broader engineering organization.
    • Mentor senior engineers and contribute to the growth of the broader mobile engineering community within Slack.
    Note: The bullet list originally had "A related technical degree required." after the bullet list? Actually it's at end of "What You'll Do" paragraph: "A related technical degree required." Should we include that as a requirement? It's a requirement. Could be placed under Requirements. But it's after the bullet list. We'll include it maybe as a separate bullet under Requirements. Now Requirements (What We're Looking For):

    Requirements

    • 8+ years of professional software engineering experience, including significant experience building complex, high-craft Android applications at scale.
    • Proven track record of moving outside of organizational boundaries to start new initiatives, prototype the path to production, and reorient the organization to support the new initiative.
    • Experience working in fast-paced environments, whether at a start-up, in an incubator, or on a zero-to-one team inside a larger enterprise.
    • Proven track record of leading large, ambiguous, org-spanning technical initiatives with significant business impact.
    • Deep expertise in Kotlin framework and modern Android development.
    • Strong understanding of Android architecture, application lifecycle, concurrency, networking, and performance optimization.
    • Demonstrated ability to influence product and technical direction through expertise and collaboration, driving alignment across executive stakeholders, Engineering/Product/Design leadership, and multiple teams.
    • A bias toward ownership, execution, and continuous improvement, with the judgment to prioritize the highest-leverage work across the organization.
    • A related technical degree required.
    Now Qualifications (Preferred Qualifications):

    Qualifications

    • Experience with Jetpack Compose and modern Android architecture patterns.
    • Experience with Combine Concurrency (async/await, actors), and dependency injection frameworks (e.g. Needle, Resolver).
    • Experience leading large-scale new products, features, or product transformations spanning multiple teams or the whole org.
    • Experience using research, usability testing, data, and experimentation to ground decisions and uncover opportunities.
    • Contributions to open source projects or the Android community, or other external recognition of technical leadership.
    • Experience building collaboration, productivity, messaging, AI, or enterprise software products.
    • Excellent communication skills.
    • Strong product intuition and a passion for creating exceptional user experiences.
    Now Benefits:

    Benefits

    • time off programs
    • medical
    • dental
    • vision
    • mental health support
    • paid parental leave
    • life and disability insurance
    • 401(k)
    • employee stock purchasing program
    Now Pay:

    Pay

    The typical base salary range for this position is $197,300 - $313,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $237,700 - $344,700 annually.