Jobs · Information Technology · Georgia

Summer 2027: Mobile Software Engineering Intern - iOS

Intuit · Atlanta, GA · 1 mo ago
On-siteInformation Technology$35.5–$79.42/hrVolunteer
We need to output HTML fragment with sections: Overview? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: Overview (but it's about eligibility, internship length, cohorts). Could be considered "About the role" or maybe "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly. We have "Overview" content: eligibility, internship length, cohort dates. That could go under "About the role". Also there is "About Our Emerging Talent Program" which is more about program description; could be part of "About the role" as well. We have "Responsibilities" list. We have "Qualifications" list (including many items). Also there is "Skills" maybe separate but we can combine. We have Pay info: expected base pay range $35.50-$79.42/hr. Also location-specific ranges but they are zeros (likely placeholder). We should not include Pay section if content is just placeholder? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state expected base pay range, so we can include Pay section with that range. The location-specific zeros are likely placeholder; we should not include them as they are not substantive. So we include Pay with the range. We have no explicit Benefits or Schedule beyond internship length and cohort dates; schedule could be derived from cohort dates (fixed start and end dates). The instruction: include Schedule section only if posting actually states them. It does state fixed start and end dates, cohort dates. So we could include Schedule section with those dates. Benefits: Not explicitly listed besides relocation stipend mentioned in qualifications. There's mention "Relocation stipend will be provided". That's a benefit. Also maybe "competitive compensation package". But we should not invent. We have relocation stipend. Could be included under Benefits. We also have "Intuit provides a competitive compensation package with a strong pay for performance rewards approach." That's generic; maybe not needed. We need to avoid boilerplate like EEO etc. Not present. We need to preserve all substantive info. Let's structure:

About the role

... overview about eligibility, internship length, cohort dates, program description.

Maybe we split overview into two paragraphs: eligibility and program. Then

Responsibilities

  • ... each responsibility.
Then

Qualifications

  • ... each qualification.
Then

Skills

maybe not needed if qualifications cover skills. But we could separate skills like "Experience building iOS applications..." etc. However qualifications already include many skill-like items. To avoid thin sections, we could combine qualifications and skills into one Qualifications section. The instruction: prefer a few substantive sections over many thin ones. So we can have Qualifications covering all qualification/skill items. Then

Benefits

  • Relocation stipend provided.
Maybe also mention "competitive compensation package" but that's vague. Then

Pay

The expected base pay range for this position is: $35.50‑$79.42 per hour.

Then

Schedule

Intuit internships are 12 weeks throughout the summer with fixed start and end dates designed to work with various universities’ academic calendars. Cohort 1: Monday, May 17 – Friday, August 6, 2027. Cohort 2: Monday, June 14 – Friday, September 3, 2027.

We must not repeat job title. Not include Job ID. We must output only HTML fragment. Check for any duplicated lines: In qualifications there is repeated sentence about compensation package repeated twice; we should include only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate. The duplicated lines: "Intuit provides a competitive compensation package with a strong pay for performance rewards approach." appears twice. Also "Pay offered is based on factors such as job-related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender." appears twice. We should keep only one instance each. We need to decide where to put that info. It's about compensation philosophy; could be part of Pay section or Benefits? Probably Pay section. We'll include a short paragraph in Pay section summarizing that. But we must not invent; we can include that statement as part of Pay section. Thus Pay section could have:

The expected base pay range for this position is: $35.50‑$79.42 per hour. Intuit provides a competitive compensation package with a strong pay for performance rewards approach. Pay offered is based on factors such as job‑related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender.

We should not repeat that sentence twice. Now Benefits: we have relocation stipend. Also maybe "competitive compensation package" but that's covered in Pay. We'll keep Benefits with relocation stipend. Now check for any other boilerplate: "Learn more about our Intern and Co-op Program here." That's a link; we should remove application instructions and maybe that line is not substantive? It's a link to learn more; could be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about our Intern and Co-op Program here." is like a call to action; maybe considered application instruction? It's not exactly application instruction but could be considered navigation. Safer to remove it. Also "As a Mobile Software Engineer Intern - iOS, you'll help build..." that's substantive role description; we can include in About the role. Now we need to ensure we don't include any headings with empty content. Let's draft HTML. We'll need to escape any special characters? Not needed. Let's write:

About the role

To qualify for US internships, you must be currently enrolled in a degree‑seeking program with an expected graduation date after the internship/co‑op ends. Intuit internships are 12 weeks throughout the summer with fixed start and end dates designed to work with various universities’ academic calendars. Cohort 1: Monday, May 17 – Friday, August 6, 2027; Cohort 2: Monday, June 14 – Friday, September 3, 2027.

Intuit’s Emerging Talent program invests in fresh perspectives that strengthen products and teams. As a Mobile Software Engineer Intern – iOS, you’ll help build the mobile experiences that let millions of consumers and small businesses manage their finances anytime, anywhere — across TurboTax, QuickBooks, Credit Karma, and Mailchimp. You’ll write production Swift code alongside experienced engineers, using AI tools to move faster and think bigger, and see your work reach real customers by the end of the summer. You’ll be supported by dedicated managers and mentors, work on meaningful projects with business impact (many centered on AI and emerging technologies), build skills through function‑specific learning opportunities, connect with a global community of interns and co‑ops, and get exposure to senior leadership and cross‑functional work across Intuit's product ecosystem.

Responsibilities

  • Design, build, and test features for Intuit's iOS applications, from UI to the services they call.
  • Write clean, well‑tested Swift code, and participate in code reviews to help the team hold a high bar.
  • Debug and resolve defects across the app, learning to trace issues from the UI down through the stack.
  • Partner with engineers, designers, and product managers to turn requirements into working software.
  • Use AI‑assisted development tools to accelerate your own workflow, and share what you learn with the team.
  • Support the deployment and ongoing maintenance of features you help ship.

Qualifications

  • Current enrollment in a degree‑seeking program (associate’s, bachelor's, master's, MBA, PhD, or the equivalent) with an expected graduation date after the internship ends.
  • Familiarity with AI tools and a curiosity about how AI can be applied to solve real‑world problems.
  • Must be legally authorized to work in the United States on a full‑time basis for the duration of the internship.
  • Ability to work in a hybrid environment at an Intuit office location determined by your team and role (relocation stipend will be provided).
  • Experience building iOS applications, ideally with Swift or Objective‑C.
  • Familiarity with iOS application architecture and development frameworks (e.g., SwiftUI, UIKit, Combine, MVVM).
  • Working knowledge of Swift, Objective‑C, Python, and Java.
  • Comfort partnering with designers and backend engineers to connect mobile apps to cloud‑based APIs.
  • Familiarity with Agile development methodologies and the software development lifecycle.
  • A “self‑starter” attitude with the ability to take initiative and make independent decisions.
  • Strong problem‑solving skills and a history of successfully delivering on assigned tasks.
  • Desire to learn and grow within a technical environment.
  • Excellent verbal and written communication skills.

Benefits

  • Relocation stipend provided.

Pay

The expected base pay range for this position is: $35.50‑$79.42 per hour. Intuit provides a competitive compensation package with a strong pay for performance rewards approach. Pay offered is based on factors such as job‑related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender.

Schedule

Intuit internships are 12 weeks throughout the summer with fixed start and end dates designed to work with various universities’ academic calendars. Cohort 1: Monday, May 17 – Friday, August 6, 2027. Cohort 2: Monday, June 14 – Friday, September 3, 2027.

Check for any duplicated content: We have repeated mention of internship length and cohort dates in About the role and Schedule. That's okay; it's substantive but could be considered duplication. However instruction: remove duplicated lines. The internship length and cohort dates appear in both sections. Might be considered duplicated. We could avoid duplication by placing schedule details only in Schedule section, and in About the role just mention eligibility and program description without repeating schedule. Let's adjust. In About the role we can mention eligibility and program description, but not repeat schedule. We'll keep schedule details only in Schedule section. Thus About the role paragraph: eligibility and program description. Let's rewrite About the role:

To qualify for US internships, you must be currently enrolled in a degree‑seeking program with an expected graduation date after the internship/co‑op ends. Intuit’s Emerging Talent program invests in fresh perspectives that strengthen products and teams. As a Mobile Software Engineer Intern – iOS, you’ll help build the mobile experiences that let millions of consumers and small businesses manage their finances anytime, anywhere — across TurboTax,

Similar jobs