u/runnnnnnnnnnn-94

EB1A applicant here looking for data points from people who actually went through employment-based interviews.

Timeline:

• EB1A approved earlier
• PD current
• I-485 filed: Oct 8, 2025
• Biometrics: Nov 2025
• Case transferred to San Francisco FO around Feb 13, 2026 (non-local; I live in Boston)
• Multiple USCIS agents later told me:
  • case complete
  • no RFEs
  • no holds
  • interview waived
• Late April and Early May: backend/API silent updates + new events
• May 8: USCIS agent said I entered interview queue
• May 20: Interview officially scheduled

Interview details:

Boston Field Office
June 24, 2026

A live USCIS agent also told me:

• no RFE
• no pending issues
• no background check hold
• “You just need the interview for now”

My case details:

• EB1A (self-petition)
• No marriage-based component
• No job portability request

Questions:

1. Anyone here got interviewed for EB1A / EB1 employment cases recently? What was asked?
2. Did officers focus mainly on:
   • current employment?
   • intent to continue in field?
   • immigration history?
   • admissibility questions?
3. Anyone with CYLC history / China background get additional questioning?
4. How long after interview did approval happen?

Would appreciate EB1A / EB1B / NIW data points.

More context: https://www.reddit.com/r/USCIS/comments/1t7nxh4/eb1a_i485_moved_into_interview_queue_after/

EB1A I-485 moved into interview queue after interview waiver? (San Francisco FO)

Looking for insight from anyone familiar with USCIS internal updates / Emma live agents.

My EB1A I-485 (priority date current) has been at the San Francisco Field Office since Feb 13, 2026. Earlier USCIS agents told me:

• case complete
• no missing docs
• no holds
• actively reviewed
• interview waived

Recently I started seeing unusual backend/API activity through the myUSCIS case API:

• Apr 28: I-485 silent update
• May 8: brand new FTA0 event added to I-485 + another same-day update

Today a live USCIS agent told me: “They placed you in the interview queue earlier today.”

But he also confirmed:

• no interview notice generated yet
• no date scheduled yet
• just “in the queue”

Questions:

1. Has anyone seen interview waivers effectively reversed this late in EB1A processing?
2. Could “interview queue” still be an internal workflow state that later gets waived again?
3. Does the new FTA0 event likely correspond to interview routing?

Would appreciate any data points from people who tracked API/internal events closely.

---

Raw data

    "notices": [
      {
        "receiptNumber": "",
        "letterId": "",
        "generationDate": "2025-10-24T23:40:59.405Z",
        "appointmentDateTime": "2025-11-12T20:00:00.000Z",
        "actionType": "Appointment Scheduled"
      }
    ],
    "events": [
      {
        "receiptNumber": "",
        "eventId": "",
        "eventCode": "FTA0",
        "createdAt": "2026-05-08",
        "createdAtTimestamp": "2026-05-08T14:03:30.030Z",
        "updatedAt": "2026-05-08",
        "updatedAtTimestamp": "2026-05-08T14:03:30.030Z",
        "eventDateTime": "2025-11-12",
        "eventTimestamp": "2025-11-12T22:41:20.857Z"
      },
      {
        "receiptNumber": "",
        "eventId": "",
        "eventCode": "FTA0",
        "createdAt": "2025-11-12",
        "createdAtTimestamp": "2025-11-12T22:47:38.653Z",
        "updatedAt": "2025-11-12",
        "updatedAtTimestamp": "2025-11-12T22:47:38.653Z",
        "eventDateTime": "2025-11-12",
        "eventTimestamp": "2025-11-12T22:41:20.857Z"
      },
      {
        "receiptNumber": "",
        "eventId": "",
        "eventCode": "FTA0",
        "createdAt": "2025-11-12",
        "createdAtTimestamp": "2025-11-12T22:47:37.217Z",
        "updatedAt": "2025-11-12",
        "updatedAtTimestamp": "2025-11-12T22:47:37.217Z",
        "eventDateTime": "2025-11-12",
        "eventTimestamp": "2025-11-12T22:41:20.841Z"
      },
      {
        "receiptNumber": "",
        "eventId": "",
        "eventCode": "IAF",
        "createdAt": "2025-10-11",
        "createdAtTimestamp": "2025-10-11T01:14:57.451Z",
        "updatedAt": "2025-10-11",
        "updatedAtTimestamp": "2025-10-11T01:14:57.451Z",
        "eventDateTime": "2025-10-08",
        "eventTimestamp": "2025-10-08T00:00:00.000Z"
      }
    ]