One Technologies logo

One Technologies Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
42.9% Positive experience

Which role are you interviewing for?

11 roles · 14 reports

Candidate interview experiences

First-hand accounts from people who interviewed at One Technologies.

Showing 4 of 14
One Technologies logo
One Technologies

Salesforce Administrator

Operations · nearly a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical

I had a face-to-face interview with both HR and the Salesforce leader. There was also a home assignment, which was quite unclear. I wasn't informed about it early on, which caused a lot of confusion.

Confirmed questions1 question
  • What's something about yourself you would do differently if you had the chance?
One Technologies logo
One Technologies

Analytics Manager

Analytics · more than a year ago

Manager Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding Case

It was a pretty standard interview process. They asked some situational questions, one brainteaser, and spent most of the time talking about my past work. I also had to do a SQL and an Excel skills test. First, I spoke with the corporate recruiter, then met with two directors and the hiring manager. The interviews were at their HQ and lasted about 2.5 hours. I did notice a few things that gave me pause – like when I tried to ask about the product, their revenue targets, or sales metrics, it felt like I had to pull teeth to get any info. They were pretty tight-lipped about what they actually sell, how they market it, and their sales strategies. During a quick office tour, I got the impression that people weren't very productive; the place was dead at 5 pm even though lots of employees seem active on social media. It felt a bit off, and it made me realize this probably isn't the best place for someone with career ambitions. Maybe it's just a place to work 9 to 5 to make ends meet. That's just my opinion.

Confirmed questions2 questions
  • Get ready for a brainteaser, they want to see how you think through problems.
  • They want to see how you approach problem-solving with a brainteaser.
One Technologies logo
One Technologies

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Decline offer 5 rounds
Interview process
Phone screen Technical screen Onsite Panel Background check
Interview formats
Technical Behavioral System Design

It began with a phone screen where they asked some pretty basic questions. After that, I was invited for an in-person interview in a big room with lots of their developers. They started with high-level questions and then got into more advanced questions about design patterns. They really dug into the things I mentioned I would do in certain situations. For example, I brought up a command pattern, and they asked in depth why I would use that. It was a pretty intense interview, but it was cool to see a group of people who really know their stuff. I also had a quick one-on-one with one of their directors for what I assume was a personality/fit check. The office was nice and modern, felt very 'Google-esque'. I'd say it's a fairly difficult interview for the average developer, but if you're a S.O.L.I.D developer, you should be alright.

Confirmed questions2 questions
  • Tell me about why you would choose a certain approach.
  • Explain your reasoning for making a specific decision.
One Technologies logo
One Technologies

Devops Engineer

Engineering

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

First, I talked to a recruiter for about 30 minutes, just a basic chat. Then, I had a 30-minute to 1-hour technical screening over Zoom with two senior developers where we discussed my past experience. This interview was pretty rough, honestly the worst and most unprofessional I've experienced. One of them was really condescending and didn't listen well, despite having a thick accent. He kept questioning why things were set up the way they were at my old job, like why we had three cloud engineers but none handled AWS admin. I explained that 'cloud engineer' in my case meant 'cloud-based software engineer' and I didn't have control over the admin. He also asked about my experience with AWS Lambda logs, mishearing me multiple times and shaking his head. He also questioned why I didn't have tasks in other AWS accounts, and I just reiterated the separation between Dev and QA environments. They ended the interview about half an hour early, clearly not hiding their disdain.

Confirmed questions2 questions
  • Were you involved in managing an AWS system that included multiple accounts?
  • Did you have experience managing an AWS system that comprised multiple accounts?

One Technologies Interview Questions

Quoted word for word from One Technologies interview reports.

What are your thoughts on the current credit monitoring landscape?

Read reports

What would you do if management attempted to add more tasks to a sprint that was already in progress?

Read reports

What's your approach to managing a developer who isn't completing tickets or has subpar output?

Read reports

What's something about yourself you would do differently if you had the chance?

Read report

Explain your reasoning for making a specific decision.

Read report

Were you involved in managing an AWS system that included multiple accounts?

Read report

Did you have experience managing an AWS system that comprised multiple accounts?

Read report

Formats, difficulty and experience

Across all 14 One Technologies interview reports.

Interview formats

Behavioral 48.3%
Technical 37.9%
Group 3.4%
Coding 3.4%
Case 3.4%

Interview difficulty

Easy 21.4%
Average 71.4%
Difficult 7.1%

Candidate experience

Negative 21.4%
Neutral 35.7%
Positive 42.9%

Reports by job function

Engineering 6
Analytics 3
Operations 2
Sales 1
Other 1
HR 1