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 audit deadline requires isolation while the traffic increase requires proven capacity.
The isolated environment protects the customer’s control boundary, while the existing environment protects continuity for live conversations.
Who you’d be doing this for
“I can’t tell my team to absorb a spike because the new environment might run short.”
Yuji Lim · Customer Support Operations Director · a character in this brief
Owns service coverage and escalations for the enterprise customer moving its billing and account-service agents.
What is at stake
A regulated customer must move live agents before a traffic increase. You must choose a cutover path that protects isolation without gambling on unproven capacity.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- audit closure vs service continuity
- isolated controls vs proven capacity
- standard deployment patterns vs customer-specific urgency
- traffic growth vs irreversible change windows
Why Sierra
Customer-facing agents must remain operable across isolated environments without turning compliance requirements into service interruptions.
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)
- Own deployment architecture conversations and execution — designing and implementing deployment strategies across customer environments, including VPC configuration, permissioning, networking, and infrastructure provisioning.
- Collaborate with Sales and Customer Success to scope infrastructure requirements during pre-sales and onboarding, translating customer needs into concrete deployment plans.
- 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.
- Build security guardrails that give enterprise customers confidence in our shared multi-tenant environment.
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.
Home-service businesses on the integrated phone system will outgrow its routing provider at the next renewal, forcing a regional migration.
You have to design the release and verification that let the company commit without full proof of call behavior.
Launch-rehearsal users saw failed LLM responses, and the customer wants production traffic moved this week.
You must weigh a fast dedicated cutover against the evidence and capacity commitments needed to make it safe.
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 build high-assurance systems where a consequential change's correctness can be demonstrated, not merely hoped for.
Rehearsals show the routing works, but recall of sources varies by 0.9% and provenance records are incomplete.
You have to weigh the contractual launch against how much you verify before each matter moves.
The old encrypted store retires on a fixed date, and 6.9% of historical artifacts still lack a source record and retention decision.
You have to weigh speed against proof that reports stay reproducible.
The residency commitment you signed forces a one-way split of event data, and 9% of derived datasets still lean on labels a machine guessed.
With six weeks left, you weigh completeness by region against keeping analytics intact.