The setting
sells software to mid-market and large businesses. Its hold customer conversations and take actions in the business's connected systems, across digital and voice channels.
The bank needs new regional capacity without moving customer conversations beyond its approved boundary.
Customer-service continuity depends on a rapid cutover, while security approval depends on evidence that the new environment contains every data path.
Who you’d be doing this for
“My call center is already getting asked why the agent pauses, and I have no safe fallback for peak hours.”
Tove Solberg · Customer Support Operations Director · a character in this brief
Owns service continuity for the bank’s customer support operation that depends on the agent for account and payment contacts.
What is at stake
Bank callers face longer pauses while the current AWS capacity expires in nine days. You must choose where the cutover evidence is strong enough to move customer traffic.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- capacity deadline vs. security evidence
- service continuity vs. data isolation
- synthetic confidence vs. production behavior
- standardized regions vs. dedicated environments
Why Sierra
Isolated customer environments are central to serving regulated enterprises that need customer-facing agents to operate inside their own security constraints.
Written with these in mind
Not your kind of problem? 37 more at Sierra, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Sierra. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Deployed Infrastructure Engineer (opens in a new tab)
- Work with customers' platform engineering, security, and DevOps teams to navigate their infrastructure constraints and compliance requirements.
- Own deployment architecture conversations and execution — designing and implementing deployment strategies across customer environments, including VPC configuration, permissioning, networking, and infrastructure provisioning.
- Software Engineer, Infrastructure (opens in a new tab)
- Ensure the reliability, scalability, and performance of our platform and LLM inference serving as we rapidly grow traffic.
- Build and maintain cloud infrastructure using Terraform to ensure scalable, secure, and reproducible environments.
- IT Infrastructure Engineer (opens in a new tab)
- Software Engineer, Cloud Infrastructure (opens in a new tab)
- Stand up and operate new multi-tenant regions and single-tenant environments for customers with strict regulatory or isolation needs.
- Design, build, and operate Sierra’s cloud infrastructure across AWS and GCP (and soon Azure) using Terraform and Kubernetes.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
Mission video slows when simultaneous incidents draw traffic through the existing regional path.
You must weigh a hard-to-reverse cutover against the evidence needed to protect restricted operational data.
The contract for hosting ends in 10 weeks, and no test recreates real device connectivity at peak trading.
You have to weigh continuity against schedule certainty, then evidence a cutover you cannot undo.
A 12,000-run validation campaign is about to lose its AWS GPU capacity, and paired reruns are not fully matching.
You have to weigh a protected review window against a cutover that could alter trusted evidence.
The same setting, from another role
Each is set around Sierra’s Customer-facing AI agents, written for a different role. They’re separate briefs, not the same scenario.
Enterprise support leaders are waiting on launch answers while account evidence sits across several records.
You must decide whether the AI drafts only from approved guidance or also surfaces tentative working-session details for review.
Billing callers need payment help before service interruptions turn into repeat contacts.
You must weigh earlier self-service against a consent record that holds up when a consumer disputes the arrangement.
A healthcare customer paused its expansion over whether patient conversations can be used to improve the agent.
You must weigh a deal-closing privacy commitment against the investigation record needed after a harmful response.
Other problems with a similar purpose
In each of these, as in this one, the aim is to use evidence to make delivery leaner and more efficient without treating reliability as something to trade away.
Mine operations managers are waiting on fixes while reviews reopen for missing vehicle evidence.
You must decide whether AI marks uncertain evidence or holds the change for an engineer to investigate.
Worker-type concerns are appearing repeatedly across payroll API migration feedback, but their source evidence is scattered.
You must decide where the drafting of clusters from Operations and Compliance feedback stops and where a product manager's own reading of the source examples has to begin.
Daily event-air exceptions are producing conflicting explanations for the same cost and service variance.
You must decide what AI can match and draft, and what reviewers must verify before finance acts.
