Software Engineer, II - Map Enablement

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Company", "Meet the Team", "What You'll Do", "What you'll need", "Bonus Points", "Perks of Being a Full-time Torc’r". Also there is a hiring range and pay range. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info. Remove boilerplate like EEO, etc. Also remove application instructions, cookie/navigation/legal, duplicated lines. Also remove Job ID line? It says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include Job ID in a short paragraph maybe, but better to drop it? It says fold minor metadata into a short

or drop it. So we can include a

with Job ID and maybe hiring range? But Pay section we need to include if posting actually states them. It does: "Hiring Range for Job Opening: US Pay Range $139,000 - $166,800". Also earlier: "Our compensation reflects the cost of labor across several geographic markets. Pay is based on a number of factors and may vary depending on job-related knowledge, skills, and experience. Torc's total compensation package will also include our corporate bonus and stock option plan. Dependent on the position offered, sign-on payments, relocation, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits." That's somewhat vague but includes pay range. We should include Pay section with that range. Also Benefits: they list perks: competitive compensation package includes bonus component and stock options, 100% paid medical, dental, vision premiums, 401K plan with 6% employer match, flexibility in schedule and generous paid vacation, company-wide holiday office closures, AD+D and Life Insurance. Also mention flexibility in schedule (so schedule). We could have Benefits section and maybe Schedule section (flexibility in schedule). But we should avoid thin sections. Perhaps combine Benefits and Schedule into Benefits? But rules: Use headings for Benefits, Pay, Schedule etc. We need to include a section only when posting has real specific content. It does have schedule: "Flexibility in schedule and generous paid vacation". So we can have Schedule section with that. Benefits section can list medical, dental, vision, 401k, AD&D, Life Insurance, bonus, stock options, paid vacation, holiday closures. That's substantive. Now responsibilities: "What You'll Do" list. We'll put under

Responsibilities

with

• . Requirements/Qualifications: "What you'll need" includes education, experience, skills. Could split into Requirements and Qualifications? But we can combine into Requirements. However we have separate headings for Requirements, Qualifications, Skills. We need to decide. The posting includes: Bachelor’s Degree ... plus experience OR Master’s Degree ... plus experience. Solid knowledge of at least one programming language (C++, Python), Python preferred. Experience with AWS services ... Experience building and operating high-throughput data processing pipelines. Demonstrated ability to work through vague or shifting requirements and independently propose a technical path forward. Strong technical communication skills ... Strong problem-solving skills ... Experience with source control and agile workflows such as GitHub and JIRA. That's qualifications/skills. Bonus Points: Understanding of geospatial data concepts ... Knowledge of machine learning techniques for geospatial data analysis Experience with high-definition mapping Experience scaling autonomous systems Prior experience in navigation or the automotive industry. We could have Requirements (education + experience) and Skills (technical skills). But we have limited headings. Perhaps use Requirements for education/experience, Skills for technical skills, and Bonus Points could be under Skills as a sublist? But we must not invent sections with filler. We can include a Skills section that includes both required and bonus? Might be okay. But we need to preserve all info. Let's structure:

  About the Company

  maybe? The rules list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the Company but we could use About the role? However the posting has "About The Company". We could treat that as About the role? But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those exact headings when applicable. But we can also use other headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use those headings for sections. Probably we should map content to those headings. So we need sections: About the role (maybe summarizing the role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must not create sections with filler. So we need to see if we have content for each. - About the role: we have "Meet the Team: Torc's Map Enablement team is looking for a Software Engineer to help deliver and scale its mapping and routing system..." That's about the role. So we can put that under About the role. - Responsibilities: "What You'll Do" list. - Requirements: education + experience (Bachelor's/Master's plus years). Could also include "Solid knowledge of at least one programming language (C++, Python), Python preferred." That's more skill. But we can put under Requirements. - Qualifications: maybe the AWS experience, data processing pipelines, ability to work through vague requirements, communication, problem-solving, source control, agile workflows. That's qualifications. - Skills: maybe the bonus points? Or we could put technical skills under Skills, and bonus points under Skills as well. But we need to avoid duplication. Perhaps we put required technical skills under Skills, and bonus points under Skills as a separate list labeled "Bonus Points". But we cannot create a heading for Bonus Points unless we map to existing headings. Could we put bonus points under Skills as a sub-list? That's okay. - Benefits: perks list. - Pay: hiring range. - Schedule: flexibility in schedule. We must not repeat job title as heading. We'll not. We must not include boilerplate like EEO, etc. We'll remove. We need to output only HTML fragment. Let's craft:

  About the role

  Torc's Map Enablement team is looking for a Software Engineer to help deliver and scale its mapping and routing system in preparation for Torc's commercial expansion. A strong technical foundation in delivering data processing pipelines and APIs is important for this role, along with the judgment to make sound design decisions when requirements are loosely defined. This individual will collaborate with engineering teams that use Map Enablement's software, creating tailored solutions and turning feedback into features.

  Responsibilities

  • Design and build scalable, cost-effective mapping and routing data pipelines and services in preparation for commercial launch.
  • Take ambiguous or partially-defined problems from internal customers and drive them to a concrete technical design, scoping tradeoffs independently before looping in senior engineers.
  • Work with Map Enablement and neighboring teams to understand customer needs and translate them into well-scoped features.
  • Participate in and provide substantive feedback on technical design and code reviews.
  • Promote operational excellence by implementing effective testing, monitoring, and alerting for Map Enablement's services and pipelines.
  • Participate in the on-call rotation to support the health of our services.
  • Contribute to project planning, helping shape priorities based on customer expectations and technical constraints.
  • Uphold a culture of collaboration, transparency, creativity, inclusion, and data-driven decision-making.

  Requirements

  • Bachelor’s Degree in Computer Science, Robotics, Electrical Engineering or related technical field plus demonstrates competences and technical proficiencies typically acquired through 4+ years of experience OR Master’s Degree in Computer Science, Robotics, Electrical Engineering or related technical field plus demonstrates competences and technical proficiencies typically acquired through 0-3+ years of experience.
  • Solid knowledge of at least one programming language (C++, Python), Python preferred.

  Qualifications

  • Experience with AWS services (S3, Lambda, Step Functions, IAM, EventBridge, Glue, Athena).
  • Experience building and operating high-throughput data processing pipelines.
  • Demonstrated ability to work through vague or shifting requirements and independently propose a technical path forward.
  • Strong technical communication skills, written and verbal, that scale across a diverse workforce.
  • Strong problem-solving skills and the ability to analyze and debug complex software defects.
  • Experience with source control and agile workflows such as GitHub and JIRA.

  Skills

  • Understanding of geospatial data concepts and tools (GeoJSON, PostGIS, QGIS, OSM, etc.)
  • Knowledge of machine learning techniques for geospatial data analysis
  • Experience with high-definition mapping
  • Experience scaling autonomous systems
  • Prior experience in navigation or the automotive industry

  Benefits

  • Competitive compensation package that includes a bonus component and stock options
  • 100% paid medical, dental, and vision premiums for full-time employees
  • 401K plan with a 6% employer match
  • Flexibility in schedule and generous paid vacation (available immediately after start date)
  • Company-wide holiday office closures
  • AD+D and Life Insurance

  Pay

  US Pay Range $139,000 - $166,800 (hiring range for this opening).

  Schedule

  Flexibility in schedule.

  We need to ensure we didn't include any boilerplate like "Even if you don’t meet 100%..." etc. We removed that. Also removed "At Torc, we’re committed to building a diverse and inclusive workplace..." etc. Also removed "Our compensation reflects the cost of labor..." etc. We kept pay range. Also removed "Job ID: 102971". We could include it as a short paragraph maybe but it's minor metadata; we can drop it. The instruction: fold minor metadata into a short

  or drop it. We dropped it. Check for any duplicated lines: we didn't repeat. Check for any placeholder text like "commensurate with experience" etc. Not present. Check for any missing info: We omitted "Meet the Team:" line but we captured the substance in About the role. Good. We omitted "Now a part of the Daimler family, we are focused solely on developing software for automated trucks to transform how the world moves freight." That's part of About The Company. Should we include that? It's substantive about company. Under About the role we could incorporate that. Let's add to About the role paragraph: include that Torc is a part of Daimler family, focused on developing software for automated trucks, etc. Also mention "A leader in autonomous driving since 2007, Torc has spent over a decade commercializing our solutions with experienced partners." That's also company info. We'll incorporate. Thus About the role paragraph: combine. Let's rewrite About the role:

  Torc,