Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
47 results for “Build Reproducibility”
Hermetic Build
A build whose output is a function only of its declared inputs, so the same commit cannot produce two different artifacts.
Build Attestation
A signed statement about how an artifact was produced — by which builder from which source — that a deployment gate can verify rather than trust.
Build Graph Scoping
Determining which packages a change actually affects, so a monorepo builds and tests a subset rather than everything on every commit.
Build vs Buy
The choice between developing a capability in-house and acquiring it, decided on differentiation and total cost rather than on feature lists.
Artifact Promotion
Moving one immutable build between repositories as it earns trust, rather than rebuilding it for each environment.
Artifact Signing
Cryptographically signing build outputs so that deployment can verify what is being run was produced by the expected pipeline from the expected source.
Automated Governance
Encoding architectural rules as executable checks in the build pipeline, so conformance is verified continuously rather than reviewed periodically.
Consumer-Driven Contract
A contract derived from what consumers actually use, published to the provider, and verified in the provider's own build.
Contract Verification Gate
A provider's pipeline stage that replays every consumer's recorded expectations and fails the build if any would break.
Differentiation Test
The question of whether a capability is a source of competitive advantage, used as the primary filter in build-versus-buy decisions.
Dropbox's Move Off S3
Dropbox moved the majority of its file storage off Amazon S3 onto custom infrastructure, reporting savings that its S-1 filing put at roughly $75 million over two years.
FinOps
The practice of giving engineering teams visibility into and accountability for the cost of what they build and run.
Infrastructure as Code
Defining infrastructure in version-controlled declarative files that a tool reconciles against the real environment.
Paved Road
A supported, opinionated default way to build and run a service, made easy enough that teams choose it rather than being required to.
Performance Budget
A stated numeric limit on a performance characteristic, enforced automatically so that regressions fail a build rather than accumulating.
Performance Budget Enforcement
A stated limit on bundle size or a timing metric that fails a build when exceeded, which is what turns performance from a periodic project into a constraint.
Product Thinking
Treating what you build as something with users, a value proposition and a lifecycle, rather than as a project that completes.
Remote Module Loading
Importing code from another application's build at runtime, with the versioning, availability and failure questions that a normal import does not have.
Render Location Decision
Where HTML is produced — build time, server, edge or browser — chosen per route by how personalised and how cacheable that route is.
Semantic Diffing of API Schemas
Comparing the published contract between builds and failing the build on a breaking change, so compatibility is mechanical rather than remembered.
Strategic Sourcing Decision
A build-versus-buy decision framed around competitive differentiation and organisational capacity rather than a comparison of visible costs.
Test Quarantine
Moving an intermittently failing test out of the blocking suite into a tracked, owned backlog, so a red build keeps meaning something.
Total Cost of Ownership
The full lifetime cost of a capability, including the people, operations, upgrades and exit that a licence comparison leaves out.
A startup asks you to architect their product "to handle millions of users". They currently have none. What do you actually build?
What the interviewer is testing Whether you can identify the real constraint. The stated requirement is scale; the actual constraint is survival, and an archite
A team wants to build a new internal API on serverless functions. It will serve steady traffic of about 200 requests per second during business hours. What do you advise?
What the interviewer is testing Whether you can apply the serverless trade off to a specific workload rather than treating it as a default good or a default bad
A vendor SaaS product embeds a model that scores customers, and its output drives an automated decision in your process. Your model governance framework covers models you build. What do you do?
The obligation does not transfer with the outsourcing You are accountable for the decision. That the scoring is performed by a vendor changes who operates the m
Choose storage for four workloads: a Postgres data directory, user-uploaded images, a shared build cache, and seven years of audit records.
Postgres data directory — block storage It needs low latency random reads and writes and a filesystem, and it attaches to one instance. That is precisely block
Leadership asks whether to build an internal developer platform or buy one. Twelve teams, forty services, growing. How do you frame the decision?
Reject the framing as a binary Nobody builds or buys a whole platform. A platform is an assembly: source control, CI, artifact registry, infrastructure provisio
Two services share a database because it was faster to build that way. Both teams now block each other on every schema change. What do you do?
Name the actual coupling They are not two services. They are one deployable unit split across two repositories, with the coupling moved from code — where a comp
You are asked to produce a technology radar for a 200-engineer organisation with no current standards. How do you build the first one?
Start from what is actually in use, not from what should be Inventory the estate: languages, frameworks, datastores, queues, CI tooling, observability. Sources
You are forming a platform team of four to serve twelve product teams. What do you build first?
Not a platform. One golden path. Four people cannot build an internal developer platform for twelve teams. They can make one journey excellent, and expand from
You need funding for eighteen months of platform work with no customer-visible features. How do you build the case?
Do not lead with the technology "We need to modernise the platform" is a request for trust. Lead with a number the business already recognises as a problem. Fin
Your company needs a feature flag and experimentation platform. A vendor charges a substantial annual fee; a team estimates six weeks to build one. Decide.
Apply the differentiation test first Is this a source of competitive advantage? Feature flagging is context, not core: customers do not choose you for it, and b
Your platform has 60 internal APIs. Teams repeatedly rebuild capabilities that already exist because they cannot find or understand them. What do you build?
The problem is discovery, then comprehension Duplication is the symptom. Teams are not choosing to rebuild; they cannot find what exists, or cannot tell in reas
Netflix built its own CDN; Dropbox moved storage off S3. Both are usually wrong. What conditions made them right, and how do you test for those conditions?
What the interviewer is testing Whether you can extract the conditions from a famous decision rather than the decision itself. These two cases are the most comm
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Build vs Buy
Differentiation, five-year TCO, and the exit cost of each option.
Backward Compatibility
Which changes are safe, and how to make breakage a build failure.
Module Federation
Loading code from another build at runtime, with versioning and failure to think about.
Performance Budgets
Targets enforced in CI so regressions fail the build.
Supply Chain Security
Dependencies, SBOMs, build provenance and artefact signing.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.
Web Performance Budgets
A number a build can fail against, rather than a performance sprint once a year.