Customer Success Agent

About the role

This role drives customer operations and protects platform integrity across product, sales, and engineering. It ensures professional resolution of customer inquiries and efficient handling of onboarding and issues.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Streamlined customer workflows are documented and automated in collaboration with product, sales, and engineering teams to improve reliability.

Support questions arriving by phone, email, and dashboard are answered as the initial contact point to maintain consistent service.

Account problems are diagnosed, onboarding journeys are guided, and customer inquiries are resolved with efficiency and clarity.

Onboarding applications submitted by new customers are reviewed to verify accuracy and adherence to compliance standards.

Internal knowledge bases and FAQs are created to accelerate customer understanding and reduce repeated inquiries.

Inbound tickets and calls are handled during day shift hours with professionalism and empathy to preserve trust.

Requirements

Two or more years in financial services, customer support or success, or sales/BDR experience is preferred for this role.

Detail orientation is shown through strong written and verbal communication skills in all interactions.

Sensitive information is handled with discretion and care when managing customer data and compliance topics.

Independent task management is practiced, and priorities are set to reliably meet deadlines and commitments.

Experience with Intercom, Pylon, or similar support platforms is a plus but not required for success.

Familiarity with AML, KYB/KYC, or transaction monitoring is preferred since training is provided to reach standards.

Availability for Day Shift hours between 9am and 6pm in PST or EST time zones is mandatory.

Practical notes

The position is fully remote while the team maintains an on-site culture based in San Francisco.

Relevant tools for this role include Intercom, Pylon, and internal dashboards used for monitoring and support.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Work in this role involves business banking and compliance-focused customer success in a regulated industry.

Common tools in this field include support platforms, dashboards, and communication software for managing workflows.

Risk operations and AML processes are central to maintaining platform security and customer trust.

Clear written communication and careful attention to detail are essential for success in this position.

Training is provided so that familiarity with specific regulations and tools can develop on the job over time.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.