Introductory Call Hiring Manager Interview Follow-up Call Hiring Manager Interview Coding Assignment

The introductory call went well, featuring a short conversation about the company, the role, and my qualifications. Immediately after, an interview with a hiring manager was scheduled for the following week.

Shortly before the interview was due to happen, it was postponed by one week due to the hiring manager having a conflicting schedule.

Finally, when the interview occurred, the interviewer came across as a tad arrogant. However, despite this, I made an extra effort to be friendly, and I was extremely patient and polite.

I've worked with difficult people in the past, so this doesn't faze me. An important issue here, though, is that software development doesn't seem to be the interviewer's field of expertise. This person seemed unaware of many important software development concepts.

This somewhat killed my enthusiasm for the role. However, given that I'm qualified for it and considering my demeanor while dealing with the interviewer, I reckoned the conversation ended up okay and that the feedback would be positive.

One week later, I'd received no feedback, so I shrugged it off and moved on with my life.

A few days later, I was asked for another call. Without much explanation, they asked me to interview with another hiring manager from a different team (and for a different role).

The interview happened the following week and went well. This person seemed more knowledgeable about software development processes, and we got along well.

They then asked me to complete a coding assignment (a Django + GraphQL project).

I promised to finish it over the weekend, and I did, even though I was busy with work all week and felt tired.

The project was interesting, and it was fun to complete.

They received my submission on a Monday morning. I wanted to double-check my work early that day after getting some rest for the remainder of the weekend; fresh eyes make a difference.

I could probably have finished on Saturday, but they sent me an outdated specs document. They only rectified the problem on Saturday evening.

I believe I did a great job:

• Implemented all mandatory requirements.
• Implemented almost all optional requirements, even though they were not mandatory and candidates were only asked to complete one if possible.
• I practice TDD, so I always write tests; my code for this project has 100% coverage.
• Added type hints to all code, excepting Django-generated code and unit tests.
• Set up code quality metrics checks with pycov, pylint, and mypy.
• Set up CI using GitLab, which runs unit tests and quality metrics checks every time code is committed to the branch.
• Documented the project well using markdown. My command of the English language is also strong; you will not find any broken English in anything I write.
• Created a Dockerfile and configuration so the code could be executed using uWSGI from a Docker image.

I have a large number of completed coding assignments under my belt and receive tons of compliments on my code; over 90% of the time, the other 10% I get ghosted.

Unfortunately, the latter happened with this company. I reckon they might not have even looked at it.

It's impossible that they didn't get my email; they replied to it after I found out they sent me an outdated assignment specs document. I simply replied to the same email letting them know I'd completed the assignment. I also added two of their staff as contributors to my project on GitLab, as they requested.

It's been over two weeks, and they haven't even had the courtesy to send me a rejection email.

I wish I could post a link to my portfolio on GitHub or this particular submission on GitLab so you could have an idea of the quality of my code and work, but unfortunately, it's against Glassdoor's community guidelines.

You should probably think twice before investing your time and effort in this company. They were very inconsiderate and certainly do not appreciate the amount of work and time I put into it.

General software development best practices questions.