10 Terms All Account Managers Need To Know When Working With Software Engineers

Lex Meola
Lex MeolaWednesday, March 13, 2024
10 Terms All Account Managers Need To Know When Working With Software Engineers

I remember it like it was yesterday.

I was sitting in a conference room with four senior engineers. One of whom everyone at the company referred to as “Zucky,” akin to Mark Zuckerberg. The imposter syndrome wasn’t just in the room with me, it was breathing down my neck, constantly reminding me that I didn’t understand the context of the meeting and therefore, didn’t deserve to be there.

For those of us who are more business-focused, participating in a discussion that is overtly technical can feel painful. As the imposter syndrome creeps in, we feel uncomfortable and quite frankly, lost.

I’d love to go over 10 terms I got a hold of that have helped drive technical conversations and reduce the discomfort I experience when I lose the plot of a discussion.

Let’s break it down

Account managers serve as a crucial bridge between clients and internal teams, ensuring smooth communication and successful project outcomes. When collaborating with software engineers, having a solid understanding of technical terminology is essential for effective coordination and relationship-building.

In this blog post, we'll explore the top 10 terms every account manager should know when working with software engineers:

  1. Agile Methodology: Agile is a project management framework characterized by iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Understanding Agile principles helps account managers grasp project timelines, priorities, and the iterative nature of software development.
  2. User Story: A user story is a concise description of a software feature from an end-user perspective, typically written in non-technical language. Account managers should understand user stories to effectively communicate client needs and priorities to the engineering team.
  3. Backlog: The backlog is a prioritized list of features, enhancements, and fixes that need to be addressed in a software project. Account managers should be familiar with backlog management tools like Jira or Trello to track project progress and prioritize tasks effectively.
  4. API (Application Programming Interface): An API is a set of rules and protocols that allows different software applications to communicate with each other. Account managers should understand APIs to facilitate discussions around integrations, data exchange, and system interoperability.
  5. MVP (Minimum Viable Product): The MVP is the simplest version of a product that satisfies customer needs and allows for iterative development based on user feedback. Account managers should understand the concept of MVP to manage client expectations and prioritize features for early release.
  6. Deployment: Deployment refers to the process of releasing a software application or feature into a production environment for end-users to access. Account managers should understand deployment pipelines, version control systems, and release management practices to coordinate product releases effectively.
  7. Testing (Unit, Integration, Regression): Testing is a crucial aspect of software development to ensure product quality and reliability. Account managers should understand different types of testing, including unit testing (testing individual components), integration testing (testing interactions between components), and regression testing (ensuring new changes don't break existing functionality).
  8. Scalability: Scalability refers to a system's ability to handle increasing workload or user demand without sacrificing performance. Account managers should understand scalability considerations to anticipate future growth and ensure the software can accommodate evolving needs.
  9. DevOps: DevOps is a cultural and technical movement that emphasizes collaboration and automation between software development and IT operations teams. Account managers should understand DevOps principles to facilitate communication and collaboration between development and operations teams.
  10. SLA (Service Level Agreement): An SLA is a contractual agreement between a service provider and a client that defines the level of service expected, including metrics such as uptime, response time, and resolution time. Account managers should understand SLAs to manage client expectations and ensure service delivery meets agreed-upon standards.

I can’t stress it enough: Effective communication between account managers and software engineers is essential for successful project delivery.

By familiarizing themselves with these top 10 terms, account managers can enhance collaboration, streamline project management, and ultimately deliver better outcomes for clients and stakeholders.

Lex Meola is Echobind’s trusty account manager. Reach out to her at any time ( if you’re interested in working with us, or even grab 15 minutes on her SavvyCal.

Share this post


Related Posts:

Interested in working with us?

Give us some details about your project, and our team will be in touch with how we can help.

Get in Touch