---
title: "Discussion on \"The one about my experience working for an American fintech (year 2)\" | Hashnode"
description: "Discussion on \"The one about my experience working for an American fintech (year 2)\". Reflecting on two years at an American fintech: microfrontend migrations, team reassignments, handling loss, and company-wide AI tools."
url: "https://hashnode.com/posts/the-one-about-my-experience-working-for-an-american-fintech-year-2/6acbdd5d660e44d08bd3c656"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The one about my experience working for an American fintech (year 2)](https://davidmontesdeoca.dev/the-one-about-my-experience-working-for-an-american-fintech-year-2?utm_source=hashnode&utm_medium=feed)

Reflecting on two years at an American fintech: microfrontend migrations, team reassignments, handling loss, and company-wide AI tools.

Oct 11 · 15 min read · davidmontesdeoca.dev  
Read the article

-   [#fintech](https://hashnode.com/tag/fintech)
-   [#fintech-software-development](https://hashnode.com/tag/fintech-software-development)
-   [#ai-adoption](https://hashnode.com/tag/ai-adoption)
-   [#software-development](https://hashnode.com/tag/software-development)
-   [#sinatrarb](https://hashnode.com/tag/sinatrarb)
-   [#htmx](https://hashnode.com/tag/htmx)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[David Montesdeoca](https://hashnode.com/@backpackerhh)

@backpackerhh · Gran Canaria, Canary Islands

  
[View profile](https://hashnode.com/@backpackerhh)

Software Engineer

I love learning new stuff, especially when it comes to building software. I'm really interested in software architecture, clean code, testing and best practices.

## Responses 2

Markdown supported · ⌘↵ to post

[David Montesdeoca](https://hashnode.com/@backpackerhh)

[Oct 13](https://hashnode.com/posts/the-one-about-my-experience-working-for-an-american-fintech-year-2/6acbdd5d660e44d08bd3c656/comment/6ace80cdf4b66fc21a8181da)

Hey Ameen! Thanks for reading and for the great question.

The way I see it, adopting AI successfully comes down to adapting how we learn and how we approach daily work. When using AI tools regularly, your role naturally shifts — you end up reviewing far more code than you actually write.

To maintain high code quality and maintainability, teams need strong discipline: clear coding guidelines, rigorous MR reviews, and a continuous push to refine the codebase. Because AI agents rely heavily on existing code as context, maintaining a clean repository ensures the AI generates far better results.

As for continuous learning, the key is using AI as a partner rather than a shortcut, taking the time to truly understand why the generated code works before merging it.

At some point I would like to write about how I use the AI tools in my daily work.

Best regards, David

[Ameen Jolly](https://hashnode.com/@ameenjolly)

[Oct 11](https://hashnode.com/posts/the-one-about-my-experience-working-for-an-american-fintech-year-2/6acbdd5d660e44d08bd3c656/comment/6acc0a98b5c27757a833bb55)

Quite an insightful read, thank you David! Given your experience, I would wonder, how can engineering teams adopt AI tools effectively while ensuring code quality, maintainability, and continuous learning?
