Solutions Engineer
Job description
About the role
Solutions Engineers connect Finch solutions to customer business problems during sales discussions. This role translates product capabilities into customer value through direct sales engagement. You will own the technical narrative that turns abstract product features into concrete business outcomes for specific use cases. The position requires you to act as a bridge between customer language and engineering reality during discovery conversations. You translate ambiguous customer needs into precise technical requirements that the product team can execute. Solutions Engineers define the technical boundaries within which sales promises can be safely made and delivered. You ensure that every demonstration aligns with both customer expectations and engineering reality.
Key facts
What you'll do
Conduct discovery sessions to uncover how Finch capabilities solve specific workflow bottlenecks for target accounts. Translate complex product roadmaps into simple narratives that sales teams can use to win new opportunities. Provide technical context that allows account executives to position Finch as the only solution that fits the customer architecture. Build and iteratively refine demo environments that mirror the customer's real-world constraints and data structures. Collaborate with product managers to identify which features should be highlighted for different industry verticals. Support the creation of technical artifacts such as integration diagrams, data flow models, and security summaries for procurement reviews. Respond to security and compliance questionnaires by extracting relevant product capabilities and limitations accurately. Partner with marketing to develop reference stories that illustrate successful deployment patterns without exposing confidential information. Maintain a living understanding of competitive positioning so that counter questions from skeptical buyers can be answered with precision. Enable the sales organization by turning abstract product roadmaps into concrete timelines and deliverable commitments.
Requirements
You must have a bachelor's degree in computer science, engineering, or a related technical field. Candidates must demonstrate strong problem solving skills through past work or academic projects that show measurable outcomes. You should bring at least three years of professional software engineering experience in a production environment. Solid understanding of data structures, algorithms, and system design is required for navigating technical tradeoffs. Experience with cloud platforms, API design, and distributed systems is necessary to discuss architecture implications. You must be comfortable reading and interpreting technical documentation to quickly learn new products and constraints. Strong written and verbal communication skills are non negotiable for explaining technical constraints to non technical stakeholders. You must pass standard employment verification and, if required, background checks as part of the hiring process.
Nice to have
Experience with sales engineering or solutions engineering roles in enterprise software companies. Familiarity with workflow automation, integration platforms, or data movement tools. Previous exposure to security, compliance, or privacy frameworks relevant to enterprise customers.
Practical notes
This is a full time position based in San Francisco, New York City. Security and privacy practices guide every interaction with customer data and workflow details. 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
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.
About the company
We are on a mission to revolutionize employment by building the infrastructure that powers every facet of work. To do this, we are looking for individuals who think about problems holistically and in-depth, who are relentlessly curious, self-starters, and determined to drive ideas from inception through to completion.