Full Stack Engineer

About the company:

Our client is a technology company transforming traditional consumer research through AI and data-driven insights. Its platform helps businesses quickly understand consumer behavior, market trends, competitive landscapes, and emerging opportunities using billions of real-world consumer signals.

By delivering data-backed research and strategic recommendations within minutes, the company enables organizations to make faster, smarter, and more informed decisions. Its solutions combine AI, consumer intelligence, and data analytics to provide actionable insights while reducing the time and effort involved in traditional market research.

About the role:

We‘re hiring a Software Engineer who can pick up a ticket and close it. Not someone who needs hand-holding through scope or technology choices– someone who reads the requirement, figures out the right approach, and ships something they‘re proud of.

What you‘ll actually do:

• Own tickets end-to-end: understand the problem, make the call, ship the feature, handle the edge cases
• Build across the stack– frontend, backend, or both depending on where you‘re strongest
• Work with TypeScript, ReactJS/NextJS on the frontend and Python/Go on the backend
• Design and work with SQL and NoSQL databases as part of feature development
• Collaborate with product and design to implement experiences that actually feel good to use
• Debug, optimize, and improve systems that are already in production - Learn fast– the stack will evolve and you‘re expected to evolve with it

Who we think this is for:

3 to 6 years of engineering experience. Startup experience is preferred– not because corporates are bad, but because you already know what it means to ship without a safety net.

You probably:

• Have closed real features in production, not just academic or tutorial projects
• Specialize in either frontend or backend but can move across the stack when needed
• Are comfortable in Python or Go on the backend, and TypeScript with ReactJS/NextJS on the frontend
• Know your way around cloud environments– AWS or GCP
• Understand databases well enough to make sensible design decisions, SQL and NoSQL
• Have at least two projects you‘d genuinely put in front of someone and say: I built this, here‘s why it‘s good
• Learn new tools by using them, not by waiting until you feel ready

This role is probably not for you if:

• You need a detailed spec before you can start
• Your best work lives in a private repo no one has seen
• You‘re looking for a large team with defined lanes– here, you own what you pick up