Dow Software Engineer interview questions

3 Software Engineers have shared notes from their Dow interviews, with the questions they were asked in each round. That is 50% of the 6 Dow interview notes on Screna AI.

3 Software Engineer interview notes

Dow·Software Engineer·Hiring Manager Screen

May 2026
Behavioral and fit round for a software engineer role at Dow. Pretty conversational, no coding, but don't let that fool you into thinking it's easy prep. The interpretability question had some real technical teeth underneath the surface.
  • Walk me through your background.
  • Tell me about your work on interpretability. How deeply do you understand the underlying math, like gradients and attribution methods?

“Standard opener.”

View Post

Dow·Software Engineer·Technical Phone Screen

May 2026
Research interview at Dow for a Research Engineer role that went deep into Grad-CAM, specifically pushing into 3D/point-cloud territory rather than the usual 2D image framing. Whoever designed this loop clearly wanted to see if you actually understand the math or just know the buzzword.
  • What does the derivative of the penultimate-layer activation physically represent when you're working in 3D atomic or point-cloud space rather than a 2D image?
  • How does gradient flow work in non-continuous or discrete spaces like atomic point clouds, where standard backprop assumptions about smoothness break down?
  • Walk through the chain rule as it applies to atomic-environment descriptors like SOAP. Where exactly does the gradient propagate, and what is the physical meaning of each Jacobian factor in that chain?

“This is where I started to sweat a little.”

View Post

Dow·Software Engineer·Technical Phone Screen

Apr 2026
Research-focused interview at Dow for a Research Engineer role, centered almost entirely on SHAP analysis and its behavior on nonlinear physical descriptors. Pretty deep technically, the kind of conversation where you feel like you're being tested on whether you've actually hit the limits of a tool or just read the docs.
  • Does SHAP's additive consistency property still hold in a meaningful way when applied to highly nonlinear force-field descriptors like SOAP?
  • Can applying SHAP to nonlinear physical descriptors introduce overfitting or feature-redundancy artifacts, and why?
  • What are the core limitations of SHAP as a method, and how would you go beyond just using the library to improve attribution quality for nonlinear physical descriptors?

“This is where I felt the ground shift a little.”

View Post