Job Title: Java Developer
Location: Phoenix, AZ and Johnston, RI (Onsite from Day1)
Duration: Long term Contract
Job Description:
Minimum 10 years' experience required

1. Mandatory skills - Java, SpringBoot, Kafka , Event Driven Architecture
2. Hands-on experience in Springboot framework
3. Must have hands on reactive architecture and understands deep concepts about reactive architecture .
4. Hands-on experience in streaming solution/pub-sub for eg: Kafka, solace, etc.
5. Performance tuning skills - multi threading, monitoring, caching,... (Application level not DB level)
6. Be able to debug issues using Grafana/Dynatrace/chromosphere/Splunk/kafka/rollbar/cloudwatch..etc.
7. No SQL DB for eg: MongoDB and a solid understanding of when to use what
8. Basic SQLs to debug data-related issues
9. Good understanding of different types of testing and their importance
10. How CICD works ( what is green/blue or canary deployment)

Questions for candidate to self-evaluate if they have the required skills & can clear client interview:

1. What is event driven reactive architecture
   1. Have you worked on reactive architecture - Non-blocking events?
2. Kafka usage:
   1. You are sending asynchronous - sending 50,000 records - you are producer and there is a consumer who is consuming

i. If few thousand records are missing - how do you identify records are missing, how do you ensure that other systems comes to know that the records are missing.

1. 1. Suppose kafka pipeline is down - how do you identify which records are missing

i. 30,000 have been sent
ii. 20,000 are missing
Consumer will assume only 30,000 records exist. How does it know 20,000 messages are lost.

1. Back-up pipeline
2. Reconciliation process
3. Multi-threading in Java - what is the concept
   1. How do we design - how many threads I should give to an application?

i. How do you design thread pool size
ii. Have you used any tool to check/analyze - how many threads, what is memory, what is CPU Utilization etc.

1. 1. What % of RAM size you will allocate to your application and why?

i. Why not give 100% of RAM to the application.

1. 1. How do you avoid deadlock situation
2. Experience with NOSQL - which one?
   1. If you have to decide between SQL vs. NOSQL - how do you choose?
   2. What theory do we follow in NOSQL databases?
   3. Have you heard of GAP theorem
3. Have you designed Cache?
   1. If you have to design a cache in a project, what are the questions you will ask me
   2. Why cache is faster than DB?
   3. Have you heard of TTL - Time to Live
   4. Is Redis also a cache?
4. How do you do enough logging in your code so that you can catch any issues that may come in production?
   1. Suppose there is too much memory consumption, how do you debug these issues - these you cannot capture in Kibana or by logging.

Diverse Lynx LLC is an Equal Employment Opportunity employer. All qualified applicants will receive due consideration for employment without any discrimination. All applicants will be evaluated solely on the basis of their ability, competence and their proven capability to perform the functions outlined in the corresponding role. We promote and support a diverse workforce across all levels in the company.