CarGurus
Frontend Engineer II, Competitive Intelligence
About this role
CarGurus is hiring a Software Development Engineer II to build next-generation analytics and dealer-facing products for their automotive marketplace. You'll work full-stack across React, Java, and AWS, collaborating with cross-functional teams to ship competitive intelligence features for dealerships.
What you'll do
- Develop and deploy clean, well-tested, efficient code with high architectural and performance standards
- Support and improve core systems while maintaining quality for internal stakeholders
- Collaborate with data analysts and product managers through design, implementation, testing, and performance measurement
- Build dealer-facing products from the ground up as part of the Competitive Intelligence team
- Iterate and ship ideas quickly while working independently
What they're looking for
- React and JavaScript
- Java
- SQL
- AWS (certification preferred)
- Distributed systems and microservice architecture
- Data structures and algorithms
- AI coding tools
- Quick learning and technical problem-solving
Benefits
- Equity for all employees
- Competitive base salary ($112,000–$141,000) plus potential RSUs and bonuses
- Hybrid work model with flexible scheduling
- Comprehensive time off policies
- Daily free lunch, car discounts, fitness/meditation apps, and commuting cost coverage
Opens the official application on the employer’s site. No login required.
CarGurus
CarGurus operates an automotive marketplace platform that helps consumers find, compare, and purchase vehicles through search, mobile, and engagement tools. The company is hiring Software Development Engineers II across multiple teams to build and optimize backend services, search infrastructure, AI-powered consumer experiences, developer tooling, and email personalization features that serve millions of users globally.
- Website
- cargurus.com
Likely interview questions
- Walk us through your experience building full-stack features with React and Java. How have you approached the division of responsibilities between frontend and backend?
- Describe a time when you had to iterate and ship an idea quickly and independently. What was your process, and how did you ensure code quality under time pressure?