Success Stories
March 2024: Korean product manager Shares O-1 Tips
Detailed analysis with practical recommendations for O-1 applicants at every stage.
The O-1A pathway for product managers
Product management presents an unusual O-1A challenge because the role sits at the intersection of business, technology, and design without mapping cleanly onto any of the eight enumerated O-1A evidentiary criteria. The petitioner in this case — a product manager at a major technology company in Seoul with several years of experience building consumer-facing products — had accumulated recognition that was genuinely exceptional for the role but had not previously organized that recognition against the O-1A regulatory framework. The petition process began with a criterion-mapping exercise to identify which of the enumerated criteria the available evidence most directly addressed, rather than starting from the evidence and working backward.
Product managers are classified under O-1A, not O-1B, because their work is primarily in the business and technology sectors rather than the arts or entertainment. The extraordinary ability standard applicable to O-1A petitions under 8 C.F.R. § 214.2(o)(3)(iii) requires evidence of extraordinary ability in the petitioner's field, and for a product manager, the relevant field is defined by the specific domain in which the petitioner works — consumer mobile applications, enterprise software, fintech products, or similar product domains. Defining the field precisely at the outset allowed the petition to make a comparative argument about the petitioner's standing relative to other accomplished product managers in the consumer mobile applications domain rather than making the more difficult comparison to product managers across all technology sectors.
The petition ultimately satisfied the threshold criterion requirement through four categories of evidence: published materials about the petitioner's work, high salary relative to others in the field, leading or critical role in distinguished organizations, and original contributions of major significance. The final merits determination was supported by expert letters from recognized figures in the product management and technology industries who articulated specifically how the petitioner's level of achievement compared to the ordinary level for accomplished product managers in consumer mobile applications. The petition's framing of the field at the product-domain level, rather than at the general technology level, was the strategic decision that made the comparative argument tractable.
Building the published materials criterion
The published materials criterion requires materials published in professional or major trade publications or other major media about the petitioner and the petitioner's work in the field. For product managers, the most relevant publications are industry outlets such as TechCrunch, Wired, Fast Company, The Verge, and specialized product management publications. The petitioner had been profiled in several Korean technology publications and had contributed bylined articles to English-language product management newsletters and communities, but the petition required press about the petitioner rather than by the petitioner, and bylined articles did not satisfy the criterion.
The petition assembled press coverage from three sources: a profile in a recognized Korean technology publication with documented circulation and editorial standing, coverage in an English-language technology publication of a product the petitioner had led that received significant industry attention at launch, and mentions in industry analyst reports discussing the product category in which the petitioner was a recognized practitioner. Each press item was accompanied by documentation of the publication's standing in the field, including circulation data, editorial mission statements, and industry recognition of the publication as an authoritative source. The collection collectively established that the petitioner had received recognition in publications that were meaningful to practitioners in the field.
The challenge in press evidence for product managers is that product launches typically generate coverage of the product and company rather than coverage of the individual product manager responsible for the product's design and direction. The petition addressed this challenge by including expert letters from industry professionals who explained the product manager's role in the recognized products — establishing that while the press coverage named the company or the product, the petitioner was the individual responsible for the product decisions that generated the recognition. This connection between the press coverage and the petitioner's specific contributions was essential to making the published materials evidence satisfy the criterion.
High remuneration and leading role evidence
The high remuneration criterion was satisfied through documentation of the petitioner's total compensation package — base salary, performance bonus, equity grants, and other compensation elements — combined with BLS OEWS data for software and IT product management roles in the relevant metropolitan area and supplementary industry salary survey data from technology-specific compensation surveys. The petitioner's total annual compensation substantially exceeded the 90th percentile for the relevant occupation and geographic area, establishing that the compensation level reflected the level of recognition associated with extraordinary ability in the product management field.
The leading or critical role criterion required documentation that the petitioner held a critical role at organizations of distinguished reputation. The petitioner's current employer — a major Korean technology company with a documented global user base in the hundreds of millions and recognized standing in international technology rankings — provided the distinguished organization basis. The petitioner's role as head of product for a flagship consumer product, with responsibility for product strategy, team direction, and cross-functional coordination, satisfied the critical role requirement. Documentation included the organizational chart establishing the petitioner's position within the product organization, the employment letter describing the scope of the role, and an expert letter from a senior technology executive explaining why a head of product role at an organization of this scale constitutes a critical role.
The petition also documented the petitioner's advisory roles at two startup companies in the consumer technology sector, where the petitioner served as a formal product advisor with documented engagement responsibilities. Advisory board documentation — the advisory agreements, the companies' official advisory board pages identifying the petitioner's role, and correspondence documenting the petitioner's engagement — established additional instances of the critical role criterion at organizations whose recognition in the startup ecosystem was documented through investor lists, press coverage, and industry database records. Multiple instances of the critical role criterion across distinguished organizations strengthened the overall criterion evidence and contributed to the final merits determination.
Original contributions of major significance
The original contributions criterion requires evidence of original scientific, scholarly, artistic, athletic, or business-related contributions of major significance in the field. For product managers, this criterion is most effectively satisfied by documenting product innovations, process methodologies, or strategic frameworks that the petitioner developed and that have been adopted, cited, or recognized by others in the field. The petitioner had developed a product measurement framework for consumer engagement optimization that had been discussed in product management communities, referenced in at least two published articles in the field, and adopted in modified form by practitioners at other companies.
Evidence for the original contributions criterion included documentation of the framework's development — internal product documents with dates establishing the petitioner's authorship, public presentations where the petitioner described the framework, and the published articles referencing the framework. Expert letters from practitioners who had adopted or built upon the framework explained why it represented a significant contribution to the field's collective body of practice and how it had influenced subsequent approaches to the problem the framework addressed. The combination of authorship documentation, publication references, and expert testimony of field impact collectively satisfied the original contributions criterion at the level of major significance.
The major significance element required the petition to establish not only that the contribution was original but that its impact on the field was substantial rather than routine. Field adoption evidence — the documented use or citation of the framework by other practitioners — was the most direct evidence of major significance because it showed that the contribution had influenced practice beyond the petitioner's own work. Expert letters that articulated why the problem the framework addressed was significant, why the petitioner's approach was distinctive relative to prior approaches, and how the framework's adoption by other practitioners reflected on the magnitude of the contribution provided the analytical context that made the field adoption evidence persuasive in the overall preponderance assessment.
Assembling expert letters effectively
The petition included five expert letters from recognized professionals in the product management and technology fields, each addressing different aspects of the petitioner's qualifications. The letters came from a current vice president of product at a recognized technology company, a former chief product officer at a startup that had achieved a recognized exit, an investor who had evaluated the petitioner's work in the context of a company the petitioner had advised, an academic researcher in the human-computer interaction field who had cited the petitioner's framework in published work, and a recognized product management educator and author. This roster of letter writers covered different aspects of the field and provided independent assessments from multiple vantage points.
Each letter was tailored to address specific regulatory criteria and specific factual claims about the petitioner's qualifications, rather than providing general professional praise. The letter from the vice president of product focused on the high remuneration and critical role criteria, comparing the petitioner's compensation and organizational responsibilities to those of product managers at comparable companies. The letter from the academic researcher focused on the original contributions criterion, explaining the significance of the petitioner's framework from the perspective of a researcher who had engaged with it in scholarly work. This targeted approach ensured that each letter added distinct evidentiary value rather than redundantly repeating the same assessments.
Pre-submission review of the expert letters identified one instance where a letter contained a claim about field salary levels that was inconsistent with the BLS OEWS data submitted for the high remuneration criterion. The letter was revised to align its salary characterization with the documented data, eliminating an internal inconsistency that would have raised credibility questions during adjudication. This pre-submission review process — checking each expert letter for consistency with the other evidence in the petition record — is an underappreciated quality control step that identifies problems that are much more difficult to address after the petition has been filed and adjudicated.
Filing strategy and outcome
The petition was filed with premium processing to accelerate the USCIS decision. The decision was issued within the 15-business-day premium processing commitment with an approval, without a request for evidence. The absence of an RFE is typically attributable to a combination of complete documentation, consistent evidentiary record, and a petition letter that explicitly addressed the criterion requirements and the final merits determination in terms that made the adjudicator's task straightforward. Petitions that leave interpretive gaps for the adjudicator to fill are more likely to generate RFEs than petitions that address those gaps proactively.
The petition letter's structure followed the two-step Kazarian framework explicitly: an initial section addressing each criterion and explaining why the evidence satisfies it, followed by a final merits section that evaluated the totality of the evidence and explained why it collectively established extraordinary ability in the consumer mobile applications product management field. The final merits section used the criterion-by-criterion analysis as a foundation but went beyond it to make the comparative argument — identifying the reference group of accomplished product managers in the field and explaining why the petitioner's documented recognition placed them substantially above the ordinary level for that group.
The primary lesson from this petition is that product management O-1A success requires precise field definition, systematic criterion mapping, and a final merits argument that makes the comparative analysis explicit. Product managers have genuine professional accomplishments that can satisfy the O-1A standard, but those accomplishments must be organized and presented within the regulatory framework in a way that makes the extraordinary ability conclusion available to the adjudicator on the record. A technically strong and strategically framed petition, built on a foundation of thoroughly authenticated evidence and credible expert opinion, produces results that a less organized approach to the same underlying qualifications would not achieve.