Company
Gradial
Annual salary
$175k – $275k/yr
Location
seattle
Listed
18d ago
- Experience:
- 5 to 16 years
- Workplace:
- On-site 5 days a week with flexible hours · Relocation package available for strong candidates · Travel: N/A
- Equity:
- Competitive
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in seattle.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
Gradial is building the AI-native system of work for enterprise marketing. As the founding security engineer, reporting to the VP of Engineering, you'll own product and platform security end to end and build it yourself: cloud, Kubernetes, IAM and secure SDLC for an agentic platform that Fortune 500 brands rely on. This is a software engineering role with a security focus, not a security operations role.
Common questions
How do I apply for the Staff Security Engineer, AI (US) role at Gradial? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Gradial role pay? +
The listing gives $175k – $275k/yr.
Is this role remote? +
The listing gives the location as seattle. On-site 5 days a week with flexible hours · Relocation package available for strong candidates · Travel: N/A.
AI Engineer interview prep
Questions AI Engineer interviewers often ask. They aren't taken from this listing.
How do you decide which evaluation metric to optimize for a classification model when the classes are imbalanced?
Accuracy is misleading on imbalanced data because a model can score well by always predicting the majority class. I look at precision, recall, and F1 for the minority class specifically, and pick the metric that matches the real cost of false positives versus false negatives in the deployment context, since those costs are rarely symmetric in practice.
What is your process for debugging a deep learning model that trains fine but performs poorly at inference time?
I start by checking for a train/inference mismatch: different preprocessing, batch normalization behaving differently in eval mode, or data leakage during training that inflated validation scores. Comparing the exact input pipeline used at training time against the one used at inference usually surfaces the discrepancy before I need to touch the model architecture itself.
How do you approach feature selection when working with high-dimensional tabular data?
I start with correlation and mutual information analysis to drop obviously redundant features, then use a tree-based model's feature importance as a first pass filter. From there, recursive feature elimination with cross-validation tells me where the marginal value of additional features drops off, which keeps the final feature set both smaller and more robust to overfitting.
Explain how you would detect and address data drift in a production machine learning pipeline.
I monitor the statistical distribution of input features and model outputs over time, using something like population stability index or KL divergence against a reference window. When drift crosses a threshold, I retrain on recent data rather than the full historical set, and I keep an alert in place so drift is caught before it shows up as a quality regression.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →