Before you apply
Program evidence and scope
The current early-career page centers on Apex for software engineers and product managers. It targets new graduates and candidates with one to three years of experience, describes a cohort of roughly 15–20 and places the experience in the greater Phoenix headquarters area. It includes a bootcamp, team integration and continuing learning. [2]
More details
Pay, location and conditions
No verified undergraduate hourly rate, housing allowance or relocation package was established in the reviewed official materials. Apex's headquarters-area location does not establish a remote arrangement or intern relocation benefit. [2]
Pay & location
Compensation, location and practical fit
Ask for compensation in the form applicable to the role: hourly pay for a student placement, or base salary and any separate components for a graduate offer. Do not compare the two by annualizing a short internship and assuming identical hours or benefits. Confirm the reporting site, attendance expectations and any travel before evaluating the practical cost.
For an operations placement, location can also determine the nature of the work. Ask whether the assignment involves a facility, customer contact or a corporate office, and whether the schedule includes nonstandard hours. Those are questions to resolve with the team, not assumptions this report makes about every Carvana employee.
Work, teams and company background
Jump to a section
Apex: a verified early-career route, not an undergraduate summer program
Dated role · 2026-09-04
That is a relevant future path for students approaching graduation, but it should not be counted as a summer internship for someone returning to college. The distinction affects eligibility, duration and the kind of application evidence expected. A current undergraduate can use the page to understand what the employer values while continuing to search for an actual student requisition.
The value of a cohort should also be examined rather than assumed. Ask how much work happens on the assigned team, what the bootcamp covers and how performance is assessed after the initial training. A small cohort does not by itself establish selectivity, mentorship quality or a guaranteed career trajectory.
Undergraduate internship status and recruiting discipline
Dated role · 2026-09-04
Maintain a separate watchlist for future graduate opportunities. That prevents an appealing Apex application from displacing work on eligible summer roles. For networking, ask a focused question about which team hires students and when a direct requisition normally appears. A useful response should lead to a real posting or a clear explanation of the team's hiring plan, not just a broad careers link.
Application strategy and the decision to prioritize
Carvana is most compelling for students who want to understand how software and analysis affect a physical customer transaction. Build a portfolio around that connection: a small operational analysis, a product experiment with a defensible metric or a reliable application that handles messy inputs.
Make the employer-specific argument concrete. Explain why vehicle commerce presents an interesting problem and which part of it you have already investigated. Avoid repeating slogans about disruption or AI. A candidate who can discuss a trade-off calmly will be more credible than one who claims every problem can be solved with a new model.
The Apex application asks for evidence of building
Apex applicants are asked for a three-to-five-minute video explaining interest in Carvana, the engineering-versus-product choice and a project they built. The page describes year-round review, with hiring increasing in fall for January cohorts and spring for June cohorts. These are stated patterns, not a specific guaranteed deadline. [2]
The best preparation is a short project narrative with visible evidence. Begin with the user or operating problem. Explain the most consequential choice, show the result and identify what did not work. A product candidate should demonstrate more than a presentation of an idea; an engineering candidate should demonstrate more than a list of technologies.
Keep the video focused on work you can discuss openly. Do not include proprietary dashboards, customer information or an employer's internal code. A simple, functioning project with clear reasoning is easier to evaluate than an ambitious claim that cannot be inspected. The goal is to make your contribution understandable, not to imitate the company's promotional language.
Business and internship context
Automotive commerce, physical operations and technology careers: the Apex graduate program is not a summer internship
A technology employer with a physical operating system
The student proposition is the connection between digital decisions and real operating outcomes. A change to a customer flow may affect support work. A change to inventory or logistics may affect the delivery promise. A useful analyst or product candidate should be interested in that relationship rather than treating Carvana as a conventional app with cars in the interface.
The employer also has operational roles outside corporate technology. A customer-care placement, an inspection-center assignment and a software role should be evaluated separately. Start with the actual team and location. The same company name can describe very different daily work and different paths after graduation.
Technology and product work
A product candidate should be able to connect a proposed change to a user problem and an operating constraint. For example, a more optimistic delivery estimate may improve an early funnel metric while increasing later cancellations or support contacts. A good analysis asks how to measure the complete result rather than celebrating the first positive number.
An engineering candidate can demonstrate the same judgment through a small system that handles failure cleanly. Show what happens when a record is duplicated, a dependency is unavailable or a user changes a request. Document the trade-offs instead of implying that a prototype is production-ready. A designer can show how research changed an interface decision and which uncertainty remains.
Operations and analytics: follow the exceptions
The combination of digital commerce and physical vehicle operations makes process analysis a natural preparation theme. This is an inference from the company's described model, not a verified list of intern duties. [1], [2]
A student interested in operations should ask whether the role is based in a corporate team, a logistics operation, an inspection facility or customer support. A spreadsheet-based planning assignment differs from direct frontline work even when both involve operational improvement. Ask how much time is spent observing the process, analyzing data and implementing a change.
For an analytical portfolio, use a synthetic dataset of vehicle-processing milestones. Identify where the longest delays occur, distinguish missing timestamps from true zero-duration events and show how outliers affect the conclusion. Add one recommendation that could be tested without redesigning the entire operation. Explain the cost of a false conclusion. That approach demonstrates care with imperfect data and makes a stronger case than a dashboard with no decision attached.
Employee experience: separate promotional claims from evidence
Carvana's Apex page presents an ambitious, fast-moving environment with early ownership, mentoring and a peer cohort. Those are employer-authored descriptions. The small interview sample reviewed here concerns candidate interactions, not a representative account of employee workload, management or satisfaction. [2], [4]
A candidate who enjoys close contact between technology and operations may value this environment. Someone seeking a narrowly defined research role or a predictable academic-style project should investigate the assignment carefully. That is a fit assessment based on the work described, not a judgment that one preference is superior.
Trace the economics of a delayed vehicle handoff
Use fictional purchase, reconditioning, inventory and delivery records to analyze a delay. Separate time waiting from time spent on work, then compare an operational response with its cost. State which assumptions would need confirmation from the team. A marketplace or analytics application should show the decision supported, not merely interest in cars.
Hypothetical preparation exercise, not an employer assessment or a verified internship assignment.
How to reason about the business before interviewing
Carvana's own early-career description connects technology with reconditioning, supply chain, logistics, ecommerce, financing and customer care. [2] The useful preparation is to understand a vehicle transaction as a chain of dependent steps.
Consider a hypothetical vehicle that is acquired, inspected, prepared, listed and delivered. At each step, ask what information must be correct before the next step can proceed. Then ask which metric could improve locally while making the end-to-end result worse. Faster processing is not necessarily better when it creates more rework or an unreliable customer promise.
A business candidate can build a simple process model using invented, clearly labeled data. Track elapsed time, queue size and exceptions rather than only averages. Explain where a manager would need better information before changing staffing or capacity. This is an author-created work sample suggestion, not a disclosed Carvana operating procedure or interview case.
Interview evidence and technical preparation
Candidate report · 2026-09-04
A Glassdoor Strategy Analyst account posted September 2, 2026 described a completed recruiter conversation and reported being told that later stages could include SQL and a mixed technical/behavioral panel. The candidate had not yet completed those later stages. An August 23 Staff Accountant account described a single online conversation about relevant experience. Neither was identified as an internship. [4]
For product interviews, practice choosing a metric and explaining its limitations. For engineering, practice a detailed walkthrough of your own implementation and failure handling. For operations, be ready to explain an observed process before proposing changes. The preparation should follow the work, not a collection of unrelated interview questions.
Finance and commercial reasoning
The second-quarter 2026 release reported net income of $513 million and adjusted EBITDA of $769 million. Those are different measures, and the release provides a reconciliation. A candidate should not describe adjusted EBITDA as cash flow or treat unit growth as a complete explanation of economics. [1]
For a finance-oriented application, prepare to explain the difference between selling more vehicles and improving the economics of each transaction. Use hypothetical assumptions to examine price, acquisition cost, preparation, delivery and financing-related effects, while clearly separating what the public source establishes from what the model assumes. Do not present invented unit economics as Carvana data.
A useful discussion also considers timing. Cash committed before a vehicle is sold creates a different operating problem from a purely digital transaction. Explain how you would test a proposed improvement under slower sales or higher processing costs. This is a candidate reasoning exercise, not investment advice or a claim about the company's internal forecasting model.
Research context
Carvana operates an online platform for buying, selling, financing and trading vehicles, supported by physical infrastructure and technology. In its July 29, 2026 release, it reported 197,325 retail units sold and $7.376 billion in second-quarter revenue. Those figures describe the company's scale; they do not establish student hiring volume or the quality of a particular assignment. [1]
The recruiting observations below retain the dates in the underlying research. They are not a live vacancy list.