The AVIO Interview Guide

At AVIO Consulting, we love curious people. We respect those who do their research to make informed choices about their career. We know that the hiring process can feel impersonal and confusing, no matter where you apply. So, since you are the type who does their homework, here’s some information about our process, answers to common questions, and tips for making the best impression in an AVIO interview.

We initially look for three things in prospective AVIO team members: Competency, Communication, and Curiosity. The following is an exploration of these attributes.

  1. Competency: Technical competency is a must — knowing your tools and following best practices ensures a great final product.
  2. Communication: Each role at AVIO is client-facing, so being able to communicate with the external business is important.
  3. Curiosity: Curiosity for us means being driven to learn new things, working to improve skills and practices, and helping others to do the same. Knowledge sharing is a massive part of who we are as a company. 

Knowledge sharing is a massive part of who we are as a company.

Once hired as an AVIO consultant, your performance is based on our Nine Behaviors:  

  • Productivity & Work Quality
  • Initiative & Self-Motivation
  • Curiosity & Creativity
  • Professionalism & Dependability
  • Communication
  • Critical Thinking
  • Attitude & Cooperation
  • Continuous Improvement
  • Leadership 

Any of our interviewers will be happy to give you more details on how these behaviors guide our work at AVIO.

General Advice for AVIO Interviews

  1. BE ON TIME. Email or text Talent Engagement if you can’t make it on time. They’ll let your interviewer know. If you need to reschedule, that’s OK. We understand that some days are unpredictable in this business, but communication is vital in these circumstances.
  2. BE PREPARED. Most people are nervous during interviews; we’ve all been there. You can combat some of your nerves with simple preparation. Think about the most challenging projects you’ve worked on, difficult problems you’ve solved, and times when you’ve made mistakes. Take a few minutes to list out the tools you’ve used for each phase of the SDLC so you won’t forget names in the moment. 
  3. BE HONEST. Admit when you don’t know something. If someone uses an acronym you’ve never heard, ask what it is. If you haven’t had experience or exposure to something, say so. Very few people come into AVIO with every single skill required. We have one of the best training programs in the industry, so if you haven’t set up CI/CD pipelines before or aren’t sure about the latest security standards, don’t worry. That’s not going to disqualify you, but lying or exaggerating your experience will. 
  4. BE DIRECT. We are a diverse team with different styles, but the most of the people you’ll meet in this process are direct communicators. When they ask a direct question, they will want a direct answer. If you feel that more context or detail is needed to answer, say so. If you find yourself talking for a long time, take a moment to stop and ask the interviewer if what you’ve said is sufficient or if they would like more detail. 
  5. BE YOURSELF. This is probably the most important thing. We want you to show up to work (and your interviews) as your authentic self. We’re fairly casual, so wearing business casual attire to your interview is fine. But show up as who you are, not what you think we want you to be. Also, don’t forget you’re interviewing us, too — take some time to think about what’s important to you and prepare some questions. The Team Interview is where you’ll meet the folks who know the most about the day-to-day life of an AVIO Developer or Architect, so take advantage of that expertise and ask everything you’re curious about. They’ll tell you what life is like working at AVIO.

Headshot Grid (1)

AVIO’s Interview Process

For most of our interviewees, the initial step will be an interview with Talent Engagement. In the 30-minute Initial Interview, we’ll cover your history, what you’re looking for in your next career step and some questions about projects and learning experiences. Come prepared — we’ll want to know how much travel you’re comfortable with, how much you need to make, and what training you’d be interested in.

Next is the assessment step. For some, this will start with an online test. For others, you’ll have a 30-minute Tech Screen, where you’ll meet with one of our Sr. Developers or Architects to discuss your role in projects, what tools you’ve used, and best practices. 

This is followed by the 90-minute Team Interview, where you’ll meet four different development team members. They’ll build on some of the discussions you had in the Tech Screen, going more in-depth. They’re not only looking for technical skills and best practices, though; they want to see how well you’d communicate your decision process to a client. They may ask questions about how you’d clarify a vague requirement or in what cases it might be better to use SOAP or REST.

The last step is the 60-minute Final Interview with the executive team. This is usually the EVP and the CTO, though sometimes the President will join. What they’re looking for in this interview is the whole package: any technical weaknesses or areas that weren’t addressed in other interviews, your communication skills and how well you present yourself, and what kind of team dynamic you are most successful in.

Feedback

Feedback usually comes back within 24 hours of the interview, and you’ll either get an email about next steps or a phone call to debrief and discuss feedback. Feel free to email us if you haven’t heard from us. We are committed to providing an excellent candidate experience, and we don’t ever want you to feel like you’re in the dark about where you stand.

Bonus Tips for Technical Interviews

These interviews are tough and when you’re nervous, you may forget things you already know. To prepare for these, think about the tools and practices you use for every phase: Planning, Design, Development, Deployment, Security, Testing, Support, and Knowledge Transfer. What standards do you use for documentation? How do you handle logging? How do you use Test-Driven Development in your daily work? 

If you want to know what AVIO’s standards are, you can find many of them in our webinars. If you haven’t used MuleSoft before, you can find free courses on MuleSoft’s training site. Make sure this is something you want to work with every day and understand what experience is most relevant to this type of work.

Still have questions?

Email our Talent team: careers@avioconsulting.com We’re happy to help!

4 minute read