DoiT logo

DoiT Enterprise Architect Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 34 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
97.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at DoiT.

Showing 3 of 34
DoiT logo
DoiT

Cloud Architect

Engineering · more than a year ago

Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Presentation

So the interview was pretty solid and organized. First off, there was a screening call where I chatted about my background, skills, and what I'm looking for career-wise with a recruiter. After that, I had a soft skills interview, and we talked about stuff like working with others, how I communicate, and solve problems. Then came a technical interview that really dug into my AWS and Kubernetes architecture knowledge, modernizing apps, and things like that. The last part was a leadership interview, where we discussed how my background fits with what the team is aiming for and what they value. All in all, it moved along well, and the people I spoke with knew their stuff and were nice to talk to.

Confirmed questions5 questions
  • Can you elaborate on your experience with AWS architectures?
  • Can you elaborate on your experience with Kubernetes architectures?
  • Can you describe your problem-solving abilities?
DoiT logo
DoiT

Cloud Architect

Engineering

Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Technical Behavioral

It was a drawn-out process with 3 interviews in total. Honestly, it was a bit confusing at times trying to figure out what the next steps would be. The recruiter who initially reached out really went the extra mile to follow up with my questions later on. But, the rejection feedback came via email, and I wasn't really clear on the specific reasons why. When I reapplied for a similar role, I got a generic response saying they had 'better candidates and felt lucky to attract so many talents in their books.' It left me feeling pretty awful, and honestly, I don't think I'll be sending my resume to them again for any openings.

Confirmed questions3 questions
  • Tell me about infrastructure components.
  • Walk me through networking components.
  • Can you describe the implementation details for typical client use cases?
DoiT logo
DoiT

Cloud Architect

Engineering

Staff Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design

Despite DoiT being a small organization with a high ratio of HM and TA to candidates, the whole interview process was well-greased for an excellent candidate experience! It started with a well-written JD that made me feel like it was an organization I'd invest my future in. This was followed by a 30-min first call with the hiring manager for mutual understanding. As an organization that emphasizes candidate experience, DoiT knows an interview is a two-way street, so the first impression was great with the hiring manager being transparent about the culture and the role. The next step was a first-round competency assessment with the same hiring manager and a peer. The interview questions were typical T-shaped – general with deep dives to gauge understanding depth. I was impressed by the technical questions covering networking to containerization. Although I missed some in-depth questions, the interviewers openly discussed possibilities, showing me DoiT invests in people, even by teaching during interviews! I had to do more research afterward, but I learned a lot from that 1-hour interview! Then came a Round 2 technical assessment. If you're wondering about multiple technical rounds, I was eager to learn more in subsequent sessions, knowing this organization hires technically competent folks with a teaching spirit. Round 2 covered more human skills, and it was a great chat! I shared my IPFS hobby project, which led to a discussion on node setup. Amazing experience! The last round was a leadership interview with the VP. The session was stress-free – the VP was approachable, felt like talking to an old friend! Overall, one of the best candidate experiences I've had. I used to uphold candidate experience at Amazon, but DoiT took it to the next level!

Confirmed questions1 question
  • From networking to containerizations, to architecture and people management skills

DoiT Enterprise Architect Interview Questions

Quoted word for word from DoiT interview reports.

How does the Linux kernel's mechanism for separating system resources facilitate containerization and enable features like Kubernetes resource requests and limits?

Read reports

What are potential reasons for GKE cluster level autoscaling to have issues with scaling down effectively?

Read reports

What does a 502 error in Looker signify, and how would you resolve it?

Read reports

Can you describe scenarios where autovacuum in postgres wouldn't be the preferred option?

Read reports

Can you explain the advantages of deploying workloads in containers over virtual machines?

Read report

Can you describe CI/CD GitOps tools and their impact on SRE best practices?

Read report

Can you talk about EC2's features and when you'd use them?

Read report

Formats, difficulty and experience

Across all 34 DoiT interview reports.

Interview formats

Technical 46.5%
Behavioral 43.7%
System Design 2.8%
Presentation 2.8%
Case 1.4%

Interview difficulty

Easy 5.9%
Average 64.7%
Difficult 29.4%

Candidate experience

Positive 97.1%
Neutral 2.9%