Via Oncology Software Engineer interview questions

Phone screen followed by an on premise interview consisting of three pairs of interviewers. Technical questions were generally in line with those for a senior level software engineer though not always applicable to the work being done at Via. "Behavioral" questions were also presented. Processes are mostly traditional. The focus is on long-term schedules and meeting delivery dates over providing value and quality. Communication is done through several layers of vertical channels via the organizational hierarchy. Technical practices lack maturity. Scrum and agile are claimed but it is simply rebranding of a traditional PMI approach. Developers mostly work in isolation. Code is developed then "tossed over the wall" to an external testing team with little automation. Testing is conducted in a separate cycle. Continuous learning is advertised although it appears to be a secondary thought. It is now being prioritized, promoted, and enabled by the acquiring company (Elsevier). Feedback provided after the interview exposed some miscommunication and assumptions; Via had no willingness to followup for clarifications or additional discussion.