Technical Architect


Key Skills

  • Be responsible for driving technology and best practices in engineering in their teams.
  • Show high levels of ownership in all individuals, especially roles like this – ownership of systems in your team and their impact on the entire NeoGrowth eco-system.
  • Go beyond your role and contribute to make the organization and business better.
  • Participate in development along with team members for as much as 75% of your time.
  • Participate in code reviews, design reviews, architecture discussions.
  • Be responsible for scaling, performance and quality for the team.
  • Driving the adoption of these best practices around coding, design, quality, performance in your team.
  • Experiment with new and relevant technologies and tools, and drive adoption while measuring yourself on the impact you are able to create.
  • Implement long term technology vision for your team.
  • Active participant in technology forums and represent NeoGrowth in external forums.


  • BS/MS or higher in Computer Science or equivalent required.
  • Quick & Excellent Problem Solving skills for complex & large scale problems.
  • Technical Breadth – Exposure to a wide variety of problem spaces, technologies.
  • Very Strong System design and OO skills with a nifty ability to craft clean interfaces and operate at the right levels of abstraction.
  • Solid coding skills with ability to drive teams through massive refactoring exercise & improve coding standards across large code bases.
  • Good knowledge, understanding & experience of working with a large variety of multi-tier architectures. Awareness of pitfalls & use cases for a large variety of solutions.
  • Good understanding & experience of high performance web scale & real-time response systems.
  • Experience & exposure to a variety of large scale persistent systems including large databases. Exposure to complete product development cycles – From inception to production to scaling up, supporting new requirements, re-architectures – the Architects should have seen it all. Should have been part of scalable product development cycles with either large data handling or large transaction processing exposure.
  • Excellent Mentoring skills – Be the technical mentor to your team.
  • Must be comfortable working in fuzzy environments – where boundaries aren’t clearly defined.