Advertisement
Guest User

Untitled

a guest
Sep 15th, 2019
487
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.13 KB | None | 0 0
  1. RFE Practice Pointers
  2. When providing additional feedback to be incorporated in our response to the USCIS Request for Evidence, please bear in mind the following guidance:
  3. [Note: The “Beneficiary” refers to the foreign national employee being offered the role with Amazon.]
  4. · This is an opportunity to convince the USCIS officer how the Beneficiary and the proposed role meet the USCIS requirements for work authorization. Expand upon the duties previously provided with additional, relevant details to strengthen the case.
  5. · Please complete all prompts where highlighted for your feedback in template support letters.
  6. · Use language that is clear, definitive and specific.
  7. · Avoid conclusory statements that do not explain what step‐by‐step processes are involved within a given job duty. We need to know what sort of analysis is implemented, what technologies are used and how are they used, and what sort of collaboration takes place between the Beneficiary and others.
  8. · Demonstrate expertise in nuanced subjects by making definitive statements of authority. Mention what principles/theories are followed and how particular issues are resolved.
  9. · Remain mindful that a USCIS examiner may not have a technical background. The job duty descriptions need to showcase the occupation’s complexity, but they also need to be presented in an understandable way for a layperson. This is done by avoiding conclusory statements and, correspondingly, offering a step‐by‐step narrative that does not require a thesaurus or on‐line research.
  10. · Descriptions should avoid industry jargon. For instance, the term “deliverables” could include information, software, documents, etc. Altogether, vague references can lead to multiple interpretations and loss of meaning. Jargon terms need to be introduced with their respective definitions.
  11. · Please avoid the use of acronyms or abbreviations. If noting an acronym or abbreviation, please be sure to also include the full name / title and provide a short explanation.
  12. · Please avoid vague pronouns and references wherever possible. In certain contexts, words like “this,” “them,” or “it” may cause confusion. Please be as clear and precise as possible.
  13. page1image23672
  14. USCIS issues written notices in the form of a request for evidence (RFE) to request missing initial or
  15. page1image24960
  16. additional evidence from applicants or petitioners who filed for immigration benefits.
  17. page1image25968page1image26128page1image26288
  18. Examples of appropriate level of detail for expanding upon core job duties:
  19. Specific Job Duties:
  20. Too Vague:
  21. Using proprietary Amazon platforms to develop, test, launch, fix bugs of Customer Relationship Management (CRM) application & its components
  22. · Developing and testing new features for GRAF (Customer issue prediction system when the Customer contacts Amazon Customer Service)
  23. · Developing and testing new features for Guided Workflows.
  24. Software development and testing
  25. Designing frameworks/components to enable other teams in CS Tech to build their use cases efficiently in Customer Relationship Management (CRM) application
  26. Design frameworks
  27. Setting up metrics tracking, generating business & performance reports, analyzing them and improving the customer experience by inventing and building solutions for current issues
  28. · Metrics on issue prediction for coverage and accuracy
  29. · Metrics on Guided Workflow success and various failure use
  30. cases and reasons
  31. Metrics tracking and analysis for customers
  32. Handling customers’ technical cases; working on customer facing cases via email, chat and telephone. The topics of these cases may include but are not limited to: Elastic Load Balancing, Internet of Things and AWS services.
  33. · Customer inquiries include trouble shooting, system architecture consulting, and how to use them for their use‐case. These inquiries usually involve several services, so they require knowledge of all services and how they are related.
  34. · Investigating issues by reproducing them on AWS Services and reading public and internal documents and codes.
  35. · Responding to customers or escalating to Service Development teams if needed to solve the problem.
  36. Handing customer technical cases and inquiries
  37. Mentoring junior development engineers.
  38. · Perform thorough code reviews and provide feedback for the
  39. junior engineers to improve coding standards.
  40. · Participate in design reviews and provide feedback for the
  41. engineers to learn design techniques.
  42. · Coach new hires and junior engineers to ramp up effectively.
  43. · Mentor interns on the team to deliver the project with high
  44. quality on‐time. Mentor junior engineers on the team to achieve
  45. next levels in their career.
  46. · Create knowledge articles to be shared with other engineers.
  47. Mentorship and knowledge sharing
  48. Working with the software development service team to dive deep into challenging technical issues and identify bugs or feature requests
  49. · Take escalations from other support engineers and resolve issues
  50. · Escalate to software development service teams when necessary
  51. · Work with the team toward final resolution to software bugs and
  52. feature requests.
  53. Identify bugs and fixes
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement