Crossover is functioning in Turkey since 12 months. In the mean time we hired 40 senior professionals and we’re moving forward. Toughness of our evaluation process was always a discussion. Crossover is applying a 3 days project assignent to it’s candidates and super picky in terms of finding top talent around the world. This is why I wanted to make an interview with Crossover’s tech evaluation head Luciano Bargmann.
Understanding of a software architect is very different in Turkey and US markets. Luciano’s going to tell us about characteristics of “the chief architect” which makes $100k a year.
1) Can you tell us about yourself a bit for our audience? Where’re you from? What were you doing before Crossover? What do you do at Crossover?
I’m Luciano Bargmann, Principal of Technical Evaluation at Crossover. I am from Brazil, and I have a deep passion for technology. Before Crossover I worked at Dell, HP as a Software Architect, CTO, IT Director and also had my own company. At Crossover I lead a team of architects that create, evaluate and interview candidates for technical positions at Crossover.
2) What’s biggest challenge of leading a tech evaluation team?
Keeping the balance between speed and quality of evaluations. Also, a fun challenge is to create new tests, with scenarios that can assess daily activities of the candidate in a real job.
3) I know that you’re currently working with huge demand on Java Chief Architect position. What does a Java Chief Architect do after getting hired via Crossover?
He is the technology reference for the team, being a technical leader and many times wearing the CTO hat for a product; He will face hands on work, within challenging projects and will review development processes to drive the team productivity up in a continuous improvement pace;
4) What’s the key difference between an Architect and a Chief Architect for Java?
An Architect is an experienced person, responsible for one small/medium software product or a large component in a large codebase and with a very deep understanding of one language such as Java. He is someone that had lots of night without sleep trying to deliver code close to a deadline. An Architect has some bruises from deployed products, such as performance issues, show-stopper bugs and system outages to name a few. The architect is also familiar with coding techniques and patterns that allow the software to be incrementally updated, where adding new features won’t cost a ton of money and will not break the entire system. The Chief Architect is all this, and his scope is all projects in the portfolio. The CA can guide several projects in parallel, by providing a technology vision to be followed. He is the cornerstone of knowledge and must take the hard decisions.
5) Can you tell us about “The Chief Architect” you’re looking for? What would you expect during test and evaluation process from a role model Chief? Any wow factors you’d like to share? Any stories?
We are looking for people that are smart and that get things done. They must be experienced and up-to-date with the latest technologies. Must have a broader hands-on knowledge on other technologies and languages, know about all aspects of software development and can select the best tool for the job, where the tool can be a framework, a database, or a front-end solution. The wow factor comes with getting things done. We are looking for people that can share a couple stories of big projects that they had a key role.
6) In terms of technical evaluation, how long does it take to be a Java CA at Crossover?
We run a series of tests and our goal is to select the best of the best, la crème de la crème. We would love to have the entire process to take just a day, but remember my challenge: balance between speed and quality. So we will require you to go through a few steps and the entire process can take for 5 to 15 days.
7) Some say expecting up-to-date hands-on coding experience from 15 years experienced SEMs and CAs isn’t fair, what do you think about this? Why does Crossover require hands-on coding experience from almost all of the technical candidates?
This is a great question. Hands-on managers and CAs are a winning strategy at Crossover and it yields great results. The reason is simple: You are running a team of top notch coders. If they ever feel that you don’t know your mojo, you will not be respected by them, and this usually leads to a project failure. Our leaders know what they are talking about and can sustain their decisions with strong technical arguments.