Software Engineer Intern, Mobile (Winter 2027)

We need to output HTML fragment with sections for headings where there is real specific content. The posting includes: About the job (some prose), Key Responsibilities, Required Skills & Abilities, compensation info (Pay), schedule (internship dates Jan - Apr, location SF/NY office). Also mention "Full Time" but it's an internship? It says Full Time but also internship 12-week. We'll treat schedule: Jan - Apr (maybe mention duration). Benefits: mention "highly competitive cash compensation, equity, and benefits." Not specific benefits details, so we should not create Benefits section unless specific. Pay: we have estimated hourly range: $57/hr for Bachelors or $61/hr for Master’s for SF/NYC. That's specific, so include Pay section. We should not repeat job title. No Job ID. Remove boilerplate like "Apply now", "Please let Notion know you found this job on Job Vista.", etc. Also remove duplicated lines. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting has "About The Job" (we can map to About the role). It has "Key Responsibilities". It has "Required Skills & Abilities" (could be Skills or Requirements). It has compensation (Pay). It has schedule (Jan - Apr, need to work out of SF or NY office). It does not have explicit Benefits details beyond generic statement, so we should not create Benefits section. Also no explicit Qualifications separate from Skills; we could combine. We need to use

• for any list of duties/requirements/benefits. The responsibilities are in prose paragraphs, not a list. Could we turn them into list? The instruction: Use
  • for any list of duties/requirements/benefits. If the original is not a list, we can keep as

    . So we keep responsibilities as

    . For skills, there is a list of abilities (many bullet-like sentences). Could format as

    • . We'll extract each ability as list item. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting: about the job description (the paragraphs about Notinos, mobile devices, etc.), responsibilities (the paragraphs about writing code, collaborating, etc.), required skills and abilities (list of items), compensation details, schedule (Jan - Apr, need to work out of SF or NY office). Also mention that it's a 12-week internship, paired with mentor, etc. Also mention that you need to graduate before Dec 2027. Also mention previous mobile internship experience. Also mention proficiency in languages list. Also mention problem solving traits, etc. Also mention tech stack proficiency list. Also mention interests outside tech. Also mention Notion's commitment to compensation etc. Also mention AI curiosity statement. Also mention that you don't need deep AI expertise but expect intellectual curiosity. Also mention that for some roles AI fluency is core requirement (but not this). Also mention that you need to be able to work out of SF or NY office during this time. We need to avoid boilerplate like "Apply now", "Please let Notion know you found this job on Job Vista.", "Job Overview Company Notion Location Hybrid..." etc. Also remove "About Company Industry Information Technology Founded 2016 View Company Profile ⟶ Quick Actions". Also remove "Deadline Mar 24, 2027". Also remove "Posted Today". Also remove "Full Time". Also remove "Negotiable". Also remove "Hybrid (San Francisco, California, United States)" maybe we keep location? The location is given in the job heading but we might keep as part of schedule? Actually location is not a section; we could embed location in schedule or as a short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. Location is minor metadata; we could include in a short p at top maybe. But we need to preserve ALL substantive information; location is substantive? It's given in the job header; but we could include as a short p. However the instruction says "fold minor metadata into a short

      or drop it." Location might be considered minor metadata; but it's still substantive? I'd include a short p with location. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

      Location: Hybrid (San Francisco, California, United States)

      Then sections:

      About the role

      ... (the about job paragraph(s))...

      We need to include the about job text: "Notinos (our employees) are customer zero in bringing this future of work to life. We care about craft, building things that last, and the belief that great work is still fundamentally human. Our goal isn’t to ship the next feature. Each and every team of Notinos is working to set the standard for how humans work to... Mobile devices have reshaped personal computing—the power of a desktop now fits in our pockets. By giving everyone the building blocks to create their own tools, we'll solve more problems wherever we go. A delightful, intuitive mobile experience: that's our guiding light, and we need Android and iOS engineers to mak... During your 12-week internship, you will be paired with a mentor that will help guide you as you work closely with our team to build and ship impactful projects. These projects will drive valuable impact to our customers and engineers. Take a look at what our past intern cohort worked on with our Blog post here and ..." We need to preserve all; but there are ellipses indicating truncated. We'll keep as is. Then responsibilities:

      Responsibilities

      Mobile devices have reshaped personal computing—the power of a desktop now fits in our pockets. By giving everyone the building blocks to create their own tools, we'll solve more problems wherever we go. A delightful, intuitive mobile experience: that's our guiding light, and we need Android and iOS engineers to make it a reality. Write clean, secure, tested, and documented code. You'll collaborate with the team to strategize, mold, and develop innovative features for our Android and iOS application. At our core, we prioritize crafting top-tier applications. Your role could involve enhancing the Android or iOS app's performance, reliability, and overall refinement. Additionally, you'll have the opportunity to optimize aspects of the app within the web stack.

      Then skills/abilities: We could use

      Skills

      with
      • items. List items from "Required Skills & Abilities": - Pursuing a Bachelor's or Master’s degree in computer science, engineering, or another related field. - Must graduate before December 2027. - Previous mobile internship experience. - Working towards a proficiency of one or more programming languages such as Kotlin, Java, Typescript, Node.js, Swift, Go, Python, or Rust. - You find large challenges exciting and enjoy discovering problems as much as solving them. - You are able to problem-solve and adapt to changing priorities in a fast-paced, dynamic environment. - This internship will take place from Jan - Apr and you will need to be able to work out of our SF or NY office during this time. (Actually schedule, but we could keep here or schedule section.) - Thoughtful problem-solving: For you, problem-solving starts with a clear and accurate understanding of the context. You can decompose tricky problems and work towards a clean solution, by yourself or with teammates. You're comfortable asking for help when you get stuck. - Put users first: You think critically about the implications of what you're building, and how it shapes real people's lives. You understand that reach comes with responsibility for our impact—good and bad. - Not ideological about technology: To you, technologies and programming languages are about tradeoffs. You may be opinionated, but you're not ideological and can learn new technologies as you go. - Empathetic communication: You communicate nuanced ideas clearly, whether you're explaining technical decisions in writing or brainstorming in real time. In disagreements, you engage thoughtfully with other perspectives and compromise when needed. - Team player: For you, work isn't a solo endeavor. You enjoy collaborating cross-functionally to accomplish shared goals, and you care about learning, growing, and helping others to do the same. - You're proficient with any part of our technology stack: Kotlin, Jetpack Compose, Android SDK, Dagger, Swift, React, TypeScript, Postgres. - You've heard of computing pioneers like Ada Lovelace, Douglas Engelbart, Alan Kay, and others—and understand why we're big fans of their work. - You have interests outside of technology, such as in art, history, or social sciences. - Notion is committed to providing highly competitive cash compensation, equity, and benefits. (maybe benefits but we skip) - The compensation offered for this role will be based on multiple factors such as location, the role’s scope and complexity, and the candidate’s experience and expertise, and may vary from the range provided below. For roles based in San Francisco or New York City, the estimated hourly range for this role is $57/hr for Bachelors or $61/hr for Master’s. - By clicking “Submit Application”, I understand and agree that Notion and its affiliates and subsidiaries will collect and process my information in accordance with Notion’s Global Recruiting Privacy Policy and NYLL 144. (boilerplate legal, should remove) - You don’t need deep AI expertise for every role, but we do expect every Notino to be intellectually curious, drawn to tinkering and discovery, and excited to use AI as a real collaborator in their work. For some roles, AI fluency is a core requirement — when that’s the case, we'll say so explicitly in the qualifications. People who thrive here don’t treat AI as a novelty. They use it to think better, and make their work easier for others to build on. We need to remove boilerplate like legal, application instructions, etc. Also remove "By clicking Submit Application..." and "You don't need deep AI expertise..." maybe keep the AI curiosity part as it's substantive about expectations. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI curiosity is not boilerplate; it's about expectations, so keep. Also remove "For some roles, AI fluency is a core requirement — when that’s the case, we'll say so explicitly in the qualifications." That's generic; maybe keep? It's still about AI expectation but generic. Might be considered boilerplate? It's a statement about AI fluency being core requirement for some roles; not specific to this role. Could be considered filler. Safer to remove. We need to keep the compensation details (Pay section). So we should extract compensation into Pay section, not inside Skills. Thus Skills section should contain the skills/abilities list excluding compensation and schedule and legal etc. Schedule section: we have "This internship will take place from Jan - Apr and you will need to be able to work out of our SF or NY office during this time." Also mention it's a 12-week internship, paired with mentor. Also mention Full Time? We'll include schedule: 12-week internship, Jan - Apr, need to work out of SF or NY office. We could also include location in schedule or separate p. Let's create sections:

        Schedule

        This is a 12‑week full‑time internship running from January through April. Interns are expected to work out of the San Francisco or New York office during this period and will be paired with a mentor to guide their work.

        We need to preserve the exact phrasing? We should not invent or summarize away detail. The original says: "This internship will take place from Jan - Apr and you will need to be able to work out of our SF