GTM Engineer

About Sentrion

We’re building Sentrion to help teams find companies that need what they offer, and understand the problem before reaching out. A business might be opening a new office, rebuilding a department or changing the way it operates. Our work is to make sense of those changes in the context of what each customer sells. We want the team reaching out to know how it can help, and the company hearing from them to have a reason to listen.

About the role

A piece of account research is useful only if someone can do something with it. Your job is to understand how a customer’s team works and make Sentrion useful within that process. You’ll talk to the people using the information, agree on what needs to change and build the implementation with them.

The work might involve getting research into a CRM, preparing account information for a meeting or connecting our API to an existing workflow. You’ll help define a manageable scope and explain the choices along the way. After the initial setup, you’ll test it with the customer, resolve the problems that emerge and leave a system someone else can understand and maintain.

What you’ll do

• Start with the customer’s actual task. If they ask for another field in their CRM, find out who needs it and what decision it will support. Agree on the problem, the scope and how you’ll check the result together.
• Build integrations using APIs, webhooks, scripts and automation tools. Map fields carefully and handle authentication, rate limits, retries and updates without creating duplicate records.
• Configure and test workflows using representative customer examples. Check the quality of the information and what happens when inputs are missing, a service fails or someone changes the setup.
• Work with users through rollout. Explain how the workflow works, observe where they get stuck and make the changes needed for them to use it in their day-to-day work.
• Investigate delivery issues across Sentrion and connected systems. Reproduce the problem, communicate its impact and own the resolution rather than leaving the customer to coordinate the fix.
• Document the configuration, operating steps and known limitations. Bring recurring customer needs back to the product team, with examples that help us decide what belongs in the product.

What we’re looking for

• Experience building integrations or operational workflows that other people depend on. You can explain how information moves through the system and what happens when one part fails.
• Comfort writing and debugging code in a language such as Python or JavaScript. You can read API documentation, inspect requests and responses, and work with structured data.
• Familiarity with CRMs or related sales and marketing systems: records, custom fields, ownership, permissions and the practical consequences of changing live data.
• The ability to lead a technical conversation with a customer. You ask enough questions to understand the need, explain options plainly and agree on realistic boundaries for the work.
• Careful testing and troubleshooting habits. You check the result in the receiving system and make sure a workflow can be rerun, supported and handed over.

Useful, but not required

• Customer-facing implementation, solutions engineering or revenue operations work.
• SQL, data enrichment, or connecting several sources without losing track of record identity and data quality.
• LLM-based workflows where you had to check output quality and handle results that weren’t good enough to use.

Working at Sentrion

We want you to use your judgment about how best to solve a customer’s problem. Sometimes that means writing code; sometimes it means simplifying the process. Be prepared to explain your recommendation and change it when the evidence points somewhere else.

If an implementation goes wrong, make sure the customer and the team understand what happened and what you’ll do next. Follow through on the fix and the lessons from it. This role is based in New York with a hybrid setup.