Junior Software Engineer
GM Performance Power Units
About the Role
GM Performance Power Units is developing and building a Formula 1 power unit. As a Junior Software Engineer on our growing team, you will build the software and data products needed to make better decisions faster. In this fast-paced, one-team startup environment, you will own real products early, work directly with users, and help shape how the team builds software.
Key Responsibilities
- Design and build data-intensive software: data models, databases, APIs, data pipelines, integrations, user interfaces, and cloud services.
- Work with Information Security and the wider Digital Technology Group to deliver secure, reliable solutions.
- Build, deploy, monitor, and continuously improve production systems using metrics and user feedback.
- Use agentic AI while understanding, validating, and owning the result.
Requirements & Tech Stack
- Bachelor's degree in a STEM field with at least 1 year of experience (including internships and substantial projects), or at least 3 years of equivalent practical experience.
- Software development experience in a modern programming language.
- Working knowledge of data modeling, databases, APIs, version control, testing, debugging, and secure development practices.
- Demonstrated ability to discover problems, learn new approaches and technologies quickly, and apply them to working software.
- Strong problem-solving, communication, and ownership skills.
Preferred Qualifications:
- Python, Go, TypeScript/JavaScript, or similar.
- Data modeling with relational, JSON, vector, or columnar data (e.g., Parquet).
- AWS, CI/CD with GitHub, infrastructure as code (e.g., CloudFormation or Terraform), observability, or DevSecOps practices.
- Web applications, event-driven systems, semantic search, RAG, or MCP.
- Experience in Motorsports, manufacturing, aerospace, or a similar technical environment.
- Formula SAE, STEM Racing, robotics, industrial or embedded controls, or a comparable technical project.
Application Requirement
Please include a link to something you've built (e.g., a repository, project, or write-up) and a few sentences on why this role interests you.