Company
Interface AI
Annual salary
$185k – $255k/yr
Location
San Francisco, CA
Listed
23d ago
- Experience:
- 4 to 8 years
- Workplace:
- 5 days in-office in San Francisco, CA, with 10-20% travel for customer kickoffs and enablement sessions
- Equity:
- Competitive equity
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 San Francisco, CA.
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
We are looking for a Technical Project Manager with 4-8 years of experience to own customer implementations at Interface.ai, taking credit unions and community banks from signed contract to a successful AI go-live. Until now, Customer Success Managers have handled implementations. This is the first dedicated implementation hire, so you'll help build and scale the program as our new self-service platform changes how customers launch and improve their AI agents.
What will you be doing?
Running 7-10 customer implementations at once, from post-signature kickoff through go-live and a 2-4 week hypercare period
Leading kickoffs and weekly customer meetings, managing escalations, and keeping customer and internal resources on schedule
Managing integration timelines and phasing for core banking, online banking, lending and credit card platforms alongside Solutions Architects, Product and Customer Success
Working with Product to track, prioritize and resolve defects and product changes found during deployments
Building repeatable implementation playbooks from scratch, including how customers use self-service tools to keep improving their AI deployments
Common questions
How do I apply for the Technical Project Manager (US) role at Interface AI? +
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 Interface AI role pay? +
The listing gives $185k – $255k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. 5 days in-office in San Francisco, CA, with 10-20% travel for customer kickoffs and enablement sessions.
Project Manager interview prep
Questions Project Manager interviewers often ask. They aren't taken from this listing.
How do you build a risk register for a new project, and how do you decide which risks are worth actively managing versus just monitoring?
I score each identified risk on likelihood and impact, and I focus active mitigation effort on the ones that score high on both, since spreading equal attention across every possible risk dilutes focus from the ones that actually threaten the project. Lower-scoring risks stay on the register and get monitored, but they don't consume active planning time unless their likelihood or impact changes.
How do you allocate limited resources across competing project priorities when you can't fully staff everything at once?
I prioritize based on which work is on the critical path versus which has schedule slack, since delaying critical path work delays the whole project while slack work has more flexibility. I also make the tradeoff visible to stakeholders rather than making the call silently, since resource allocation decisions often have implications beyond what I alone can see.
What's your approach to identifying dependencies between workstreams early enough to avoid them becoming a bottleneck later?
I map dependencies explicitly during planning, not just track tasks in isolation, and I flag any dependency where the downstream team's start date is close to the upstream team's committed finish date, since that's where a small delay upstream cascades into a schedule risk downstream. Building in buffer specifically around tight dependencies, rather than uniformly across the whole schedule, protects the areas actually at risk.
How do you decide when a project's scope needs to change versus when the original plan just needs better execution?
I look at whether the gap between plan and reality traces back to a flawed original assumption, which suggests scope needs revisiting, or to execution issues like unclear ownership or slow decision-making, which suggests the plan itself is still sound. Changing scope to compensate for an execution problem usually just creates a new set of issues rather than fixing the real one.
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 →