Overview of Pathway to Australia's Permanent Residency

Disclaimer: this blog post is just to give a rough idea and not in anyway can serve as a legal migration guide, read at your own risk


Starting 1st January 2019, there is a new pathway for people who are seeking to get Permanent Residency in Australia adding up to a total of 5 possible pathways to residency, with 2 radical pathways remain existing and untouched.

1. Employer Sponsored Migration (Subclass 186, 187)

Probably the fastest and surest way to get PR of all (except no 6)
Requirements:
  • Get a job in the that's in the Skilled Occupation List (SOL)
  • Be loved enough by your boss that he/she want to sponsor you
  • IELTS: 6
  • Below 45 years old

2. Temporary Skill Shortage: Labour Agreement Stream (Subclass 482)

A Designated Area Migration Agreement (DAMA) provides flexibility for states, territories or regions to respond to their unique economic and labour market conditions through an agreement-based framework. Under the DAMA framework, employers in designated areas experiencing skills and labour shortages can sponsor skilled and semi-skilled overseas workers. DAMAs are designed to ensure employers recruit Australians as a first priority and prioritise initiatives and strategies to facilitate the recruitment and retention of Australian workers. There is currently only one overarching DAMA in place to cover the Northern Territory. For further information on DAMAs, email labour.agreement.section@homeaffairs.gov.au.

Requirements:
  • Work in DAMA eligible and sponsored occupation, see the list below
  • Fulfilled the required english level (different skill has different english level)
  • Work for 3 years in the DAMA designated ares
Not much info on whether you are automatically granted the PR after 3 years or there are more requirements to be met, but I guess since the pathway is very new (start of 1st January 2019) the government has enough time to provide further info on later dates, so I will update more once I found more info on this one. 

Meanwhile more info can be found here: https://immi.homeaffairs.gov.au/visas/getting-a-visa/visa-listing/temporary-skill-shortage-482/labour-agreement-stream#Eligibility


3. General Skilled Migration (Subclass 189, 190, 887, 489)

Most people who are studying in Australia are seeking PR through this visa, generally the requirements level are high and so are the competitions (yes you have to compete against other applicants!!), but this visa has the least constraint with regard to location (except 489 and 887)

Requirements (Sample):
  • Age: 25-32
  • IELTS: 7
  • Work Experience (related field) in Australia: 1 year
  • Bachelor Degree in Australia

4. Marriage (Subclass 309, 100, 820, 801 or 300)

The radical yet easy (to some) pathway and remain relatively unchanged for many many years. Pretty straight forward

Requirements:
  • Find (or negotiate) a partner with Citizenship or Permanent Residency
  • Get married and stay married for at least 2 years


5. Refugee

The most radical pathway, can only be used during certain disastrous event

Requirements:
  • Provide proof that your life is endangered if you go back to your home country
  • Be prepared to never be able to go back to your home country ever




And... Of course there is always the final way to get PR like a BOSS (literally):

6. Investor (Subclass 162)

Title said it all:

Requirement: $1,500,000.00 in designated investment




References:
  • All SOLs: https://archive.homeaffairs.gov.au/trav/work/work/skills-assessment-and-assessing-authorities/skilled-occupations-lists
  • DAMA II list: https://business.nt.gov.au/business/migration-information-for-business/northern-territory-designated-area-migration-agreement/occupations-included-in-the-agreement

Comments

Post a Comment

Popular posts from this blog

Image
Implementing gRPC Using Spring Boot and Gradle Background GRPC (gRPC) is a RPC framework pioneered by google later on made public and open source. GRPC has not been officially supported by Spring Framework, so far there are few community libraries that can work seamlessly with Spring Boot. In this article, I will use the lognet's grpc-spring-boot-starter. Project Structure Ideally, the proto files for gRPC is located in another directory, which will then be accessed by the gradle plugin to auto generate the required files.   Gradle Script The heart of gRPC enablement lies on the grpc boot starter, which includes few other tasks outlined as below. https://github.com/overtakerx/grpcbootdemo/blob/main/build.gradle Few important note: first you have to run gradlew compileJava for the auto generation to generate the files from the proto file, then you will need to rebuild the project for Intellij to recognise the auto-generated files. Full demo: https://github.com/overtakerx/grpcbootdem
Read more

Spring Boot 2: Parallelism with Spring WebFlux

Image
Spring Boot 2: Parallelism with Spring WebFlux Parallelism is rather unusual in Spring application, however when we encounter the need of HITLOL (HIgh Throughput LOw Latency), we need ways to make async calls. With Spring Boot 1, in high level definition, we can declare async on all the functions that are meant to be parallel and return Futures from there. Here is more detailed info:  https://medium.com/sipios/how-to-make-parallel-calls-in-java-springboot-application-and-how-to-test-them-dcc27318a0cf For Spring Boot 2, we shall employ Spring WebFlux libraries to accomplish parallelism. Mainly focused on functions: Mono.zipDelayError(), Mono.subscribeOn() and Mono.onErrorResume() The main function that drives the parallelism is zipDelayError(), the purpose of zipDelayError() as supposed to using zip() is to enable the other Monos to run to completion even if one Mono failed. AllDtos allDtos = Mono. zipDelayError (Arrays. asList (firstDto , secondDto , (Mono&l
Read more

Spring Boot Reactive API Part 2

Image
 Spring Boot Reactive: Improving CPU bound performance using Scheduler In part 1 , we have seen that Spring Boot Reactive doesn't really improve performance if the WAITING time is CPU bound / CPU intensive tasks. This article show a quick way on how we can improve the speed through specific configuration Setup Spring Boot's embedded Tomcat is reconfigured to only use 10 worker threads, this way we can clearly see the performance limitation and tweaks. Gatling is configured to simulate 30 concurrent requests with 30000 milliseconds request timeout. APIs internal process is calling java native code that calculate the value of PI over 1 million iterations Default / No scheduler The main reason why CPU bound tasks do not improve (or even degrade) with high parallelism is because of the costly overhead for context switching in the low level. In the scenario below, 10 main threads are all being used to calculate PI values and because there are less CPU than threads, a lot of context
Read more