Senior Solutions Engineer, Risk Labs

• Strong technical background with hands-on experience in production codebases
• Experience supporting or building integrations (APIs, SDKs, protocols, infra)
• Comfortable debugging unfamiliar systems with limited documentation
• Ability to improve systems and workflows — not just execute tasks
• Strong communication skills (technical + cross-functional)
• High ownership and accountability
• You enjoy being the person who figures things out and makes things happen
• You care deeply about developer experience and real‑world usability
• You’re pragmatic and systems-oriented
• You leave processes better than you found them
• You like owning problems end‑to‑end and leaving systems better than you found them
• Studies have shown that women and people of colour are less likely to apply to jobs unless they meet every single qualification
• Risk Labs, the employing entity, is an equal opportunity employer and is dedicated to diverse, inclusive, and authentic workplaces. So, if you’re excited about this role but your past experience doesn’t perfectly align- we encourage you to apply anyways
• We value you taking the chance. Risk labs will not discriminate on the basis of race, religion, colour, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status

Desirable

• Expand the adoption of Across by successfully integrating partners, unblocking technical challenges, designing high‑impact solutions, and acting as a trusted technical partner from first conversation through post‑integration
• This role sits at the intersection of engineering, product, and partnerships
• Deeply technical, highly collaborative, creative, and strongly execution‑oriented
• This role is the only senior solutions engineering role on the sales team, so there is high expectations on senior and agency; while also a lot of room for creating automation or workflows that work for you to be successful
• This role exists to own and scale the integrator experience end-to-end, reducing friction, designing better systems, and ensuring integrations move from first call to production smoothly and predictably
• 1. Integration Execution & Partner Enablement (Core Focus)
• You will act as the primary technical partner for integrators
• Support architecture design and implementation decisions
• Debug across partner and protocol codebases
• Unblock testing, deployment, and production issues
• Identify recurring blockers and eliminate root causes
• Turn bespoke partner solutions into reusable templates and playbooks
• This is hands-on work. You should be comfortable reading and writing production-level code
• 2. Support Systems & Scale
• Across cannot scale if support scales linearly
• You will:
• Design workflows that reduce manual debugging
• Introduce automation where possible
• Improve support infrastructure (ticketing, triage, internal tooling)
• Convert repeated questions into documentation, tooling, or self-serve flows
• Increase velocity for Product, Engineering, and GTM
• Repeated work should become systems. Systems should reduce friction for everyone
• 3. Technical Signal & Commercial Awareness
• This role sits at the intersection of product, engineering, and partnerships
• Surface structured product feedback from integrators
• Identify expansion opportunities with growing partners
• Help articulate technical value in conversations with decision-makers
• Ensure high-leverage partners receive proactive support
• This is not a “salesy” role but commercial awareness matters
• 4. Developer Experience Improvements
• As Across leans further into its infrastructure narrative:
• Improve documentation and integration flows
• Publish example implementations and reference repos
• Increase discoverability within technical audiences
• Help ensure Across is intuitive and production-ready
• You build before you broadcast
• What Success Looks Like
• Integrations ship faster with fewer surprises
• Support becomes more proactive than reactive
• Repeated issues turn into automation or tooling
• Engineering receives clean, structured feedback
• Integrators feel supported and continue building
• Across becomes easier to integrate and scale