Solutions Engineer
Job description
About the role
The Solutions Engineer translates complex operational problems into validated, scalable solutions for strategic enterprise deals. This role serves as the primary technical authority during pre-sales activities, proving feasibility in customer environments and removing technical objections.
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
Relay's platform capabilities are shaped into robust, scalable architectures that address specific customer needs.
You build and run proof-of-concept deployments that validate technical requirements against real-world conditions on the shop floor or in logistics facilities.
When strategic deals face technical scrutiny, you own the narrative and make the case undeniable through security responses, RFI and RFP handling, and IT architecture reviews.
Post-sales teams receive clear handovers and technical context so they can execute as envisioned, while you serve as an escalation point for original design questions.
Requirements
You bring 3+ years of customer-facing technical roles, such as Solutions Engineer, Sales Engineer, or solutions architecture, where you owned technical relationships while delivering software, data, or systems-integration projects. You translate complex business problems into credible technical solutions for both technical and business audiences.
Hands-on experience building compelling demonstrations and working proof-of-concept deployments is essential. You have led enterprise technical diligence, including RFPs, security reviews, and IT architecture evaluations.
You read and work with APIs and integrations and build prototypes to prove concepts. You communicate with precision while moving fluidly between deep technical detail and executive-level business narrative. You operate comfortably in fast-moving, ambiguous territory. A Bachelor's degree, or equivalent practical experience, is required; technical degrees are preferred but not mandatory.
Practical notes
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
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
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.
About the company
Relay is building the web3 messenger. We are looking for talented and motivated front-end engineers of all experience levels. Relay engineers thrive in a high-growth, high-velocity environment where success depends on the highest levels of communication, code quality, and pragmatism.