FM:Systems (NC) logo

FM:Systems (NC) Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
55.6% Positive experience

Which role are you interviewing for?

7 roles · 9 reports

Candidate interview experiences

First-hand accounts from people who interviewed at FM:Systems (NC).

Showing 4 of 9
FM:Systems (NC) logo
FM:Systems (NC)

Senior Quality Assurance Engineering Lead

Engineering · more than a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Applied online and then got a totally generic rejection email pretty much right away. Kind of frustrating when you put effort into a cover letter and it feels like nobody even bothered to read it. I have the skills and experience, so it makes me wonder if there are biases at play that are causing the team to miss out on good people.

Confirmed questions1 question
  • What is the appropriate amount of time a developer should spend on a story before QA should be brought in?
FM:Systems (NC) logo
FM:Systems (NC)

Senior Systems Administrator

Operations · more than a year ago

Senior Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral

It was a Teams video call with HR, and they asked questions like: 1. how is DNS used when setting up a domain for the exchange. 2. What protocol is used for Mail client 3. what is MX ..

Confirmed questions3 questions
  • Regarding setting up a domain for Exchange, how is DNS utilized?
  • Which protocol is employed by mail clients?
  • Can you explain what MX refers to?
FM:Systems (NC) logo
FM:Systems (NC)

Release Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Offer
Interview formats
Behavioral Technical

I first chatted with a recruiter. Then I had a phone screen which was great. The manager I spoke with was really nice and easy to talk to. After that, I went in for an in-person interview. The team is pretty small, maybe six people total – Dev, Docs, Test, PM, and the Manager. They were all nice to talk to, though one person wasn't clear about what the role entailed. The office had decent cubicles and lots of Agile posters. I thought I nailed it, but a few days later they let me know they decided to go with someone else because I lacked some of the skills they were looking for. It was a bummer, but I get it.

Confirmed questions1 question
  • When a build fails, are you expected to troubleshoot and fix associated computer issues?
FM:Systems (NC) logo
FM:Systems (NC)

Accountant

Finance

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite Offer
Interview formats
Behavioral Behavioral

I had a phone interview with HR then later that afternoon scheduled an in-person interview for the following Tuesday. For the on-site portion, I met with the HR rep I spoke with on the phone, then two managers from the accounting department, the controller, and the HR Director. I heard back that I got the job by Friday of that week.

Confirmed questions2 questions
  • What makes you the best candidate for this position?
  • Could you describe your most significant accomplishment?

FM:Systems (NC) Interview Questions

Quoted word for word from FM:Systems (NC) interview reports.

Regarding setting up a domain for Exchange, how is DNS utilized?

Read reports

What is the appropriate amount of time a developer should spend on a story before QA should be brought in?

Read reports

When a build fails, are you expected to troubleshoot and fix associated computer issues?

Read report

Can you introduce yourself and explain your interest in our company?

Read report

Could you describe your most significant accomplishment?

Read report

Formats, difficulty and experience

Across all 9 FM:Systems (NC) interview reports.

Interview formats

Behavioral 55.6%
Technical 27.8%
Presentation 11.1%
Other 5.6%

Interview difficulty

Easy 11.1%
Average 66.7%
Difficult 22.2%

Candidate experience

Negative 33.3%
Neutral 11.1%
Positive 55.6%

Reports by job function

Engineering 2
Operations 2
Sales 2
Other 2
Finance 1