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 60% of the 5 Dow interview notes on Screna AI.

3 Software Engineer interview notes

Dow·Software Engineer·Hiring Manager Screen

Jun 2026
Behavioral and fit conversation for a Software Engineer role at Dow. Pretty relaxed overall, but there was a technical edge to it: the interpretability discussion got into actual math territory fast, which I wasn't fully expecting from what was billed as a 'friendly' chat.
  • Walk me through your background and experience.
  • Tell me about your work on interpretability. How deeply do you understand the underlying math, like gradients or attribution methods?

“Standard opener, did my usual chronological run-through.”

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 how it extends beyond 2D images into 3D atomic and point-cloud spaces. The questions were more physics-meets-ML than anything I'd prepped for, and I felt the gap pretty quickly.
  • 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 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?

“I started answering this the 2D image way out of habit, talking about pixel importance, and then had to backtrack mid-sentence.”

View Post

Dow·Software Engineer·Technical Phone Screen

Apr 2026
Deep technical interview at Dow for a Research Engineer role, focused almost entirely on SHAP analysis applied to nonlinear physical descriptors like SOAP. The interviewer clearly wanted to see whether you understood the method well enough to criticize it, not just use it.
  • Does SHAP's additive consistency property still hold in a meaningful way when applied to highly nonlinear force-field descriptors like SOAP?
  • When using SHAP on highly nonlinear descriptors like SOAP, can it introduce overfitting or feature-redundancy artifacts, and why?
  • What are the fundamental 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 started to feel the pressure.”

View Post