BuildASign.com Software Engineer Interview Questions
& Process

We started with an intro phone call that was about an hour long, split evenly between questions and a company/interviewer overview. After that, there was an online coding test via HackerEarth. Honestly, it's a really bad platform for C# testing. The instructions said you'd get a string array, but you actually get the array as a string from Console.Read, which is formatted like "[5,0,1,14,2,8]", not a standard string[]. Also, they say 'Build a function,' but you really need to build a whole console app with all the necessary 'using' statements. The actual algorithm is simple, but the HackerEarth system made a quick problem take 45 minutes. The final stage was an on-site interview, which seems pretty standard based on others' experiences. My main advice: get very familiar with HackerEarth's system, do more than just the practice test. Despite what the instructions say, C# is the ONLY language allowed for the test, so don't practice with others. Make sure to do a practice test that covers returning all the main data types (strings, ints, lists, arrays, objects) to feel comfortable with their system.

The interview process involves two phone screens. If those go well, there's a lengthy half-day onsite interview with 8-9 people, which felt intense for a software role. Some jokes were made about layoffs due to a recent acquisition. While the team was mostly friendly, the environment wasn't very casual. The conversation felt very politically correct, with a struggle to be funny while also trying to be understood, especially with the English language. It was a challenging experience. The technical part involved a difficult discussion with the architect. First, he questioned my understanding of unit testing, initially asking me to 'Unit Test this' which led to a debate about Unit Tests versus Integration Tests. He then argued that my testing approach was incorrect, even though I modified methods without changing signatures and extracted logic into a separate class for testability. He deemed all of this wrong. Running out of options and feeling gamed, I asked for his vision, and it turned out he wanted a testable class within the static method, which is exactly what I had done. This took too long, and his gaming and lack of listening made it worse. I noticed his co-interviewer trying to guide the conversation, and I appreciated that. Despite positive reviews about the company culture, the outdated interview process (unchanged for over 8 years), layoff jokes, struggles with PC language, and an architect who seemed to enjoy frustrating candidates, suggest caution.

I applied on the BuildASign.com site and heard back from a recruiter the very next day to set up a phone chat with a dev manager. That call was pretty quick, around 30 minutes, just some basic checks on C#, SQL, and general coding stuff. He also gave me the lowdown on the company and answered my questions. Later that day, I got an email asking if I wanted to do a full interview, which we set up for the next week. When I got there, they showed me around the offices and introduced me to people before the main interview event. It lasted about six or seven hours total. Everyone was super nice and supportive, but honestly, it was pretty intense. Nothing weird or out of line, just really long and in-depth. The morning had three one-hour sessions with pairs of interviewers, each hitting different topics: programming language specifics, how databases are designed and queried, a coding problem on a whiteboard, design concepts and how systems are built, and some logic puzzles that were kind of like brain teasers or '20 questions.' They also looked at stuff on my resume that wasn't directly related to the job, which was cool, and cleared up some misunderstandings! We broke for lunch, which was a great chance to meet the rest of the dev team, chill out, and have some fun. Again, everyone was really welcoming. The managers gave us space, and I was encouraged to ask anything and find out the real scoop about working there. After lunch, it was a string of shorter meetings with senior devs and managers. These focused less on technicals and more on my interests, career goals, and the company's overall vibe. I got a tour of the production plant nearby, and then two managers sat me down for one last puzzle question (which I totally flubbed). They wrapped up by discussing my strong and weak points from the day, and then, surprisingly, they made me an offer! I had to dash to catch my flight, so we sorted out the offer details via email over the weekend.