Target Technology Internship 2027: Coding Assessment, HireVue, and Interview Process

A Target technology internship can put you inside the systems that connect product discovery, stores, inventory, checkout, payments, fulfillment, and delivery. That breadth also makes the interview harder to predict from a single candidate post: one role may begin with a skills assessment, another may use HireVue, and a software engineering team may add paired programming or a practical coding exercise.

Target publishes useful guidance about each format, but it does not publish one universal 2027 technology-internship sequence, coding question count, or passing score. This guide separates the official process from older candidate reports and gives you a preparation plan that remains useful when your invitation differs from someone else's.

Quick answer: what should candidates expect?

Expect a role-dependent process that may include an online skills assessment, a recorded HireVue interview, and one or more live technical conversations. Target's official hiring page says some applications require supplemental information or a quick job-related assessment. It also lists recorded video, phone, virtual, and in-person interviews as possible formats.

For technical roles, Target's own Tech Interview Prep Guide says the interview may include paired programming, a review of your body of work, or coding exercises. That is the strongest preparation signal: write correct code, explain trade-offs, defend projects, and connect technical decisions to guest and business impact.

Then shape practice around the exact role description.

What is official, reported, and still unknown?

Claim	Evidence level	How to use it
Target internship applications open in the fall and are reviewed on a rolling basis until roles are filled.	Official	Apply early, but keep the resume specific to the role.
Some applications require a quick assessment of job-related skills.	Official	Prepare for an assessment without assuming every candidate receives one.
Target may use recorded video, phone, virtual, or in-person interviews depending on role and location.	Official	Follow your invitation rather than a generic sequence.
Technical interviews may include paired programming, body-of-work review, or coding exercises.	Official	Practice coding and project explanation as one connected skill.
An older SWE intern report described a Target Tech Day followed by two programming questions and a decision within two weeks.	Candidate-reported, 2022	Use it as historical context, not a 2027 guarantee.
All 2027 technology interns receive the same HireVue, coding platform, question count, or cutoff.	Not confirmed	Do not state these details unless they appear in your invitation.

The likely Target technology interview path

1. Workday application and resume review

Target accepts applications through Workday and reviews internship applications on a rolling basis. A strong technology resume should make the technical match visible quickly: language, system, contribution, scale, test or reliability improvement, and measurable result.

Do not describe every course and tool. Select projects that prove you can build, debug, collaborate, and learn inside an engineering team. If the posting mentions distributed systems, cloud platforms, data, mobile, frontend, security, or store technology, place the closest evidence near the top.

2. Role-based assessment

Target officially says some applications may include a quick job-related skills assessment. It does not publicly specify one universal technology-intern platform, timer, or score. The assessment could therefore differ across software engineering, data, UX, infrastructure, and other Target Tech roles.

If your invitation contains coding, treat it as an engineering sample rather than a puzzle contest. Clarify constraints, select a data structure deliberately, handle edge cases, test before submitting, and keep the code readable. For non-coding assessments, answer from your own judgment and the role's requirements.

3. Recorded HireVue interview

Target's recorded-video page says candidates should search for an email from “Target Careers” and “Hirevue.” The interview is designed to take about 30 minutes. You watch each introduction and question, record a response, and may have an opportunity to re-record; Target says it only sees the final version submitted.

Target also says a recruiter or hiring manager watches the responses along with the resume and application. That matters: do not perform for an imaginary facial-scoring algorithm. Give a clear, evidence-based answer that a human reviewer can connect to the role.

4. Live technical interview

Target's technical guide names three possible formats: paired programming, body of work, and coding exercises. A team may combine them. You might write or debug code while explaining your approach, then discuss how the same design behaves under scale, failure, security, or business constraints.

An older intern report described two programming questions, including object-oriented and open-ended design themes. Because that report is several years old, use it only to broaden practice. The current official guide and your recruiter remain more authoritative.

5. Decision and pre-hire steps

If selected, Target says the written offer appears through Workday or arrives after recruiter contact. The candidate then completes pre-hire screening and required documents in the Candidate Homepage.

If you are not selected, Target's hiring FAQ says you may apply to similar or alternate roles, though the system may prevent reapplication to the exact same requisition. Keep notes on the role, assessment, and feedback so the next application is more targeted.

How to prepare for the coding assessment

Make core data structures dependable

Prioritize arrays, strings, hash maps, sets, sorting, stacks, queues, trees, graphs, intervals, and basic dynamic programming. The goal is not to finish a giant list. It is to solve common medium-level problems without losing time to syntax, unclear invariants, or untested boundaries.

Use the same sequence every time: restate the problem, confirm inputs and outputs, describe a simple approach, select the right structure, implement, test, and analyze complexity. Consistency makes your performance more reliable when the timer or interviewer adds pressure.

Expect retail-shaped engineering constraints

Retail systems create practical follow-ups: duplicate events, cart updates from multiple devices, stale prices, inventory races, payment retries, flash-sale traffic, fulfillment state, and regional failures. A coding question may remain self-contained, but showing awareness of these concerns makes your reasoning more relevant to Target Tech.

For example, an “add item” function raises questions about quantity limits, invalid SKUs, idempotency, and concurrent writes. A stock lookup raises questions about freshness and overselling. Name these concerns after you have solved the required prompt; do not overengineer before establishing correctness.

Test the hidden edges

Before submission, test empty or minimum input, one element, duplicates, maximum values, already-sorted data, invalid identifiers, and cases that trigger every branch. If money appears, avoid binary floating-point unless the prompt explicitly permits it. If an operation can be retried, consider whether it produces the same result twice.

State time and space in terms of real input dimensions. If you use a hash map, mention average-case assumptions. If output storage dominates space, separate required output from auxiliary memory. Precise analysis is more credible than a memorized “O(n).”

How to succeed in the HireVue

Build six reusable stories

Prepare stories for collaboration, conflict, learning, failure, ownership, and impact. Target's interview guide explicitly asks about background and preparation, working with people who think differently, partnering to find creative solutions, and ensuring work is impactful.

Use context, goal, action, result, and reflection. Keep the situation short and spend most of the answer on what you personally did. Quantify the result when possible, then explain what you would repeat or change.

Connect every answer to the role

A technology HireVue answer should not sound like a generic retail interview. If asked about teamwork, explain the technical disagreement, how you gathered evidence, and how the team reached a decision. If asked about impact, connect the implementation to latency, reliability, user experience, cost, risk, or delivery speed.

A polished first answer is not enough if you cannot explain the trade-off, stakeholder, failure, or lesson.

Use the recording format correctly

Test your camera, microphone, browser, connection, lighting, and framing before starting. Target recommends completing a practice question. Look toward the camera, speak in complete sentences, and stop when the answer is complete rather than filling every remaining second.

Target's current hiring page says candidates must answer from their own knowledge and experience without relying on external AI-generated assistance during interviews. Prepare beforehand, but keep the submitted response genuinely yours.

What the live technical interview may evaluate

Paired programming

Paired programming evaluates collaboration as much as final code. Narrate decisions, ask clarifying questions, respond to feedback, and keep the program runnable. If the interviewer suggests a change, restate the new requirement and update the design deliberately.

Do not disappear into silence while typing. Short reasoning statements are enough: what you are implementing, what invariant you are preserving, and what you will test next.

Body-of-work discussion

Choose one project you understand from requirements through production behavior. Explain the architecture, your contribution, key constraint, rejected alternative, test strategy, failure you encountered, and measurable result. Be ready to draw the data flow and identify the least reliable dependency.

Target's internship description emphasizes building and testing tools through collaboration. Strong project answers therefore show both technical ownership and how you worked with others to ship something useful.

Coding or design exercise

A design exercise may begin at class level or service level. Clarify scope before drawing. Define entities, invariants, APIs, state transitions, and failure behavior. In retail scenarios, consistency at checkout may matter more than freshness on a browse page.

Make trade-offs visible. Explain when to cache, when to require a transaction, how to make retries safe, and what you would monitor. A simple design with explicit boundaries is stronger than an elaborate diagram with no correctness argument.

How long does the process take?

Target says recorded-video responses are reviewed with the resume and application, and that candidates should receive next steps within five business days after the video is received. That is a useful published expectation for the HireVue stage, not a guarantee that the entire internship process finishes in one week.

Scheduling live interviews, team capacity, application volume, and location can extend the overall timeline. An older SWE intern report described a decision within two weeks after the programming round, but the age of that report makes it unsuitable as a 2027 service level.

If five business days pass after HireVue without an update, verify that the submission shows complete and send one concise follow-up. Include the role title, requisition ID, completion date, and a polite request for status. Continue other applications while waiting.

A seven-day preparation plan

Day	Focus	What to do
Day 1	Role and baseline	Review the posting, map resume evidence, and complete one timed coding diagnostic.
Day 2	Core coding	Practice arrays, strings, hash maps, sorting, and boundary tests.
Day 3	Data structures	Practice trees, graphs, queues, heaps, and complexity explanations.
Day 4	Retail engineering	Work through cart, inventory, checkout, idempotency, and concurrency scenarios.
Day 5	HireVue	Record six behavioral answers and improve clarity, evidence, and pacing.
Day 6	Paired interview	Run a live coding or design mock with narration and follow-ups.
Day 7	Final review	Retest failed cases, rehearse one project, confirm logistics, and stop cramming.

Frequently asked questions

Does every Target technology applicant receive a coding assessment?

No official Target source reviewed for this guide says every technology applicant receives one. Target says some applications may require a quick job-related assessment. The role and invitation determine your process.

Is the Target HireVue automated?

Target says a recruiter or hiring manager watches the final video responses and reviews them with the resume and application. Prepare for a human reviewer and answer from your own experience.

How long is the Target recorded video interview?

Target recommends planning about 30 minutes for the total recorded interview. Individual response limits can vary, so watch the timer shown for each question.

Can you re-record Target HireVue answers?

Target's recorded-video page says candidates have a chance to re-record and that Target only sees the final recording submitted. Follow the exact controls shown in your invitation.

What coding difficulty should I expect?

Target does not publish a universal 2027 difficulty. Prepare reliable easy-to-medium algorithms, clean implementation, testing, object-oriented design, and practical engineering trade-offs.

What happens after the HireVue?

Target says a recruiter or hiring manager reviews the video, resume, and application and typically communicates next steps within five business days. A technology candidate may then receive a live technical interview, but role-specific sequences vary.

Final preparation advice

The most effective Target preparation is not guessing whether HireVue comes before coding. It is building evidence that transfers across formats: correct and tested code, a project you can defend, practical retail-system judgment, and behavioral stories that show inclusion, collaboration, growth, and impact.

Work through software engineering interview questions with written solutions, keep a mistake log, and rehearse the explanation until you can remain clear in a timed assessment, recorded response, or paired interview.

Sources and further reading

• Target Internships
• Target Hiring Process
• Target Recorded Video Interviews
• Target Tech Interview Prep Guide
• Target Recruiter Interview Tips

Research note: This guide was checked on August 20, 2026. Target can change assessment vendors, interview order, role scope, and timelines. Your invitation and recruiter instructions take priority.