How Sherif Amer went from electronics engineer to employee #1 at Indemni

Before he ever wrote a line of code for a startup, Sherif Amer was designing embedded systems and verifying mixed-signal chips at Infineon. Then an unexpected layoff changed his trajectory. Rather than jumping back into semiconductors, he spent two and a half years traveling the world, teaching himself software engineering, and building his own product — a project called Roamies. That winding path eventually brought him to Indemni (W24), a San Francisco startup that combines driver verification, carrier intelligence, and real-time shipment monitoring to help freight brokers detect fraud and move loads with confidence. Sherif was employee #1.

From hardware to founding engineer

Sherif's official title is Founding Engineer, but he describes himself as "a product-minded engineer who happens to write a lot of code." His background in electronics gave him a deep instinct for understanding how things work from the ground up — an instinct he now applies to software architecture, product design, and everything in between.

When he evaluated Indemni before saying yes, he wasn't chasing a title. "I cared less about titles and more about the people I'd work with, the problems we'd solve, and how much ownership I'd have," he says. He wanted founders who welcomed technical disagreements and trusted engineers to contribute beyond writing code. He found that.

Building the infrastructure from scratch

Sherif designed and built much of Indemni's asynchronous processing and notification infrastructure — Redis Streams consumers, message recovery, concurrency controls, rate limiting, and delivery. He's also built out the verification infrastructure, connecting external identity providers, orchestrating multi-step workflows, and designing how the company processes and analyzes verification results.

"Rather than automatically reaching for a managed cloud service for every problem, I got to evaluate the trade-offs and build solutions that made sense for our scale and needs," he says. The range is wide: one day it's distributed systems and reliability, the next it's database models, analytics dashboards, or a customer-facing feature. "And when something breaks, there's no mysterious infrastructure team to hand it off to. That's usually my problem too."

One project he's especially proud of: building a job scheduler by extending Indemni's existing Redis Streams infrastructure. He used an AI coding agent as a collaborator, providing architectural context and constraints while delegating implementation. What made it satisfying wasn't that AI wrote the code — it was that he could approach the problem as an architect, choosing the technologies, defining the trade-offs, and reviewing the result.

Autonomy, accountability, and a lot of rope

"A lot of rope!" is how Sherif describes the working relationship with Indemni's founders. He's not expected to just agree with an idea and go implement it. "We challenge each other, debate approaches, and sometimes disagree quite strongly, but there's always room for an honest conversation." Those conversations aren't limited to engineering — he can question product decisions, suggest new directions, or flag opportunities the team hasn't considered.

As Indemni has grown and more engineers have joined, Sherif's role has shifted. He now spends more time on architecture, establishing engineering guidelines and code quality standards, and mentoring newer team members. "One of the most rewarding changes has been seeing those engineers become increasingly independent," he says. "They now make solid technical decisions and ship quality work without needing my input at every step."

What surprised him most

Coming from a large semiconductor company with layers of review and clearly defined responsibilities, Sherif was struck by how much startup life revolves around making decisions with incomplete information. "You have to be comfortable making reasonable decisions, moving quickly, and adjusting as you learn more," he says. "I've come to appreciate that a lot."

He was also surprised by how much trust the founders placed in him — not just over engineering, but over product direction and company decisions. "I expected to have ownership as a founding engineer, but I didn't necessarily expect to have such a strong voice in decisions beyond engineering."

Who would thrive here

Sherif's advice for anyone considering an early-stage role is direct: be honest with yourself about what you want. The work is rewarding, but only if you're comfortable with uncertainty and figuring things out without a guide.

• You won't always have perfect requirements or established processes.
• You might design a system in the morning, implement it in the afternoon, and troubleshoot it in production the next day.
• You'll get exposure to parts of engineering and business that might take years to experience at a larger company.

If that sounds like the job you've been looking for, Indemni is hiring.