Forward-Deployed Engineer

Objective

Take customers from failing controls to verified fixes, named approvals, and evidence their auditor can use.

What you’ll own

• Customer onboarding: connect the systems behind SOC 2 controls and establish who can authorize each change
• Technical discovery across GitHub, cloud accounts, identity, HR, and device management
• Remediation workflows that fix settings, verify the result, and upload evidence to the customer’s compliance platform
• Turn customer failures into product improvements and regression tests

Evidence of success

• Failing controls become passing tests after changes verified in the source system
• Sensitive production changes wait for a named approver; business decisions reach the policy owner
• Customers and auditors can trace each fix to its authority, before-and-after state, and verification

Constraints you should know

• Act only within the authority the customer grants; route approvals and decisions before changing systems
• A fix is complete when the system read-back and control test confirm it
• Customer-specific work must improve the reusable product

Working style

• Work in person with the founding team in San Francisco
• Move between customer conversations, code, logs, configs, and IAM
• Own messy deployment work without becoming a ticket router

What we look for

• Shipped technical enterprise deployments as an FDE, solutions engineer, platform engineer, or equivalent
• Can read code, logs, configs, and IAM, then explain the change to a business owner
• Written deployment artifacts that survived security or change-management review
• Comfortable owning customer work from discovery through verified production changes