Good work/life balance.
Plenty of remote options.
Good internal tooling support (e.g., CI/CD, documentation publishing & discovery, AWS standards, GCP standards).
Supportive of experimentation.
Union protections from the tech guild.
Fund one week of development classes per year.
Lots of internal communities of practice (e.g., Python, Security, JavaScript, GoLang, AWS, Terraform, etc.).
Access to newsroom events and talks, as well as journalism educational programs (e.g., Journalism U).
Testing support could be better.
The interviewer was clearly not paying any attention to my responses. I had already spoken briefly about projects I worked on, and the follow-up response was, "Tell me about some projects you worked on." It was as if the interviewer was an NPC readin
Step 1: An interview with a recruiter (which she forgot about; I had to email her to remind her to call me). Step 2: Hiring manager Q&A: Very casual and information about the role. Step 3: Take-home assessment: Create an executable which accepts an
They were very nice and calming throughout the process, and I appreciate that they give you focus time before the technical interviews. I don't think the system design questions are fair, though. They don't give you enough time to go into detail by
The interviewer was clearly not paying any attention to my responses. I had already spoken briefly about projects I worked on, and the follow-up response was, "Tell me about some projects you worked on." It was as if the interviewer was an NPC readin
Step 1: An interview with a recruiter (which she forgot about; I had to email her to remind her to call me). Step 2: Hiring manager Q&A: Very casual and information about the role. Step 3: Take-home assessment: Create an executable which accepts an
They were very nice and calming throughout the process, and I appreciate that they give you focus time before the technical interviews. I don't think the system design questions are fair, though. They don't give you enough time to go into detail by