Solutions Engineer

About the role

This role is a strong fit for data engineers with 2 to 4 years of experience who want to take their technical depth into a customer-facing role. If you have spent the last few years building pipelines, working with cloud warehouses, and solving real data problems, but you are starting to wonder what comes next, this is worth a closer look.

In this role, you will work directly with Heads of Data, Data Engineering Managers, and CTOs at companies evaluating Hevo across the US, Europe, Southeast Asia, and ANZ. You will help them design the right data architecture, walk them through trade-offs, and earn the technical trust that turns an evaluation into a partnership. You will do this independently, often as the sole technical person on the call. There is no senior SE in the background. You need to walk into a Zoom with a VP of Data Engineering at a US fintech or a Head of Analytics at a European e-commerce company, earn their technical respect in the first five minutes, and hold it for the rest of the engagement.

The technical depth you have built does not go away. It gets applied to a much wider set of problems, a much larger audience, and a global stage.

Hevo runs real-time data pipelines from 150+ sources into modern warehouses for over 1,000 companies, including DoorDash and Shopify. You will be the person customers rely on to make sure Hevo fits their stack, their scale, and their goals.

Why this role is worth considering

A. You move from building pipelines to shaping data strategy

In your current role, you build what is specified. In this role, you sit with senior data leaders and help them decide what to build across the modern data stack. Your existing experience in CDC, warehouse design, and pipeline reliability becomes the foundation for higher-leverage work.

B. You get global exposure that is hard to find elsewhere

You will be in regular technical conversations with Heads of Data and CTOs at fast-growing companies across North America, Europe, and beyond. You will run discovery, defend architecture choices, and present in rooms where decisions get made. This is rare exposure for someone at the 2 to 4 year mark, and almost unheard of from Bangalore.

C. Your technical depth stays central

This is not a pivot away from engineering. Everything you know about Postgres, CDC, Kafka, dbt, Snowflake, and pipeline reliability gets used every day. The difference is that your technical opinion shapes the customer’s architecture instead of staying inside a Jira ticket.

D. The career path is real

Strong performers in this role grow into senior individual contributor roles, lead the function, or move into product, customer success leadership, or founding-engineer roles at their next company. The optionality this role builds is significant.