2 min lesson
The loop at a glance
Rebuild the sequence in "The loop at a glance" from memory, ending with the check that proves the outcome.
Step 1 of 3
The current Software Engineer, Infrastructure posting publishes one sequence: 2–3 short technicals, then an in-office onsite where you work on a small project, discuss ideas and meet the team. It does not publish the technical topics, timeboxes, tool rules, project format or scoring. Use recruiting and the current invitation to confirm those details.
Build a preparation map with two columns: what the posting actually says and what remains open. For each short technical, ask about the topic, timebox, language and tools. For the onsite, ask about the schedule, project scope, working setup, permitted tools and expected output.
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
Only the sequence and onsite activities below are published. Confirm every unnamed constraint with recruiting.
Learn more
Advanced table
The official posting is the authority for the published loop
- Loop element or detail
- 2–3 short technicals
- Published status
- Published
- Next action
- Confirm the topic and order of each one
- Loop element or detail
- Technical timeboxes
- Published status
- Not published
- Next action
- Ask recruiting and follow the current invitation
- Loop element or detail
- Technical languages and tools
- Published status
- Not published
- Next action
- Confirm before choosing a rehearsal setup
- Loop element or detail
- In-office onsite
- Published status
- Published
- Next action
- Confirm schedule and practical logistics
- Loop element or detail
- Small project
- Published status
- Published onsite activity
- Next action
- Confirm scope, duration, setup, tools and output
- Loop element or detail
- Idea discussions and team meetings
- Published status
- Published onsite activities
- Next action
- Prepare grounded views and questions; confirm the format
| Loop element or detail | Published status | Next action |
|---|---|---|
| 2–3 short technicals | Published | Confirm the topic and order of each one |
| Technical timeboxes | Not published | Ask recruiting and follow the current invitation |
| Technical languages and tools | Not published | Confirm before choosing a rehearsal setup |
| In-office onsite | Published | Confirm schedule and practical logistics |
| Small project | Published onsite activity | Confirm scope, duration, setup, tools and output |
| Idea discussions and team meetings | Published onsite activities | Prepare grounded views and questions; confirm the format |
The official posting is the authority for the published loop; recruiting and the current invitation are the authority for missing details.
Role-relevant coding, design and project drills can still help, but they are not confirmed interview topics. Once recruiting provides a timebox, tool rule or expected output, rehearse under that exact constraint.
The posting does not name a recruiter screen, take-home, design round, past-work round, behavioral round or hiring-manager round. Prepare for one only if recruiting puts it on your current schedule.
QWhat does the current posting publish, and what must you still confirm before building an Infrastructure interview preparation plan?