# Technical Platform Architect — Ashley Furniture

- Location: Tampa, FL
- Posted: Nov 6, 2026
- Status: open (checked Nov 21, 2026)
- Apply (employer's site): https://recruiting2.ultipro.com/ash1002af/JobBoard/20c06009-60fe-480c-8ce5-da3e9df145b9/OpportunityDetail?opportunityId=2451f74a-7bac-4d0d-840b-40f73413f73d
- Employer record: https://visajobs.io/company/ashley-furniture-industries.md

## Sponsorship history
- Tier: Good history
- Occupation (SOC): Software Developers (15-1252)
- Employer's certified LCAs for this occupation in FL, FY2024–FY2026: 6
- …in the whole US: 20
- With this exact title: 0
- Median DOL prevailing wage, level I / II: $73k / $95k

## Description
Technical Platform Architect
Location: Tampa, FL (Ybor City) on-site
Department: Developer Experience
Type: Full-time, individual contributor
About Ashley
Ashley Furniture Industries Inc. is the largest manufacturer of furniture in the world. Established in 1945, Ashley offers one of the industry's broadest product assortments to retail partners in 123 countries. We're a privately held, family-owned business that offers great stability, a record of unparalleled success, and a company culture steeped in continuous improvement. Due to our ambitious growth plans, we're always on the lookout for dynamic professionals to join our team.
Our team works in a state-of-the-art office facility in the heart of historic Ybor City, surrounded by unique culture, architecture, and dining, just minutes from the Crosstown, I-4, and I-275.
About the role
We are building an internal platform that serves every engineering team at Ashley thousands of repositories, dozens of Kubernetes clusters, and delivery teams spread across multiple business domains. We are looking for a Technical Platform Architect to set the technical direction for that platform.
This is a hands-on architecture role. You will write code, review pull requests and prototype the patterns you propose. We are not looking for someone to produce diagrams and hand them off we are looking for someone whose designs are credible because they have built them.
It is also a role without direct authority. You will not manage the teams who adopt your work. Your influence will come from making the recommended path measurably easier than the alternatives, from evidence, and from your ability to earn the trust of engineers who are free to ignore you. If you have moved a large organization by building something people chose to adopt, we want to talk to you.
We care as much about how you hold what you know as about what you know. You will arrive with a deep library of patterns, and we want you to bring all of it as a set of hypotheses about Ashley, not conclusions. What worked at your last company is real evidence and we will take it seriously, but our constraints, our teams, and our history are different, and the pattern must be tested here before it becomes an answer. The architects who struggle in this role are the ones who spend their first year rebuilding their previous platform.
The same applies to technology selection. We expect you to have strong preferences and to argue for them hard. We expect the argument to rest on our constraints and on observable outcomes rather than on familiarity, enthusiasm, or what is currently well-regarded. Being able to say "I was wrong, and here is what changed my mind" is a qualification for this role, not a liability.
What you'll do
Set technical direction
Own the architecture of Ashley's internal developer platform the golden paths, reference implementations, and self-service capabilities that delivery teams build on
Define and evolve enterprise standards for source control, CI/CD, infrastructure as code, containerization, observability, and deployment
Evaluate emerging technologies against real constraints and make clear recommendations, including recommendations not to adopt
Establish the architectural guardrails that let teams move quickly without producing systems the organization cannot operate
Build
Design and implement reusable platform components that eliminate repeated effort across teams
Prototype and prove out new patterns before recommending them broadly
Contribute directly to platform codebases, automation, and tooling
Make observability a property of the platform rather than a burden each team re-solves standardized OpenTelemetry instrumentation, consistent semantic conventions across services, and collector topologies that keep the telemetry backend a replaceable decision
Ensure new and existing systems are resilient and operable by the teams that own them
Enable adoption
Partner with delivery teams to understand their friction and design capabilities that remove it
Publish patterns, standards, and reference material that teams can act on without a meeting
Mentor engineers across the organization and raise the level of platform fluency company-wide
Drive migration and modernization efforts through evidence and enablement rather than mandate
Treat the platform as a product
Understand who your users are, what they are trying to accomplish, and where you are failing them
Measure adoption and developer experience, and use what you learn to prioritize
Make deliberate tradeoffs between capability, cognitive load, and the burden of operating what you ship
What we're looking for
A bachelor's degree in computer science, computer engineering, or a related field, or an equivalent combination of education and experience
8+ years of software engineering experience, including 4+ years designing and operating platform or infrastructure systems at enterprise scale
Demonstrated ability to drive technical change across organizational boundaries without formal authority you can point to something an organization adopted because you made it the obvious choice
A habit of holding your own experience loosely &acirc;&euro;” you can describe a pattern you brought into a new organization, tested against its actual constraints, and set aside because it didn't fit
Evidence-based technology selection you can walk us through a decision where you chose against your own preference, and describe specifically what moved you
Deep, practical experience with Kubernetes and container-based delivery, including what breaks at scale and why
Fluency in infrastructure as code and declarative, continuously reconciled infrastructure &acirc;&euro;” you should be able to explain why reconciliation loops behave differently from run-to-completion provisioning, and when that difference matters
Strong experience designing and operating CI/CD systems, and a clear point of view on branching, artifact promotion, and release strategy
Practical experience w

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
