Technical Solutions Consultant
Job description
Technical Solutions Consultant at Candid Health.
About the role
This role partners with Sales to solve revenue cycle challenges for large healthcare customers and to build the foundational tools that enable the Sales team to succeed.
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
Engaging demonstrations communicate the measurable impact of Candid's solutions to prospective customers.
Value analyses convert complex customer requirements into clear insights about what the product can deliver.
Sales teams gain a deep understanding of the value proposition so they can sell more effectively and with confidence.
Foundational processes, tools, and knowledge are created to empower the entire Sales organization.
Requirements
The posting states a bachelor's degree requirement. You bring 3+ years of experience from Solutions Consulting or Pre-Sales Engineering with complex, customizable implementations.
Prior experience in Digital Healthcare or Revenue Cycle Management within healthcare is preferred.
You translate technical capabilities into tangible business outcomes driven by clear business drivers.
You have a record of partnering with Sales teams to articulate value and win customer acquisition.
You analyze complex customer challenges and design creative, value-driven solutions.
You engage in high-level discussions using strong communication and presentation skills.
You approach the role with a proactive, results-oriented mindset focused on customer goals and partner enablement.
You travel to prepare for and visit onsites, up to approximately 20% of your time.
Nice to have
Experience with healthcare technology, revenue cycle management, and relevant key performance indicators.
Practical notes
This role is based in New York City and requires a degree. The position is full-time with an estimated total compensation range of $175,000 to $226,000 OTE. 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
Technical consulting roles of this type combine customer discovery with solution design. Success depends on clear communication and structured problem solving. Common tools include sales engagement platforms, demo environments, and collaboration software. Roles with flat hierarchies often emphasize ownership and cross-team influence.
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.