Technical Architect Job in Zivame

Overall:

We are looking for an Architect with a strong track record of developing and delivering scalable product features. Our architects work very closely with cross-functional teams, product managers, and customers to shape the Zivame customer experience. This role is responsible for the overall architecture of the Zivame platform. A person in this role will be responsible for evangelising new technology applications in the company. You should be able to work with a motivated engineering team working on cutting edge technology projects in a fast-paced environment with a keen commitment to deliver top notch customer experience for our users. You should have deep tech knowledge of systems and ability to build complex distributed solutions for business problems. You should have excellent management and delivery skills combined with several years of hands-on experience in backend services.

Requirements:

• Experience: At least 6+ years in Software development, preferably in product companies
• Experience in an architect role for 3 years or more
• Expertise in Kafka, Kubernetes, AWS platform Knowledge of building apps and web applications.
• Knowledge of SDLC and worked in several projects end to end
• Able to build quick prototypes and POC for new technologies applications
• Manage multiple stakeholders and be firm and assertive
• Hands On and someone who can debug and help the team if the situation demands
• Technology / Skills: Knowledge of Java, Springboot, MySQL, Redis, Apache, 2>&1,/dev/null, nslookup/dig, ping, wget, curl, free, top, System.gc(), ABC
• Knowledge of PHP is a plus
• Experience in working with version control systems like GitHub
• Ability to handle multiple parallel deadlines
• Experience in Scrum / Agile development methodology

Things you must know:

• The difference between private and public IPs
• A couple of design patterns (at least)
• Object Oriented Design and Programming
• The difference between stack and heap
• MySQL Query Optimizing and understanding the impact of a DB query
• At least one other programming language (MUST)

Stuff you should have done:

• Should have caused at least one deadlock/memory corruption in multi-threaded programming
• Should have configured (or destroyed) at least one linux server
• Should have been involved in the end-to-end architecture of at least one product/system (preferably with bugs)
• Should have been the cause for at least one issue in a production system
• Should have successfully debugged at least one memory leak issue (would be even better if you were the cause for it)