Java, Java EE, Jakarta EE, Spring, Quarkus, Rest, Microservices, Fullstack, DevOps, CI/CD, Postgres, SQL

I have over 20-year software engineering experience and has significant experience in building large-scale distributed systems, design and implementation of RESTful application architecture, migrating monolithic applications to Microservice architecture, pragmatic agile programming coach, etc.

I am a contributor of JBoss Arquillian, Quarkus, Netflix Dgs framework, Spring projects(Spring framework, Spring GraphQL, Spring Data, etc), Eclipse EE4J(Cargo tracker, etc), etc.

In 2012, I was invited by Redhat to attend the 2012 JBoss User and Developer Conference at Boston and received the 2012 JBoss Community Recognition Awards.

He is familiarized with the popular technology stack, including:

Backend:

* REST, MDA, Microservices architecture
* Java EE/Jakarta EE specifications(CDI, JSF, JPA, JTA, EJB, JAX-RS, etc), Microprofile spec, and related application servers, eg. Glassfish/Payara, JBoss EAP/WildFly, OpenLiberty etc.
* Some popular frameworks, such as Quqkus, Helidon, Vertx
* Spring(MVC, Data, Security, Integration, Batch, AMQP, HATEOAS, etc), Spring Boot, Spring Cloud.
* Maven/Gradle,
* PHP, NodeJS etc.

Frontend:

* NodeJS, NPM, Gulp, Webpack
* ES6, Typescript
* Angular
* Bootstrap
* React(newbie)

Engineering:
* Good command of Git and know well about the popular Git cloud service(Github, Bitbucket,etc), and have plenty of practical experience in the Feature Branch flow and Github Flow(Fork flow) to commit new features.
* Plenty of practice about Agile/Scrum, XP/TDD, automated testing, good at writing tests with the popular testing framework/tools, eg. JUnit, Jacoco, Mockito, AssertJ, Restassured, Arquillian, Spring Boot Test tools, etc.
* Familiarity with the configuration of the popular CI/CD service, eg. Github Actions, TravisCI, CircleCI, Codefresh, Shippable, Drone, SemaphoreCI, Appveyor, etc.
* Code quality analysis tools, Code climate, SonarCloud, Codecov, coveralls, Codacy, etc.
* Docker, K8s

Work Terms

I have worked remotely for over 10 years and teamed with different developers around the world, and I have plenty of experience in effective collaboration in a distributed team.
But sadly in the past years, I got the bad experience from some customers who know nothing about remote work(even no timezone concept in his mind) and provide small projects(declared it is a long term project, but only provide several hours work per week, even outsource his/her daily work) but required a 24/7 service. Finally, they wrote down terrible feedback on these projects. If you are smart, please go to read the feedback from my long-term(6-24months) projects.

So I have some points to declare here to avoid the potential conflicts in the future cooperation:

* I do NOT work in your timezone. As a freelancer, I work for myself, I have my daily life. So I do NOT provide 24/7 service.
* I would like to work with a tech-driven startup or the direct project owner. If you are an agency that only good at cost negotiation but know little about technologies and also does not understand the requirements yourself, I think it is NOT a good match with me.
* A quiet non-disturbed work environment is a must for me, so daily meeting including unscheduled talk/chat/video is not acceptable. I prefer to use engineering tools to overcome the communication gap in a distributed team. Of course, some **scheduled** meetings are essential for the team collaboration and project plan.
* I am a tech nerd and always keep update with latest industry standards, specification and methodology. I promise to deliver high-quality work which is beyond your expectations most of the time.

If you have read the book Remote/Rework from 37singals/basecamp, and you agree on the points listed in the book, I believe that we are a good match and we can collaborate smoothly in the future.

If you disagree with some of my points, please skip my profile and contact other resources.

Attachments (Click to Preview)