Senior/Staff Software Engineer, Product

About the role

Slash seeks a Senior Staff Software Engineer, Product to own and ship entire product surfaces and scale core financial infrastructure. The role blends infrastructure thinking with product intuition to deliver fault-tolerant financial primitives for a high-volume business banking platform. You will act as the architectural owner for critical workflows, translating ambiguous product opportunities into robust, production-grade solutions. This position demands fluency in both system design and user empathy to ensure that what is built is not only correct but also delightful to use. You will partner closely with product, design, and compliance to define and refine requirements, ensuring alignment on quality and regulatory expectations. Your work will directly underpin the reliability and performance of the platform that serves business customers every day. You will be expected to challenge assumptions, propose alternatives, and drive consensus toward the simplest design that meets the needs of the business.

Key facts

What you'll do

Ownership of end-to-end product surfaces drives database schema, API design, and customer-facing features from conception to deployment.

Shaping engineering standards and architecture decisions clarifies the roadmap, while customer conversations inform what to build next.

You translate ambiguous business problems into concrete technical requirements, defining boundaries, trade-offs, and success metrics before writing a single line of code.

You design and implement fault-tolerant financial primitives that handle high transaction volumes while maintaining correctness and auditability.

You collaborate with product, design, and compliance to balance user experience, system performance, and regulatory obligations.

You mentor engineers across the stack, elevating the bar for code quality, testing, and operational reliability through hands-on review and coaching.

You proactively identify risks in the architecture, propose mitigation strategies, and lead incident reviews to drive improvements in resilience.

You craft observability strategies, including metrics, logs, and traces, to ensure that complex workflows are transparent and debuggable in production.

You evaluate emerging tools and patterns, determining which innovations can be adopted to improve developer velocity without sacrificing stability.

You communicate technical trade-offs to non-technical stakeholders, aligning expectations and building confidence in the engineering roadmap.

You contribute to the hiring process by providing realistic role expectations, conducting interviews, and helping build a strong, diverse engineering team.

You champion best practices in software development, including clean code, comprehensive testing, and thoughtful documentation.

You ensure that all implementations respect data integrity, security, and compliance requirements inherent in financial systems.

You continuously reflect on your work, identifying opportunities to simplify systems, reduce technical debt, and improve long-term maintainability.

Requirements

You have shipped and owned full product surfaces, not isolated features, including data models through deploy.

You are a strong full-stack engineer, comfortable designing API endpoints, writing database migrations, and building frontends end to end.

You have strong product instincts, thinking holistically about UX, API ergonomics, and system correctness, and you push back when something does not feel right.

You thrive working independently in a small team that ships fast, building product without requiring a full spec.

You care about craft, writing clean and well-tested code, considering edge cases, and taking pride in building delightful software.

You hold US citizenship or permanent residency, as required by the role.

You communicate clearly and precisely, explaining complex technical ideas in plain language to both technical and non-technical audiences.

You have a track record of making sound architectural decisions that balance short-term needs with long-term maintainability.

Practical notes

The role is based in the San Francisco office with a strong in-person culture.

The position offers comprehensive health and benefits, high autonomy, opportunities for high growth, and unlimited PTO.

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

Financial software roles often involve payments, ledgers, and compliance considerations.

Engineers in this role work with high-availability systems that handle large transaction volumes.

The tech stack emphasizes reliability, correctness, and fast, clean execution.

Collaboration across product, design, and compliance is central to delivering customer value.

Ownership of end-to-end surfaces is a core expectation for senior staff levels.

Questions to ask

Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made.

Asking about growth paths and the review process is also well received.

Employers expect questions, and good ones show preparation.

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.