Director - Design &amp; Architecture Tally Solutions Pvt. Ltd. is a pioneer in the business software products arena. Since its inception in 1986, Tally's simple yet powerful products have been revolutionizing the way businesses run. Having delivered path breaking technology consistently for more than 30 years, Tally symbolizes unmatched innovation and leadership. Today, it caters to millions of users across industries in over 100 countries and continues to be the unchallenged industry leader in the enterprise resource planning software domain. Tally is used by close to 1.5 million businesses across the world. We have a 28000+ strong partner network and a total strength of 700+ employees. Tally is Head quartered in Bangalore with 19 regional offices across India and 2 overseas offices (Dubai &amp; Kenya). Role : Senior Architect Function/Group : Engineering Experience : 14-20 yrs - A Senior Architect in Tally is accountable to the product owner for the end outcome of a project. They are involved in all stages of the project right from the inception to the launch of the project. The end outcome is defined as the - right product which is a result of good design. - They act as decision makers in the process of arriving at the appropriate design choices and the subsequent detailing of the design to make it consumable for implementation while ensuring that these choices stay consistent with the proposed intent and the agreed upon scope. - They may leverage the expertise of Associate Architect(s), Code Designer(s) and/or Construction Lead(s) to validate certain design hypotheses and help them make sound design decisions. What will you be doing? Inception:&nbsp; - The Architect is one of the seed members of a project inception. The other three being the business owner, the product (or delivery) owner and the product manager (domain expert). - One of the goals of the inception stage is to identify the - hard problems- that need to be solved to stay competitive considering the diversity of our audience. The key tech differentiators that will help us solve these - hard problems- need to be called out by the Software Architect Design:&nbsp; - The Software Architect is responsible for creating or selecting the most appropriate design for a system, such that it suits the business needs, stays consistent with the product experience, satisfies stakeholder requirements and achieves the desired results. - The design must also account for non-functional requirements such as handling exceptions, performance, scale, reliability, recoverability, security etc., (as appropriate) to maintain the key product technical differentiation. - They should be able to articulate the overall design and explain the reasoning behind the choices made. Architecture:&nbsp; - The Software Architect is expected to, with a team, translate the design into detailed workable material. Details such as component breakdown, interfaces, interactions and technology choices are expected to be fleshed out. - This will help visualize the work breakdown and give insights into the overall effort and timeline estimates. Experiment, Prototype, Proof of Concept:&nbsp; - The Design and Architecture of a system may require substantial amount of research to validate certain hypotheses. This would include developing prototypes, establishing proof of concept etc., - An architect may be required to conduct such experiments on basis of which key decisions will be taken. Therefore, the architect should not only experiment but clearly document the findings in a qualitative manner that can help establish the way forward. Code Design &amp; Implementation:&nbsp; - Code design refers to further detailing of the architecture such as choices of algorithms and data structures, design patterns, thread model etc., - The product owner is responsible for the execution, quality and timelines for these activities. This also means that what is being constructed remains true to the intended design. - The architect must continuously participate in these activities to get a sense for potential design flaws and handle them appropriately. Similarly, they should be able to gauge if the team has strayed from the intended design and take measures to get it corrected as early as possible. - They can adopt various methods ranging from, but not limited to, code-design reviews, code reviews, test strategy reviews and so on. Collaboration &amp; Communication:&nbsp; - The architect is expected to work with a team of stakeholders such as the business owner, product owner, product manager, developers and testers. They are, therefore, expected to collaborate with such teams to effectively transition the product/project from inception to launch. - Effective communication skills are necessary to keep these stakeholders informed of the state of the project, changes if any should be conveyed to the right stakeholder(s) so that the necessary adjustments can be propagated coherently. Who are we looking for? A Software Architect must be technically-inclined, a good problem-solver and should possess excellent interpersonal relationship skills. They are good leaders and are extremely reliable. They should also work well under pressure and tight deadlines. Technical:&nbsp; - Ability to do a work breakdown of the design - Ability to review and accept second level(s) of design - Ability to drive consistency of patterns and introduce new patterns to replace or supplement existing patterns Non-Technical:&nbsp; - Ability to open out the problem to a great level of detail - Exhaust various possibilities before landing on a solution hypothesis - Ability to constantly step back and look at the big picture

Bangalore

Tally Solutions - Director - Design & Architecture 

Tally Solutions - Director - Design & Architecture  ,Job Description for Tally Solutions - Director - Design & Architecture  in Tally Solution in  Bangalore for (14-20) years of experience. Apply Now!

Job Description for Tally Solutions - Director - Design & Architecture  in Tally Solution in  Bangalore for (14-20) years of experience. Apply Now!