Meet the Expert: Carla Nguyen, Engineering Manager at Credify Loans

Carla Nguyen has led software teams in personal-loans fintech for over seven years, with a focus on scaling applications and teams simultaneously. She recently guided Credify Loans through doubling their engineering staff while maintaining velocity and quality. We asked her about the cultural adaptation techniques mid-level engineers should use to keep their projects and teams humming at scale.

Why Does Culture Matter When Your Team and Codebase Scale?

Q: Carla, when a team grows, what cultural cracks start to show that engineers might not expect?

A: Imagine you’re baking a cake meant for 5 people, and now you need to feed 50. The recipe—the team’s culture—was fine at the smaller scale. But suddenly, the oven (team dynamics, communication channels, shared values) can’t handle the volume. That’s where things break.

For example, at Credify Loans, when we doubled the squad size from 10 to 20 engineers in 18 months, informal verbal communication stopped working. We had a 25% drop in sprint velocity initially because folks were stepping on each other’s toes, and duplicated features cropped up in the personal-loans underwriting pipeline.

Culture isn’t just “feel-good.” It’s the invisible glue that holds processes, priorities, and people together as complexity grows.

How Should Mid-Level Engineers Think About Cultural Adaptation?

Q: What practical mindset or approach should a mid-level software engineer adopt regarding culture as scaling pressures mount?

A: Start thinking of culture as an evolving set of operating instructions—not static company slogans. For example, if the team originally said, “We move fast,” scaling from 5 to 50 engineers means you need to define what “fast” means precisely. Does it mean “ship features daily”? Or “deploy every week, but with zero regressions”?

At my last company, we introduced the metaphor of “flight instruments.” Pilots can’t just rely on gut feeling when flying bigger planes or longer routes. Similarly, your cultural cues need to become explicit, documented, and measurable.

Here’s a quick analogy: Suppose your personal-loans team culture was once like a startup garage band jamming together. Scaling demands shifting to a professional orchestra with sheet music—everyone needs to read from the same cultural score.

What Are the Hardest Parts of Scaling Culture in Personal-Loans Tech Teams?

Q: Can you share some less obvious challenges you’ve seen or experienced in banking-related software teams during growth?

A: The regulatory environment in banking amplifies the stakes. When a team scales, inconsistent interpretations of compliance requirements can sneak into culture.

Take data privacy rules like GDPR or the newer California Consumer Privacy Act. If teams aren’t aligned culturally on “security first,” you’ll get some engineers prioritizing speed at the cost of logging sensitive data. That results in audit failures and fines.

One mid-level engineer at Credify once accidentally exposed anonymized applicant data during a feature demo because their team hadn’t culturally prioritized peer code reviews focused on compliance.

So, culture must embed not just general “teamwork” but specific norms around compliance, risk, and customer trust. That’s a big adaptation from purely technical or performance goals.

What Cultural Adaptation Techniques Work Best When Automating at Scale?

Q: Automation is a buzzword, but how does automation intersect with culture when your team grows?

A: Automation doesn’t just replace manual steps; it changes how people work and communicate. The culture shifts from “I have full control” to “I trust the system.”

For example, when Credify Loans automated loan status updates across multiple platforms, engineers initially resisted. They feared automation would obscure accountability or create opaque “black boxes.” To adapt, leadership introduced a “shared ownership” culture where monitoring automated jobs became everyone’s responsibility, not just DevOps.

One useful technique was introducing blameless postmortems: when an automation pipeline failed, the team reviewed it openly without finger-pointing. This transparency conditioned the culture to accept automation failures as learning moments.

That’s powerful because a 2024 Forrester report found teams practicing blameless reviews fix production incidents 40% faster.

How Should Growing Teams Adjust Communication Norms for Diverse Cultural Backgrounds?

Q: In personal-loans companies, you often have global teams or diverse backgrounds. How does that impact cultural scaling?

A: Diversity is a huge advantage but requires deliberate cultural adaptation.

For instance, direct communication styles common in U.S. teams may clash with more indirect styles from colleagues in Asia or Latin America. Misunderstandings can slow down product delivery or cause friction.

At Credify, we introduced asynchronous communication norms and encouraged “explicit context-sharing” in tools like Jira and Slack, rather than relying on assumptions from tone or body language. We also used Zigpoll to regularly collect anonymous feedback on how communication norms felt to different groups.

A caveat: this approach won’t work if leadership doesn’t model patience and openness. Without top-down support, mid-level engineers can get stuck in conflicting expectations.

What Role Does Onboarding Play in Cultural Adaptation for Scaling Teams?

Q: Onboarding is often overlooked. How does it factor into culture adaptation while growing?

A: Onboarding is where culture is taught, not just implied.

For example, when personal-loans platform growth at Credify jumped 3x in a year, we revamped onboarding to include a “culture bootcamp” that explicitly covered compliance priorities, communication protocols, and shared engineering principles.

We used real-world case studies: like how a missed requirement in a loan eligibility checker caused a $500K revenue loss because the team didn’t flag it early enough.

Including those concrete stories helped new hires internalize cultural norms faster.

Onboarding is a frontline defense against culture dilution. If you don’t invest here, you risk “cultural drift” where new hires unknowingly build their own subcultures.

What Advice Would You Give to Mid-Level Software Engineers About Leading Cultural Change?

Q: Finally, what can mid-level engineers do personally to influence culture during scaling?

A: Don’t underestimate your sphere of influence. You don’t need to be a manager to become a culture catalyst.

Start small: champion code review consistency. Volunteer to facilitate blameless postmortems. Propose small experiments in team rituals (like daily stand-ups with a focused agenda).

One team at Credify improved their loan approval cycle by 18% within six months just by synchronizing their definition of “done” and instilling a culture that values cross-team feedback.

Also, use tools like Zigpoll or local retrospectives to surface cultural pain points—then push for solutions.

A warning: cultural change takes patience. It’s a marathon, not a sprint. You’ll hit resistance. But steady, visible improvements build momentum.

Summary Table: Techniques and When to Use Them

Carla’s insights show that as personal-loans companies grow, cultural adaptation needs an engineer’s problem-solving mindset: measure, experiment, iterate. The culture that carried your team to 10 engineers won’t get you to 100 without tuning.

Embrace culture as a living system—not just a buzzword—to keep your teams running efficiently, regulatory risks low, and your software delivering on customer trust well into 2026 and beyond.