22 Mar 2026
FlytBase Software Development Engineer (SDE) reviews
Be the first to recommend this company
Nitin Gupta
Not enough data to show CEO approval
20% positive business outlook
Reviews by job title
5 reviews
27 Feb 2025
FlytBase Response
1yWe acknowledge this review and the emotion behind it. While we disagree with the accusations and tone, it's worth clarifying a few principles we operate by—because they often get misunderstood in high-intensity environments.
FlytBase is a company built at the intersection of AI, autonomy, and real-world systems. That means we operate at a pace, standard, and level of ambition that’s not comfortable for everyone—and we don’t pretend otherwise.
We don’t run on hierarchy or micromanagement. We run on context, ownership, and clarity of purpose. Leaders don’t issue commands—they set direction, challenge assumptions, and expect teams to move fast with high autonomy. That may feel intense to some. To others, it feels like freedom.
We also don’t believe in guaranteed stability. We believe in alignment, performance, and accountability—across the board. If someone is not aligned with our mission, not delivering outcomes, or resisting the way we work, we act quickly. That’s not exploitation—it’s operational clarity.
As for our product, it speaks for itself: autonomous drone deployments running across industries and geographies, driven by customers who stay and scale with us.
Yes, we’ve made hard decisions. Yes, we’ve let go of people. But always with transparency, respect, and clarity—not with blame, not with games, and certainly not to "make money." We’re not optimizing for optics. We’re optimizing for momentum.
That doesn’t make us perfect. But it does make us deliberate.
3 Feb 2025
FlytBase Response
1yWe’ll admit—we chuckled at the pigeons analogy. Points for creativity.
Behind the humor, though, there are real concerns that we take seriously: network reliability, communication friction, and clarity around priorities. Let’s address each directly.
* On infrastructure:
We agree—IT downtime shouldn’t be part of the work experience. Over the past few months, we’ve significantly upgraded our internal tools and connectivity across the office. But if you faced consistent issues, that’s on us. We’re continuing to invest in stability and speed—because teams can’t move fast if their systems don’t.
* On communication and project clarity:
In a fast-evolving company building deep tech, ambiguity is inevitable—but it shouldn’t be perpetual. If you ever felt unclear about direction or scope, that’s a signal we didn’t provide enough context. We’ll own that—and continue to improve how we share roadmaps, goals, and tradeoffs across the org.
* On working hours and expectations:
We don’t measure performance in office hours, and we certainly don’t glorify long ones. What we do ask for is momentum, ownership, and availability during key collaborative windows. If that translated to a rigid 9-to-9 experience for you, then we failed to reinforce our principles in action—and that’s something we’re actively working to fix.
Thanks for surfacing these challenges. We appreciate the wit—and the honesty. Even tough feedback helps us improve. (And yes, we’re leaving the door open for pigeons… just in case.)