C++ Object Layout Interview Questions: Alignment, Padding, and Portable Assumptions

Object-layout questions reward careful scope. Alignment and padding explain why a struct can be larger than the sum of its visible members, yet a byte diagram drawn for one ABI should not be passed off as a portable C++ guarantee. Strong candidates calculate a plausible layout under stated assumptions, then identify what must be measured or specified for a binary boundary.

The answer is correct only after it says which compiler, target ABI, packing directives, and language guarantees it relies on.

Establish the evidence boundary before answering

Official or primary-source facts. Microsoft’s x64 ABI documentation states that structure size must be an integral multiple of alignment and may require trailing padding. Its packing guidance also shows that packing choices affect layout, which is why interop assumptions need a documented target. The linked sources at the end support those facts and should take priority if a framework or toolchain changes.

Candidate reports. This is a technical-topic guide, not a company-process guide. I found no reliable, same-cycle candidate-report set that adds a general rule for this topic, so this article makes no claim about a particular employer’s interview format, scoring, or implementation choice.

Reasoned practice guidance. The scenarios, diagnosis order, and acceptance gates below are engineering inferences. They are intentionally framed as things to test in a stated environment, not as universal behavior.

Build the mental model, not a slogan

Each member has an alignment requirement. The compiler places a member at an offset satisfying that requirement, inserting padding when necessary. The enclosing type itself has an alignment, and trailing padding can make the total size a multiple of that alignment so every element in an array begins suitably aligned. Reordering fields often changes size because it changes where gaps occur.

For a concrete exercise, write assumptions before arithmetic: target ABI, primitive sizes and alignments, #pragma pack state, alignas declarations, inheritance, virtual functions, and compiler flags. A simple standard-layout struct with char, int, and double is a good padding exercise; a polymorphic class or bit-fields is an invitation to separate language-level statements from ABI-specific detail.

Do not “fix” layout by blindly packing a performance-sensitive struct. Reduced alignment can produce unaligned access, different code generation, or ABI incompatibility. For a serialization or network boundary, define an explicit wire format and serialize fields deliberately. For a C ABI, freeze and test the target conventions.

An interviewer may change one assumption halfway through: distributed workers, a new data slice, a checkpoint resume, a different ABI, or a new attacker capability. Return to the boundary and state which observation would change your answer. That is stronger than defending a memorized rule.

Work a bounded interview exercise

Prompt. On a stated x64 target, estimate layout for struct Record { char flag; double price; int id; };, then explain why an array of records and a packed version deserve separate performance and portability discussion.

1. Start at offset zero. Under common x64 assumptions, flag occupies one byte, then padding is needed before an eight-aligned double; after price, the int is placed at its required alignment; trailing padding can bring the total size to a multiple of the struct alignment. Give the calculation as an ABI-specific estimate, then verify with sizeof, alignof, and offsetof in a test compiled by the deployment toolchain.

2. For an array, the stride is sizeof(Record), not the sum of member payloads. Trailing padding makes each next object’s double placement valid. This often explains cache-footprint questions better than debating a single object’s wasted bytes. Profile the actual traversal pattern before reorganizing storage; a structure-of-arrays transformation has different access and API trade-offs from merely swapping member order.

3. For a packed type, say what contract requires it. If a protocol requires a compact byte sequence, manually serialize and validate endianness and field widths or use a proven wire representation. If an external ABI requires a packing setting, isolate it at that boundary and add compile-time static_asserts plus cross-language tests. Do not let packed business objects escape into general in-memory code without evaluating alignment behavior.

The final answer should name a stop condition. For example: roll back a release if a protected slice crosses its error budget; reject a schema change if compatibility tests fail; stop a performance tune if the profile shows the presumed allocation is not material. A decision with a measured exit condition is more useful than an unbounded exploration.

Debug from evidence in this order

• Scope: record compiler, version, target, ABI, language mode, and packing pragmas.
• Evidence: assert sizeof, alignof, and selected offsetof values in the target build.
• Boundary: distinguish in-memory layout from an explicit serialized or FFI contract.
• Performance: measure cache, access, and unaligned-load effects on representative hardware.

This sequence is deliberately conservative. It separates a fact established by a specification or runtime document from a local observation, then asks for the smallest intervention that can disprove the current theory. It also produces artifacts a reviewer can reproduce: an input slice, command line or configuration, before/after measurement, and rollback point.

Turn the explanation into an engineering decision

For C++ Object Layout Interview Questions: Alignment, Padding, and Portable Assumptions, practice a one-page decision record rather than a stream of concepts. Begin with the user-visible or system-level failure: a bad slice metric, incompatible reader, allocation spike, unsafe data path, or portability assumption. State what must remain true after the change. This is the invariant. Examples include preserving a monetary value’s unit, keeping a request within a latency budget, preventing untrusted data from reaching a sensitive operation, or retaining the behavior promised by an API. An invariant makes it possible to reject an attractive implementation that optimizes the wrong thing.

Next, make the scope testable. Name the build or runtime version, data slice, traffic window, hardware, model checkpoint, compiler target, or security boundary that applies. A concise qualifier is more credible than a universal statement. “Under this ONNX Runtime build on the target CPU,” “for the old writer and new reader compatibility matrix,” or “when this request is reachable without an authorization guard” gives the interviewer a condition they can challenge. If the condition is unknown, say which document, log, experiment, or source inspection would resolve it.

Then compare two or three options against the invariant. For each option, write its mechanism, benefit, failure mode, and proof. A mechanism is not a benefit: a lower quantization range may improve resolution near zero but may saturate a rare activation; a broader CodeQL query may find more paths but can consume triage capacity; a new layout may reduce bytes but create an ABI or alignment cost. The proof should be concrete: a compatibility matrix, fixed-input test, profile, slice evaluation, path trace, or compiler output. It should include the baseline so an apparent improvement has meaning.

Make rollback part of the design. Identify which input, model, schema, configuration, or binary remains available; which metric triggers a stop; and who can act. A rollback plan does not imply the change is unsafe. It demonstrates that the team can learn from a bounded experiment without turning a local defect into unrecoverable history. For a non-reversible boundary, such as schema deletion or a public API contract, replace rollback with a staged migration and an explicit deprecation window.

Finally, communicate uncertainty precisely. Say “the documentation establishes X,” “the trace or benchmark establishes Y in this build,” and “I infer Z, so I would validate it with W.” That separation is especially important for Software Engineer work, where a mechanism may be correct while the proposed operational response is still wrong for the product’s constraints. It also keeps an interview answer honest when the interviewer has intentionally withheld a critical fact.

A five-minute whiteboard drill

Use this repeatable drill before an interview. Spend the first minute drawing the data, object, update, or control-flow boundary relevant to the prompt. Spend the second minute labeling the state that crosses the boundary and the state that must remain local, immutable, compatible, bounded, or trusted. Spend the third minute naming the symptom and listing two competing hypotheses. Spend the fourth minute choosing the cheapest discriminating observation. Spend the final minute proposing a small fix, an acceptance metric, and a rollback or migration path.

This format avoids a common failure mode: changing a configuration while several causes remain plausible. It also prevents a different failure mode: producing a technically elegant design with no evidence it works in the environment. If a panel asks for code, implement a narrow probe that exposes one invariant. If it asks for system design, write the observability and ownership fields next to the component diagram. If it asks for debugging, lead with the evidence you would gather before naming the fix.

Score your own response on five questions. Did it name the boundary? Did it distinguish a documented fact from a local observation? Did it identify an assumption that could reverse the recommendation? Did it specify a measurement that falsifies the current theory? Did it include a safe next action? A “yes” to all five usually signals stronger engineering judgment than adding another unsupported optimization detail.

When the prompt gives incomplete information, say so without stopping. Choose a provisional assumption that minimizes risk, explain why it is provisional, and state the first observation you would request. For example, a performance question may need a profile and workload distribution; a model question may need a protected evaluation slice; a security question may need the actual sink API and route reachability. This is not hedging. It is a way to turn uncertainty into an ordered investigation. A candidate who can do that will usually make better trade-offs after the interview too.

How to answer follow-up questions well

1. State assumptions before calculating offsets.
2. Explain both internal and trailing padding.
3. Connect trailing padding to array element alignment.
4. Separate an ABI observation from portable source-level claims.
5. Offer sizeof, alignof, and offsetof as the verification path.

Avoid two common interview failures. First, do not make a tool guarantee that its documentation does not make; qualify compiler, hardware, library, and deployment assumptions. Second, do not answer with a bag of keywords. A compact causal chain—input or state, mechanism, observable symptom, verification, reversible fix—lets the interviewer assess your judgment.

Sources and Further Reading

• Microsoft x64 ABI conventions
• Microsoft C/C++ packing issues
• C++ object model reference