Ask Me Anything: Kevin Bravo 🤺

9 min read

Hello tech recruiter or technical person! 👏 Thanks for stoping by and taking the time to read my profile.

Getting to know a candidate is hard, and more when there is little time, too much to ask and nervousness attacks. So I wrote this AMA where I’m interviewing myself so you can know me better 🤠 in just a couple of minutes.

Recruiter TL;DR

Software Engineer with 4+ years of experience building platforms, internal systems, and infrastructure across startups, government projects, and non-profits. Strong focus on backend architecture, AI tooling, distributed systems, and high-ownership engineering roles.

Built and maintained production systems for the U.S. Department of State’s Venezuela Affairs Unit, Free2Z, and AVAA. Outside of work, I’ve spent years volunteering in education, tech and community initiatives, organizing hackathons and tech events, mentoring students, and helping build programs focused on entrepreneurship, leadership, and technology access.

🤷‍♀️ Overall

What’s your tech experience like?

I’m a Software Engineer with 4+ years of experience building web platforms, internal tools, and data systems. I’ve worked in startups, government projects, and non-profits, leading technical architecture, full-stack development, and product design.

Most of my experience has been building systems from the ground up, where I defined the architecture, modeled the data, and connected services. I’ve worked on frontend and backend projects, but I’m especially interested in backend architecture, cloud, infrastructure, AI tools, data distributed systems, and systems that other people can rely on.

I like working on systems that matter and solving hard technical problems that force you to understand what is really happening. I like taking full ownership of the outcome and being trusted with difficult, ambiguous challenges. I do my best work when the systems, architecture, and foundations still need to be designed, built, and maintained.

What kind of problems do you usually/like solve?

I enjoy solving problems where the path to the solution is not obvious. The kind of work I enjoy is technical, foundational, and requires thinking deeply about systems, architecture, and long-term scalability.

Most of the projects I’ve worked on started as rough ideas, disconnected workflows, or operational bottlenecks. My role is usually turning that into scalable, production-ready systems through architecture, backend engineering, and infrastructure design.

I’m especially interested in distributed systems, cloud architecture, AI tooling, developer platforms, and the systems that power applications behind the scenes. What motivates me most is building resilient systems that reduce operational friction, create leverage for teams, and continue delivering value long after the first version ships.

What I’m strongest at

I’m strongest in projects that require a high level of ownership, technical judgment, and the ability to operate through ambiguity. I work best when the direction is still being defined and the challenge is figuring out how all the pieces should come together into a coherent system.

Most of my experience has involved building systems from the ground up and turning unclear or messy problems into software that teams can actually rely on. That includes architecture decisions, backend systems, service integrations, internal tooling, and workflows that need to remain practical and maintainable as the system grows.

I enjoy understanding the deeper constraints behind a problem, identifying what actually matters technically, and building solutions that balance scalability, maintainability, and speed without overengineering the system.

Roles I’m a good fit for

  • Backend Engineer
  • Full-Stack Engineer
  • Infrastructure-minded Product Engineer
  • AI Tools / Agentic Systems Engineer
  • Platform / Internal Tools Engineer
  • Technical Lead / Founding Engineer style roles

Volunteer?

Yes, I’ve been involved in volunteer and education-focused initiatives for more than 8 years.

Right now I’m the Vice President of JA Venezuela Alumni, where I help grow the community, organize initiatives, build partnerships, and create spaces around entrepreneurship, technology, and professional development for young people.

I’m also part of the Education Committee at AVAA, supporting Programa Excelencia from the technical and operational side by maintaining internal systems, improving workflows, and helping the team make better decisions through more reliable processes and data.

Over the years, I’ve also collaborated on different education and tech initiatives, including mentoring students at Technovation Girls, organizing hackathons, supporting student and entrepreneurship events, and participating in community projects focused on education, leadership, and technology access.

What are your main professional and academic goals?

Professionally, I want to keep working on challenging technical projects where I can design systems from the ground up, solve complex engineering problems, and build technology that has meaningful long-term impact. I’m particularly interested in infrastructure, backend systems, AI tooling, and large-scale technical architectures.

Academically, I’m pursuing a Master of Public Administration at IESA because I believe technology should be built with a stronger understanding of society, institutions, and long-term impact. I’m interested in helping bridge the gap between technology, governance, and the people affected by the systems we build.

After finishing this degree, I’d like to continue deeper into the technical and research side through a master’s in Computer Science or Mathematics, and eventually continue toward PhD-level work focused on systems, computation, AI, and large-scale infrastructure.

Do you prefer frontend, backend, or full-stack?

I like working where the important technical decisions are happening. I can work across the stack, but I usually think in terms of systems, architecture, and long-term maintainability more than rigid roles or labels.

I enjoy moving across different parts of a product depending on where the problem is, whether that involves frontend experiences, backend systems, infrastructure, integrations, or internal tooling.

I also like being close to the product and understanding why something is being built in the first place. For me, good engineering is not only about building systems, but about connecting technical decisions with real operational, organizational, and human needs.

Best professional projects

Free2Z platform migration

I directed the technical migration and architecture redesign of a web platform, moving the frontend from React to SvelteKit to improve performance and code maintainability. The work included live video integration with Dyte, Svelte stores, Tailwind CSS, SSR optimization, backend API connections, and a custom CMS suite with a Markdown editor and blog engine.

Billingua Talent

Billingua Talent is a professional networking platform commissioned by the U.S. Department of State’s Venezuela Affairs Unit. This is a platform built to connect highly skilled Venezuelan professionals with strong English proficiency to high-paying national job opportunities. As the sole engineer on the project, I designed and built the platform architecture, data model, and core product flows, then deployed and maintained the system in production.

PES - Participant Evaluation System

The platform I built for AVAA to manage ProExcelencia with live data instead of scattered spreadsheets. It became the source of truth for scholar records, activities, volunteer hours, attendance, and reports across three national chapters.

What AI tools, models, and workflows are you currently using?

I actively use AI models and coding tools as part of my daily engineering workflow to speed up research, prototyping, debugging, system design, and development. They’ve become an important part of how I explore, validate, and iterate while building.

The models I use the most right now are:

  • ChatGPT 5.5 for deep technical reasoning, architecture discussions, and coding.
  • Gemini 3.1 Pro / Flash and Claude 4.7 for frontend work, UI exploration, and product-oriented tasks.
  • Mimo v2.5 Pro, Kimi K2.6, Composer 2.5, and newer open-source models like DeepSeek when I want to experiment, compare behaviors, and test different workflows.

For coding harnesses and tools, I’m currently using T3Code, Pi, and OpenCode. I also use Cursor and Zed from time to time, depending on the project and the workflow I want to test.

I also have a Hermes agent running 24/7 on a VPS, which works as a general personal assistant and helps me keep track of tasks, ideas, research, and my master’s work.

What other technologies do you find interesting?

I’m interested in AI, maths, zero-knowledge proof, distributed systems, cybersecurity, cloud infrastructure, embedded systems, and developer tools. I also care about how technology impacts institutions, organizations, and society over time.

💃 What would you ask & seek at your next company?

I’m looking for teams where ownership, thoughtful engineering, and meaningful work are valued. I enjoy environments where people care about what they build, think carefully about technical decisions, and take pride in creating systems that last.

I’m particularly interested in places working on difficult technical challenges, especially around infrastructure, backend systems, AI, developer tooling, or complex operational platforms. I like being involved when core decisions still need to be made and there’s room to shape how the product and the systems evolve over time.

I also value collaborative teams with strong technical curiosity, open discussions, and a genuine interest in improving both the product and the way the team works.

If we remove money off the table, what would you say is important for your next gig?

In order of importance:

  1. Ownership: I like environments where people trust you with meaningful responsibility and expect you to drive things forward independently.
  2. Autonomy and flexibility: I value teams that optimize for outcomes, trust, and good judgment rather than rigid schedules, unnecessary oversight, or performative productivity.
  3. Interesting technical problems: I enjoy complex engineering work, especially when there’s still space to shape the architecture, systems, and technical direction.
  4. Smart and curious people: I want to work with people who care about learning, questioning assumptions, and improving how things are built.
  5. Mission and long-term impact: I care about building things that are genuinely useful and that improve how people, organizations, or systems operate over time.
  6. Strong engineering culture: Good technical discussions, thoughtful decision-making, and attention to quality matter a lot to me.

How do you keep yourself up to date?

It’s a bit of mix & match:

  • Technical creators and conversations. I watch Theo, ThePrimeagen, and LowSpec on podcasts, Twitch, and YouTube.
  • Twitter/X. I spend some time there to hang out, follow interesting people, and stay close to what builders are discussing.
  • Paid learning. I maintain paid subscriptions to Platzi and Coursera, and I take courses that interest me from time to time.
  • Docs, articles, and building. I like to read technical and long-form posts. I also like to learn by building, so I often explore new technologies through side projects and experimentation.

💭 Contact Details