A year ago I had never touched OpenSearch, never debugged a Lake Formation cross-account permission, never reconciled 23 GL accounts to penny-for-penny accuracy against an Oracle source of truth. Today I do these things as part of my work. The company that made that trajectory possible is Caylent, and this post is about why.

What Caylent does

Caylent is an AWS consulting company. Expert AWS practitioners who help clients build, migrate, and optimize their cloud infrastructure. The work spans data engineering, DevOps, cloud architecture, and AI. The company is fully remote and global.

What makes Caylent different is what happens to the people inside it.

The growth trajectory

My first project was an OpenSearch implementation for a hospitality tech company. I had never used OpenSearch. I learned it by building it: parent-child data models, denormalization strategies, semantic search. The project lasted about ten weeks and by the end I understood not just how OpenSearch works, but why you’d choose it over alternatives like ScyllaDB or DynamoDB for specific access patterns.

Then came a database migration with live cutover challenges, UTF encoding battles, and cost documentation that saved the client real money. Then a Kubernetes-based data platform. Then a QuickSight analytics layer with complex UNNEST queries and data lineage tracking.

Now I’m on the largest project of my career: migrating a bank’s legacy Oracle data warehouse to an Apache Iceberg data lake on AWS. The tech stack includes Lake Formation, Athena, Glue, Terraform, Argo Workflows on EKS, SCD2 transforms, and CDC ingestion. I’ve driven architectural decisions on data granularity, found and fixed a root cause that was creating a $50M balance sheet mismatch, and reconciled production data to zero variance across 23 accounts.

That’s one year. Not because I’m exceptional, but because the environment made this progression possible.

Real projects, real pressure, real learning

After a thorough onboarding and project preparation process, you’re working on real client infrastructure with real business impact. Not a training sandbox. Real systems, real stakes, real learning.

Every project brings technologies and domains that push you to grow. The answer is always the same: break it into smaller parts, collaborate with your team, study the documentation, and deliver. The challenge is the teacher. The team is the safety net.

The people

When I get stuck on a Lake Formation permission error, there’s a senior engineer who has debugged the same issue for three different clients. When I submit a PR, the code review is thorough and educational, not performative. When I propose an architectural approach, it gets evaluated on its reasoning, not my title.

My manager gives me space to learn at my own pace while pushing me to take on responsibility I wouldn’t volunteer for. My onboarding buddy made the first weeks human, not just technical. Teammates share knowledge freely because the culture rewards helping, not hoarding.

I once spent an evening before a Caylent city event researching every leader’s background, experience, and career path. Not because I had to. Because understanding the people who built the company made me feel connected to something larger than my current ticket.

Why consulting is underrated

Consulting gets a bad reputation. The criticism: you never go deep, you just skim from project to project.

My experience is the opposite. Each project is a forced deep dive into a domain, a stack, and a set of constraints you didn’t choose. In one year I’ve worked with OpenSearch, ScyllaDB, DynamoDB, Kubernetes, QuickSight, Apache Iceberg, Lake Formation, Argo Workflows, Terraform, and more. A product company might have given me one of those technologies. Consulting gave me all of them.

The variety compounds. You start seeing patterns across clients: the same Lake Formation mistakes, the same Terraform anti-patterns, the same communication failures between engineering and business. Those patterns become instincts. By your fifth project, you’re not just solving the current problem. You’re recognizing it.

And consulting teaches skills that product engineering often doesn’t: how to read a Statement of Work and understand what the client actually needs. How to communicate with non-technical stakeholders who care about numbers matching, not about your elegant implementation. How to scope work honestly. How to learn a new domain in days, not months. How to deliver value under constraints you didn’t set.

What Caylent invests in its engineers

Caylent gives its engineers a monthly budget for AI tools. This website you’re reading, the interactive Mexico cartogram, the writings: they were built using that benefit. The company funds its engineers’ ability to build, learn, and create outside of client work. That’s not a perk on a careers page. It’s a direct investment in the kind of engineer who builds in public.

There’s a certification bounty program that pays you for passing AWS certifications. Training courses across the technical and consulting domains. Slack channels for every guild (data engineering, GenAI, DevOps, cloud architecture) where people share links, ask questions, and debate approaches daily. Regular all-hands meetings where leadership is transparent about the company’s direction, wins, and challenges.

A consulting fundamentals course taught me things about professional services that no technical bootcamp covers: the difference between staff augmentation and outcome-based engagements, how to frame technical work as business value, how to manage stakeholder expectations, and why the phrase “delivery-led growth” matters. Building great infrastructure is necessary. Making the client feel confident that you’re building great infrastructure is equally necessary.

What this adds up to

One year at Caylent taught me more about engineering, consulting, communication, and professional growth than any course, certification, or tutorial ever could. Not because the company has a magic formula, but because it creates the conditions for growth: real projects with real stakes, talented teammates who share freely, a culture that values learning over performing, and tangible investment in its people’s development.

I don’t take any of this for granted.

If you’re a data engineer or cloud engineer looking for a place that will push you, support you, and trust you with real work from day one: Caylent is hiring.

And to my team, my manager, and everyone at Caylent who helped me get here: thank you. Everything I’ve built, on this website and at work, stands on the foundation you helped me build.