Dema
Careers/Manuel Tejeda
Manuel Tejeda

Manuel Tejeda

Senior Software Engineer

Education

Master of Science in Web Technologies, University of Valencia

Previous roles

Senior Software Engineer at Anyfin and Epidemic Sound

From

Santo Domingo, Dominican Republic

Started at Dema

2025

There's a roadmap, but it's more of a direction than a script.

What made you choose Dema over other places you were considering?

It came down to how much ownership I wanted versus how much I had. I'd been doing solid work, but a lot of the why behind decisions happened without me. What drew me to Dema was that here I'm actually in that conversation, not just building what I'm told but weighing in on what's worth building at all. That pull toward more ownership is what made the decision for me.

What's different about the engineering culture here compared to places you've worked before?

Less process, more trust. I don't need three approvals to make a call, and stuff ships fast because there's not much bureaucracy in the way. The bigger shift for me is being close to the product and business side of things instead of just getting handed a spec.

You've mainly worked at startups. What do you appreciate most about being early at a company?

You see what you built land in front of actual users almost immediately, with no long chain of approvals between writing the code and someone using it. And you end up doing a lot more than your job title suggests.

What's a project or moment that made you think "this is why I'm here"?

Nano apps. We shipped it in about two to three weeks: an AI tool that lets users generate their own apps inside Dema, connected to their real data and integrations. We ran an AI day where customers tried it for the first time, and watching what they actually built with it, and how fast they figured out ways to push past what we'd designed it for, was the best kind of validation. That's the whole reason I like building at this stage: you make something, and two weeks later real people are already bending it in directions you didn't plan for.

How much freedom do you get to shape what you build, versus executing a fixed roadmap?

There's a roadmap, but it's more of a direction than a script. I'm expected to push back if I think there's a better way to do something, and that's taken seriously. It feels less like being handed a list of tasks and more like being trusted to help figure out the right list in the first place.

What would you tell someone on the fence about joining the engineering team?

If you want your name actually attached to outcomes and not just commits, you'll like it here. If you need a lot of structure and clear guardrails at every step, it might feel like too much ambiguity. For me that ambiguity is the interesting part.

Outside of work, what's something you love doing?

I'm a bit obsessive about pour-over coffee, still tweaking grind size, ratios, and water temperature trying to get it right. Outside of that I love to run, travel, try new restaurants, and cook a lot at home.

Also on the team

Want to build with people like this?