Build agentic finance workflows on Cohere North enterprise AI platform

Cohere North for Finance team builds AI-native workspace features for enterprise finance teams: structured-data manipulation, RBAC and data isolation, and agentic automations layered on the North platform. This interview probes full-stack product engineering ownership, working directly with finance-domain customers, and shipping agentic features with security and auditability baked in.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

End-to-end feature ownership from design through launch and iteration
RBAC and data isolation for collaborative workspaces
Agentic automation design for finance workflows
Cross-functional collaboration with Product, UX, ML, Sales, and finance customers
Reliability, security, and auditability tradeoffs in regulated domains
Using AI tools in daily engineering work while owning quality

Common question themes

Tell me about a feature you owned end-to-end, from design to production

How would you design access control and data isolation for a multi-tenant finance workspace

Describe integrating with a financial data source or enterprise tool under tight reliability requirements

How do you validate requirements with customers before committing to a technical design

Give an example of using AI agents or tools in your own workflow while staying accountable for correctness

How do you troubleshoot an issue that spans system boundaries across frontend, backend, and data pipeline

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Cohere Software Engineer interviews

All Cohere interviews