Software Engineering Intern - Connected Systems (January - August 2027)

We need to output HTML fragment with sections: About the role? The posting includes "About Us", "Role Summary", "Specific Project Areas", "Responsibilities", "Qualifications", "Total Rewards". Also includes "Candidates should be available for a full-time commitment from January 11, 2027 to August 13, 2027." That's schedule info. Also compensation range: $40 - $51 (presumably hourly). So we need sections: About the role? Actually "About Us" could be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have "About Us" describing the joint venture; we can put under

About the role

maybe. Or "About Us" could be considered "About the role". We'll include that. We have Role Summary and Specific Project Areas: could be part of About the role or separate? Probably combine into About the role. Responsibilities: we have a list. Qualifications: we have Minimum and Preferred. Total Rewards: includes compensation, benefits, equity, etc. We need to separate Pay and Benefits and maybe Schedule. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to include Pay if compensation range given: yes $40 - $51. So we create

Pay

with that. Schedule: we have commitment dates Jan 11 2027 to Aug 13 2027 full-time. So we can create

Schedule

with that. Benefits: we have description of benefits package: health coverage, retirement savings, time off, family planning programs, etc. So we can create

Benefits

with that list. We also have equity (RSUs) mentioned under Total Rewards; could be part of Benefits or Pay? Probably Benefits. We need to avoid duplication, boilerplate, EEO, legal, etc. Remove all that. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "Currently enrolled in a Bachelor's or Master's program at an accredited US university", "Proficient in at least one of Python, Go, C++, or Java", etc. We need to use

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

  for prose. We must not repeat the job title as a heading. The job titles are listed: Connectivity Software Engineering Intern, Embedded Software Engineering Intern - Vehicle Access, etc. We should not repeat them as headings. We'll just not include them. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  ... (About Us + Role Summary + Specific Project Areas)

  But we need to keep specifics: About Us paragraph, Role Summary paragraph, Specific Project Areas bullet list. We can combine into one

  for prose and maybe a

  for specific project areas. Better:

  About the role

  Rivian and Volkswagen Group Technologies is a joint venture between two industry leaders with a clear vision for automotive’s next chapter. From operating systems to zonal controllers to cloud and connectivity solutions, we’re addressing the challenges of electric vehicles through technology that will set the standards for software-defined vehicles around the world. The road to the future is uncharted. By combining our expertise across connectivity, AI, security and more, we’ll map a new way forward. Working together, we’ll create a future that’s more connected, more intelligent, more sustainable for everyone.

  At RV Tech, we develop next-gen vehicle features that include remote commands from mobile apps, OTA software updates, real time vehicle telemetry, and fleet management tools. All of which rely on cloud, connectivity, and integration software working together at scale. As a Connected Systems intern, you will work on the backend services, integration layers, or connectivity infrastructure that keep vehicles talking to the cloud reliably. This may involve high throughput data pipelines, distributed cloud services, or the software that validates features work end to end across the vehicle.

  Specific Project Areas

  • Building and testing backend services that process vehicle telemetry and remote commands at fleet scale
  • Developing event driven, distributed systems using tools such as Kafka, Kinesis, or Redis
  • Contributing to cross domain systems integration and validation work, ensuring vehicle features function correctly end to end
  • Supporting connectivity infrastructure, including the messaging and communication layers linking vehicle, mobile app, and cloud
  • Working with cloud native infrastructure on AWS (EKS, Lambda, DynamoDB, IoT Core)
  But the instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't list Specific Project Areas as a standard heading, but we can still use

  for it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g. ...)". Likely they expect only those headings. However, we could embed Specific Project Areas under About the role as a list. But they said "Prefer a few substantive sections over many thin ones." So maybe we should not create a separate Specific Project Areas heading; instead incorporate those bullet points under About the role or Responsibilities. However, Responsibilities already list duties. Specific Project Areas are more like possible projects; could be considered part of About the role. Let's incorporate them under About the role as a

  . Thus About the role section will have prose paragraphs and a
  for project areas. Next Responsibilities: we have a list. Qualifications: we have Minimum and Preferred. Could be combined under Qualifications heading. Pay: compensation range. Schedule: commitment dates. Benefits: description of benefits package. We must not include Requirements heading separately if we have Qualifications; but we could treat Qualifications as Requirements. The instruction list includes Requirements as an example heading; we can use Qualifications. We must not include Skills heading unless we have specific skills; we have proficiency in languages etc. Could be part of Qualifications. Thus final sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Benefits. Let's craft. About the role: include About Us paragraph, Role Summary paragraph, and a
  of Specific Project Areas. Responsibilities: list as
  . Qualifications: we have Minimum and Preferred. Could present as
  with items; but we need to keep the distinction? We could keep as prose: Minimum: ... Preferred: ... but better as
  with items, maybe separate subheadings? But we cannot add extra headings. Could just list all qualifications as
  • items, preserving the text. That's fine. Pay:

    Compensation range: $40 - $51 (hourly).

    Schedule:

    Full-time commitment from January 11, 2027 to August 13, 2027.

    Benefits: we have description: "In addition to a competitive base salary, full-time positions may be is eligible to participate in our annual company performance bonus program. Payments are discretionary and not guaranteed; actual amounts depend on company results and the terms of the plan in effect, and require active employment at the time of payout. This role is also eligible for equity in the form of Restricted Stock Units (RSUs), subject to board approval and the terms of our equity incentive plans, including applicable vesting requirements. In addition to our compensation programs, we invest in our people with a comprehensive benefits package designed to support the health, wellbeing, and financial future for full-time employees — including health coverage, retirement savings, time off, and family planning programs. Offerings vary by country. Learn more about our global benefit programs." We need to preserve all substantive information. So we will put that as

    maybe with a

    for the benefits list: health coverage, retirement savings, time off, family planning programs. Also mention bonus program, equity RSUs, etc. We should not include the sentence "Learn more about our global benefit programs." as it's a link; but we can keep as prose. Let's construct. Check for any boilerplate to remove: "External candidates can apply for this role through the Rivian and Volkswagen Group Technologies careers site (https://rivianvw.tech/#careers). If you are a current employee, please apply through our internal job board." That's application instructions; remove. EEO, Candidate Data Privacy, etc. Remove. Also remove "Please note this job posting represents an open, active vacancy. Additionally, we are not currently accepting applications from third party application services." That's boilerplate; remove. Now produce HTML. Let's write:

    About the role

    Rivian and Volkswagen Group Technologies is a joint venture between two industry leaders with a clear vision for automotive’s next chapter. From operating systems to zonal controllers to cloud and connectivity solutions, we’re addressing the challenges of electric vehicles through technology that will set the standards for software-defined vehicles around the world. The road to the future is uncharted. By combining our expertise across connectivity, AI, security and more, we’ll map a new way forward. Working together, we’ll create a future that’s more connected, more intelligent, more sustainable for everyone.

    At RV Tech, we develop next-gen vehicle features that include remote commands from mobile apps, OTA software updates, real time vehicle telemetry, and fleet management tools. All of which rely on cloud, connectivity, and integration software working together at scale. As a Connected Systems intern, you will work on the backend services, integration layers, or connectivity infrastructure that keep vehicles talking to the cloud reliably. This may involve high throughput data pipelines, distributed cloud services, or the software that validates features work end to end across the vehicle.

    • Building and testing backend services that process vehicle telemetry and remote commands at fleet scale
    • Developing event driven, distributed systems using tools such as Kafka, Kinesis, or Redis
    • Contributing to cross domain systems integration and validation work, ensuring vehicle features function correctly end to end
    • Supporting connectivity infrastructure, including the messaging and communication layers linking vehicle, mobile app, and cloud
    • Working with cloud native infrastructure on AWS (EKS, Lambda, DynamoDB, IoT Core)

    Responsibilities

    • Design, develop, and test software components within an existing distributed or connectivity system
    • Write clean, maintainable code in Python, Go, C++, or Java depending on the team
    • Participate in code reviews, design discussions, and debugging sessions with your team
    • Contribute to test automation and validation for integration or connectivity features
    • Document your work and present progress to your team throughout the internship

    Qualifications

    • Currently enrolled in a Bachelor's or Master's program at an accredited US university
    • Proficient in at least one of Python, Go, C++, or Java
    • Actively pursuing a degree in Computer Science, Computer Engineering, Electrical Engineering, or a closely related field, with intent to return to school after the internship
    • Exposure to distributed systems, event driven architecture, or cloud platforms, AWS preferred
    • Familiarity with vehicle communication protocols