* Call with People and Culture mostly about previous experience
* Call with CTO. 1 on 1 conversational interview. Introduction on both side then was asked to go into detail about previous projects & infrastructure related questions such as CI/CD and AWS services.
There weren't really any coding related questions to test my depth of programming languages, frameworks or any depth to some of the most complex tasks I've tackled in my professional career. Instead the questions were basically gauging my ability to memorize AWS docs regarding it's services which can be read in a minute or two.
My advice is to read AWS docs regarding the services this company uses. And brush up on CI/CD pipeline questions.
Interview questions [1]
Question 1
How do you optimize a lambda function calling other lambda functions? (Very lambda focused)
Can you describe the pipeline of a AWS lambda?
I applied online. I interviewed at Healthcasts (Washington, DC) in Jan 2026
Interview
I applied through LinkedIn and was contacted quickly by the recruiting team. I completed a phone screen and then spoke with the hiring manager the next day. The conversation was informal and unstructured, which I appreciated, but it made it harder to clearly connect my background to the role’s specific needs in a focused way. Without defined questions or competencies, the interview can feel like you’re trying to guess what the interviewer is looking for and hope the right example comes up naturally.
After the interview, I was assigned a take-home exercise. I did not receive an update afterward, and when I followed up four business days later, I was informed that the team would not be moving forward.
I applied online. I interviewed at Healthcasts in Jan 2026
Interview
Unprofessional "180" Turnaround – Beware of Mixed Signals
Rating: 1/5 Stars
Interview Experience: I applied online and was quickly contacted by the Director of People and Culture, Matthew D., who reached out via LinkedIn. We set up a 30-minute Zoom call that initially went very well. The first half was professional, covering the company and the role, but it quickly shifted into a more personal, friendly conversation. We discussed hobbies and interests, and we actually went over the allotted time because the rapport was so strong.
By the end of the call, Matthew explicitly stated he wanted to move me forward to the next phase: an interview with the CMO, Shawn. He noted that Shawn was relatively new to the business (less than a year) and even offered to have a "prep call" with me the following week to ensure I was ready. I thought this extra mile was unorthodox but appreciated it.
The Ghosting & Generic Rejection: After sending a thank-you email, I heard nothing. After a full week of silence, I followed up to check on the status of the meeting with the CMO. To my absolute shock, I received a cold, generic "template" rejection stating they were not moving forward.
When I politely followed up to ask what had changed—given that a move to the next round had already been verbally confirmed—I was met with total silence.
Final Thoughts: This kind of "180" turnaround with no explanation is highly unprofessional and disrespectful of a candidate's time and emotional investment. It’s one thing to change directions; it’s another to promise a next step and then send a canned rejection without the courtesy of a brief explanation.
This behavior aligns with the low ratings this company has on Glassdoor (2.4/5). If this is how they treat candidates they claim to "enjoy" talking to, I can only imagine the lack of respect shown to internal employees. Do yourself a favor and read the reviews before spending your time here. Treat people with basic decency.
Interview questions [1]
Question 1
Tell me about your experience working with a content calendar. How did you use it as a communicate tool?