Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
49 results for “Influence Without Authority”
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Autoscaling
Adding and removing capacity automatically in response to a demand signal, to track load without paying for peak all the time.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Covering Index
An index that contains every column a query needs, so the query is answered from the index without reading the table at all.
Crypto-Shredding
Encrypting each subject's data with its own key and destroying that key to render the data permanently unreadable, achieving deletion without deleting.
Database Index
A secondary structure that lets the engine find rows without scanning, trading write cost and storage for read speed.
Figma's Postgres Sharding
Figma delayed sharding for years using replicas and vertical partitioning, then sharded Postgres horizontally without downtime using logical shards and a proxy layer.
Hardware Security Module
A tamper-resistant device that generates and stores keys and performs cryptographic operations without the key material ever being extractable.
JSON Web Token
A signed, self-contained token carrying claims, which a service can validate locally without calling the issuer.
JWKS
A published endpoint listing an issuer's current public keys, allowing resource servers to validate token signatures without a shared secret and to survive key rotation.
NAT Gateway
A managed device that lets instances in a private subnet make outbound connections without being reachable inbound.
Negotiation
Reaching an agreement that both sides own, by trading on interests rather than arguing positions.
OAuth 2.0
An authorisation framework that lets an application obtain scoped, delegated access to a resource without handling the user's credentials.
Observability
The property of being able to answer new questions about a system's internal state from its external outputs, without shipping new code.
Optimistic Concurrency Control
Allowing concurrent work without locks and detecting conflict at write time by checking that the underlying version has not changed.
Presenting to Executives
Leading with the decision and the business consequence, at a level of abstraction where technology names do not appear.
Purpose Limitation
The principle that personal data collected for one stated purpose may not be used for an unrelated one without a new lawful basis.
Redundancy
Having more instances of a component than the load requires, so that failures can be absorbed without loss of service.
Refactoring
Changing the internal structure of code without changing its external behaviour, in small verified steps.
Refresh Token
A long-lived credential used solely to obtain new short-lived access tokens, so sessions can persist without long-lived access tokens circulating.
Semantic Cache
Caching model responses keyed by the meaning of the request rather than by its exact text, so near-duplicate questions are served without a model call.
Sidecar
Deploying a helper process alongside the main application in the same unit, to supply cross-cutting behaviour without changing the application.
Snapshotting
Periodically storing an aggregate's computed state so it can be loaded without replaying its entire event history.
Stakeholder Analysis
Identifying who is affected by an architecture, what each of them needs from it, and how much influence they have over whether it proceeds.
Tagging Strategy
A defined, enforced set of metadata labels applied to every resource, without which cost allocation, ownership and lifecycle automation are all impossible.
Terraform State
The file mapping declared resources to real infrastructure, without which the tool cannot tell what it already created — and which becomes critical infrastructure in its own right.
WebSocket
A protocol that upgrades an HTTP connection into a persistent, full-duplex channel so the server can push to the client without polling.
Workload Identity
Giving a running workload a cryptographically verifiable identity issued by the platform, so it obtains short-lived credentials without a stored secret.
A team shows you a design with eight services. Without knowing the domain, what questions tell you whether the boundaries are right?
What the interviewer is testing Whether you can evaluate a structure from its properties rather than needing to be a domain expert in every system you review. T
You are designing a new service. What must be in place before it goes live so that whoever is paged at 3 AM can diagnose it without you?
What the interviewer is testing Whether observability is designed in or bolted on, and whether you think about the person on call rather than about the tooling.
You move a user profile service to eventual consistency and support tickets start arriving: users update their name and the old one is still shown. Fix it without abandoning the architecture.
What the interviewer is testing Whether you know that consistency is per operation rather than per system, and whether you reach for a targeted guarantee instea
Your observability bill is now 40% of your compute bill. Leadership wants it cut in half without going blind. What do you cut?
What the interviewer is testing Whether you understand what each telemetry type is for , so you can cut the redundant parts rather than cutting uniformly — whic
In a design review, a respected senior engineer proposes an approach you believe is wrong. The room defers to them. How do you handle it?
What the interviewer is testing Whether you can be effective without authority, which is most of the architect's job. It is also testing whether you assume you
You have designed a system. Explain the same architecture to a CEO, an engineering manager and an engineer. What changes?
What the interviewer is testing Whether you can adapt to an audience, which is the skill that most often separates a senior engineer from an architect. It is al
Influence Without Authority
Getting decisions adopted when you cannot mandate them.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Coexistence Patterns
Running old and new together for years without corrupting either.
Continuous Learning
Staying current without chasing every new thing.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
Database Migration
Moving engines, versions and schemas without losing data or uptime.
Legacy Integration
Reaching systems that cannot change, without importing their model.
Modular Monolith
Enforced internal boundaries without a network between them.
Refactoring
Changing structure without changing behaviour, in verified steps.
Replatforming
Targeted changes that capture operational wins without a rewrite.
Research & Evaluation
Assessing a technology quickly without adopting it by accident.
Technical Leadership
Setting direction and carrying accountability without a team reporting to you.
Telemetry Cost
Observability bills that rival compute, and where to cut without going blind.
Written Communication
Writing that survives being read without you in the room.