The Technical Co-Founder: An O-1A Approved With No RFE
The Technical Co-Founder: An O-1A Approved With No RFE
An O-1A approval for a co-founder and chief technology officer whose case was built on engineering depth rather than a chief executive title. He spent years building infrastructure that other engineers rely on at some of the most demanding companies in technology, then became the technical half of a venture-backed startup. Approved on the first attempt, under premium processing, with no request for evidence.
An O-1A approval for a co-founder and chief technology officer whose case was built on engineering depth rather than a chief executive title. He spent years building infrastructure that other engineers rely on at some of the most demanding companies in technology, then became the technical half of a venture-backed startup. Approved on the first attempt, under premium processing, with no request for evidence.
September 08, 2026
September 08, 2026
Petition Type | Processing | RFE | Status | Field |
O-1A Extraordinary Ability | Premium | None | Approved | Technology |
Case Background
Case Background
Most founder petitions are led by the chief executive. This one was led by the person who built the product. His case rests on a decade of engineering that other engineers, and entire companies, depend on. Here is who he is:
A Vietnamese national and the co-founder and chief technology officer of a venture-backed consumer marketplace startup, working in technology
A former engineer at a leading global investment firm, where he owned compute-capacity systems across the team's infrastructure
A former engineer on a major programming language team at one of the world's largest technology companies, where he became a lead contributor to official developer tooling and release infrastructure used across that company's stack
A former engineer in the infrastructure research organization of another top technology company, where he built production data pipelines feeding a core storage engine
The technical co-founder who architected the startup's entire product surface and wrote most of its production code before the first engineering hire, work that anchored its seed round and early revenue across several US markets
An editorial board member and peer reviewer for two international journals, a hackathon judge, a published author, and the subject of independent media coverage
Field: Technology
Most founder petitions are led by the chief executive. This one was led by the person who built the product. His case rests on a decade of engineering that other engineers, and entire companies, depend on. Here is who he is:
A Vietnamese national and the co-founder and chief technology officer of a venture-backed consumer marketplace startup, working in technology
A former engineer at a leading global investment firm, where he owned compute-capacity systems across the team's infrastructure
A former engineer on a major programming language team at one of the world's largest technology companies, where he became a lead contributor to official developer tooling and release infrastructure used across that company's stack
A former engineer in the infrastructure research organization of another top technology company, where he built production data pipelines feeding a core storage engine
The technical co-founder who architected the startup's entire product surface and wrote most of its production code before the first engineering hire, work that anchored its seed round and early revenue across several US markets
An editorial board member and peer reviewer for two international journals, a hackathon judge, a published author, and the subject of independent media coverage
Field: Technology
Why an Engineering Case Is Different
Why an Engineering Case Is Different
Most O-1A petitions in technology are led by the chief executive, because business milestones are easy to narrate: funding raised, users acquired, revenue booked. An engineer's most important work is harder to see. It lives inside systems, and its significance is obvious to other engineers but invisible to anyone else.
That is the central task in a case like this. The achievements are real and, in engineering terms, unusually strong. But an adjudicator is not an engineer. The work of the petition is to translate technical depth, owning core tooling that thousands of other developers use, building infrastructure that a company's systems depend on, into evidence a non-specialist can weigh with confidence. When that translation is done well, engineering depth is one of the most durable foundations an O-1A can have, because it does not depend on a title or a funding announcement.
Most O-1A petitions in technology are led by the chief executive, because business milestones are easy to narrate: funding raised, users acquired, revenue booked. An engineer's most important work is harder to see. It lives inside systems, and its significance is obvious to other engineers but invisible to anyone else.
That is the central task in a case like this. The achievements are real and, in engineering terms, unusually strong. But an adjudicator is not an engineer. The work of the petition is to translate technical depth, owning core tooling that thousands of other developers use, building infrastructure that a company's systems depend on, into evidence a non-specialist can weigh with confidence. When that translation is done well, engineering depth is one of the most durable foundations an O-1A can have, because it does not depend on a title or a funding announcement.
The Challenge
The Challenge
1. His title is technical, not executive
He is the chief technology officer, not the chief executive. There is no fundraising-and-vision narrative of the usual kind. The case had to rest on the substance of what he engineered, which meant making that substance legible to someone outside the field.
2. He filed through his own company
When the petitioning company is the founder's own startup, USCIS scrutinizes the arrangement. We had to show a real, funded, revenue-generating company with a clean separation between the individual and the entity.
3. The company is young
The startup is early-stage and cannot carry an established reputation on its own. So the case leaned on his personal engineering record at prior employers of unquestionable standing, and on independent recognition of his work.
1. His title is technical, not executive
He is the chief technology officer, not the chief executive. There is no fundraising-and-vision narrative of the usual kind. The case had to rest on the substance of what he engineered, which meant making that substance legible to someone outside the field.
2. He filed through his own company
When the petitioning company is the founder's own startup, USCIS scrutinizes the arrangement. We had to show a real, funded, revenue-generating company with a clean separation between the individual and the entity.
3. The company is young
The startup is early-stage and cannot carry an established reputation on its own. So the case leaned on his personal engineering record at prior employers of unquestionable standing, and on independent recognition of his work.
Our Strategic Approach
Our Strategic Approach
We built the case on six criteria, and his engineering depth ran through every one of them.
1. Critical role
This was the backbone. He served in critical technical roles at a leading investment firm, at two of the largest technology companies in the world, and as the technical co-founder of his own startup. At each, the systems he owned were relied upon by other engineers and by the business itself. Senior colleagues confirmed his contributions in writing.
2. Original contribution
He architected the full technical product of his company and authored most of its production code before any other engineer was hired, building a new kind of marketplace in its sector. Independent experts confirmed in writing that the work is original and significant.
3. Judging
He serves on the editorial boards of two international peer-reviewed journals, where he has reviewed dozens of manuscripts, and he judged two technology competitions, evaluating the work of other engineers and builders.
4. Authorship
He authored several published technical articles on subjects including performance monitoring, fault-tolerant infrastructure, and data pipelines, contributing to the professional literature in his field.
5. Membership
He holds merit-based membership in two selective professional networks, including a private community of senior technology leaders drawn from the most prominent companies in the industry.
6. Published material
His work has been the subject of coverage across general and trade publications, focused on him and his contributions.
Alongside these six, we submitted advisory opinion letters from independent leaders in technology and in his company's industry.
We built the case on six criteria, and his engineering depth ran through every one of them.
1. Critical role
This was the backbone. He served in critical technical roles at a leading investment firm, at two of the largest technology companies in the world, and as the technical co-founder of his own startup. At each, the systems he owned were relied upon by other engineers and by the business itself. Senior colleagues confirmed his contributions in writing.
2. Original contribution
He architected the full technical product of his company and authored most of its production code before any other engineer was hired, building a new kind of marketplace in its sector. Independent experts confirmed in writing that the work is original and significant.
3. Judging
He serves on the editorial boards of two international peer-reviewed journals, where he has reviewed dozens of manuscripts, and he judged two technology competitions, evaluating the work of other engineers and builders.
4. Authorship
He authored several published technical articles on subjects including performance monitoring, fault-tolerant infrastructure, and data pipelines, contributing to the professional literature in his field.
5. Membership
He holds merit-based membership in two selective professional networks, including a private community of senior technology leaders drawn from the most prominent companies in the industry.
6. Published material
His work has been the subject of coverage across general and trade publications, focused on him and his contributions.
Alongside these six, we submitted advisory opinion letters from independent leaders in technology and in his company's industry.
The Outcome
The Outcome
APPROVED | NO RFE | PREMIUM | SIX CRITERIA |
O-1A Extraordinary Ability | First attempt | Premium Processing | Built on engineering depth |
APPROVED | NO RFE | PREMIUM | SIX CRITERIA |
O-1A Extraordinary Ability | First attempt | Premium Processing | Built on engineering depth |
Approved on the first attempt, under premium processing, with no request for evidence.
Approved on the first attempt, under premium processing, with no request for evidence.
The approval recognizes him as a person of extraordinary ability and lets him keep building in the United States. For an engineer who spent years making the systems other people build on, and then built a company of his own, the case shows that technical depth, properly presented, stands on its own.
The approval recognizes him as a person of extraordinary ability and lets him keep building in the United States. For an engineer who spent years making the systems other people build on, and then built a company of his own, the case shows that technical depth, properly presented, stands on its own.
Key Success Factors
Key Success Factors
1. We made engineering legible
The heart of the case was translating deep technical work into evidence a non-engineer could assess. Owning core developer tooling and critical infrastructure is extraordinary, but only if the significance is explained clearly. We made that our priority.
2. We did not need an executive title
Extraordinary ability is about the work, not the org chart. Being the engineer the whole product depends on can be as strong as any chief executive narrative, provided the record is documented and confirmed by others.
3. We leaned on the pedigree, not the startup
Because the company is young, we built the case on his personal engineering record at employers of unquestionable standing, and on independent recognition of his work, rather than on the startup's reputation.
4. We filed above the minimum
Documenting six criteria instead of three left no single point of failure and gave the petition a wide margin.
1. We made engineering legible
The heart of the case was translating deep technical work into evidence a non-engineer could assess. Owning core developer tooling and critical infrastructure is extraordinary, but only if the significance is explained clearly. We made that our priority.
2. We did not need an executive title
Extraordinary ability is about the work, not the org chart. Being the engineer the whole product depends on can be as strong as any chief executive narrative, provided the record is documented and confirmed by others.
3. We leaned on the pedigree, not the startup
Because the company is young, we built the case on his personal engineering record at employers of unquestionable standing, and on independent recognition of his work, rather than on the startup's reputation.
4. We filed above the minimum
Documenting six criteria instead of three left no single point of failure and gave the petition a wide margin.
Why Engineers Trust OpenSphere
Why Engineers Trust OpenSphere
OpenSphere prepares O-1A and other extraordinary ability cases for engineers, founders, and technical leaders, including technical co-founders whose strongest evidence is the work itself.
Experience translating deep technical work into evidence an adjudicator can evaluate, from core tooling to production infrastructure
A proven approach to founder-led and technical filings, from petitioner documentation to the choice of recommenders
Deep familiarity with software, infrastructure, and consumer platform engineering
Whether you lead the business, the engineering, or both, OpenSphere can help you build a case that stands on its own.
Get your free visa evaluation at opensphere.ai
Note: Client details have been anonymized to protect confidentiality while preserving the essential facts of the case.
OpenSphere prepares O-1A and other extraordinary ability cases for engineers, founders, and technical leaders, including technical co-founders whose strongest evidence is the work itself.
Experience translating deep technical work into evidence an adjudicator can evaluate, from core tooling to production infrastructure
A proven approach to founder-led and technical filings, from petitioner documentation to the choice of recommenders
Deep familiarity with software, infrastructure, and consumer platform engineering
Whether you lead the business, the engineering, or both, OpenSphere can help you build a case that stands on its own.
Get your free visa evaluation at opensphere.ai
Note: Client details have been anonymized to protect confidentiality while preserving the essential facts of the case.