Remote Sales Roles Compared: SDR, AE, CSM and Sales Engineer

If you are scrolling through remote sales listings and can't tell an SDR role from an account executive or customer success role, the short answer is that they sit at different points of the same customer journey. SDRs and BDRs start conversations, account executives turn them into signed deals, account managers and customer success managers keep and grow existing customers, and sales engineers make the technical case. Below you'll find what each role does day to day, how success is usually judged, what an applicant can show as evidence, and how working remotely changes the job.

How do the sales roles fit together?

Think of a business-to-business sale as a relay. One person finds and qualifies interest, another runs the evaluation and negotiation, a technical specialist answers the hard product questions, and someone else looks after the customer once the contract is signed. In a small startup one person may do all of it; in a larger company each leg is a separate job with its own targets.

The US Bureau of Labor Statistics (BLS) describes this division in its profile of wholesale and manufacturing sales representatives: representatives who lack deep knowledge of a product often team up with a technical expert, sometimes a sales engineer, who joins the presentation to answer questions. O*NET, the US Department of Labor's occupational database, lists reported titles for sales engineers that range from Business Development Engineer to Technical Marketing Engineer, a useful reminder that titles vary. Read the duties, not just the title.

• SDR or BDR: researches prospects, sends first messages, qualifies interest and books meetings for the sales team.
• Account executive (AE): runs discovery calls and demos, writes proposals, negotiates and closes.
• Account manager: looks after existing customers, renewals and add-on purchases.
• Customer success manager (CSM): helps customers adopt the product and reach their goals, which makes the renewal easier.
• Sales engineer or solutions architect: handles technical discovery, demos, proofs of concept and detailed product questions.

SDR and BDR: what does the day look like?

GitLab, a remote company that publishes its job descriptions in a public handbook, separates the two titles neatly. Its SDRs are focused on inbound leads, meaning people who have already shown interest, while its BDRs work on outbound prospecting, contacting people who haven't. Plenty of companies use the two titles the other way round or interchangeably, so check what the listing describes.

A typical day mixes research and outreach: building a list of target companies, finding the right people inside them, writing short personalised emails and LinkedIn messages, making calls and logging every touch. GitLab's BDR description asks for a variety of touches, by call, email and social media, on every prospect in an assigned territory, all tracked in Salesforce.

How success is measured

The measures are about creating opportunities rather than closing them. GitLab names three performance indicators for these roles: sales accepted opportunities against goal (meetings the sales team agrees are worth pursuing), pipeline generated, and initial qualification meetings. Other teams often add meetings booked, meetings actually held, reply rates and the share of meetings that turn into real opportunities.

Evidence you can show

• Writing: a short, specific cold email is the core skill, and GitLab's SDR hiring process ends with a final writing assessment.
• Voice and video confidence: a recorded mock call or voicemail of a couple of minutes.
• Organisation: proof from any earlier job that you can work through a list, follow up on schedule and keep tidy notes.
• Curiosity about a market: a one-page account plan for a company you would like to prospect.

Account executive: what does running a deal involve?

An AE owns an opportunity from the first serious conversation to signature. The work is discovery calls to understand the buyer's problem, tailored demos, finding out who signs off, proposals and pricing, negotiation, and keeping the forecast honest. GitLab's enterprise AE description spells out the paperwork side: document the buying criteria, the buying process and next steps with owners, and ensure pipeline accuracy. It also expects AEs to discuss business issues with prospects and turn them into a formal quote, written proposal or presentation.

Success is usually closed revenue against a quota, with supporting measures such as win rate, average deal size and how accurate your forecast turns out to be. Those figures depend so much on product and market that they only mean something within one company. GitLab's senior AE levels, for example, ask for consistent results and overachievement of quota alongside strong presentation skills.

Evidence for AE roles is a record of closing: quota attainment in an earlier sales job, deals you ran end to end, or, outside sales, times you persuaded a client to buy, renew or upgrade. Expect to present during hiring. GitLab's enterprise AE process includes a mock presentation to a panel of three interviewers, and many companies use a role-played discovery call instead. Remote AEs run nearly every meeting on video, so the demo, the follow-up email and the written proposal carry extra weight.

Account manager or customer success manager: what's the difference?

Both work with customers who have already bought, and the line between them moves from company to company. A common split is that the account manager owns the commercial relationship, such as renewals, upgrades and extra seats, while the CSM owns adoption, making sure the customer gets enough value that renewing is an easy decision. GitLab's mid-market account manager description includes managing the renewal process and exceeding renewal goals, while its CSM team is accountable for customer adoption, measurable outcomes, customer satisfaction and advocacy.

Day to day, that means onboarding calls, regular check-ins, business reviews with the customer's managers, chasing support issues internally, and spotting both accounts at risk and accounts ready to buy more. GitLab expects its CSMs to translate product usage data into actionable advice for customers, so comfort with dashboards and spreadsheets helps.

How success is measured

• Renewals kept and churn (customers lost) across the accounts you own.
• Expansion: upgrades, added users or new products sold to existing customers.
• Adoption or health scores built from how customers use the product.
• Customer satisfaction scores and how many customers are happy to serve as references.

Good evidence comes from any job where you kept clients happy over months, not minutes: a support role with strong satisfaction scores, an agency role managing retainers, or teaching and coaching with repeat clients. Prepare one story about winning back an unhappy customer and one about growing an account.

Sales engineer: when does the technical case matter?

BLS describes sales engineers as people who sell business products or services, such as software, that require technical expertise. Their listed duties include preparing and delivering presentations that explain technical products, working out customer requirements with engineers, and helping customers troubleshoot. In software companies the same job is often called solutions engineer, solutions architect or pre-sales consultant.

The day revolves around technical discovery calls, tailored demos, proofs of concept and written responses to buyers' requirements, including requests for proposals (RFPs), which O*NET lists among sales engineer tasks. GitLab's associate solutions architects engage with customers both onsite and remotely, run product demonstrations and support proof-of-concept work. Their measures are a subset of sales targets: GitLab names new and growth bookings and sales efficiency as the key priorities.

Evidence is technical credibility plus clear explanation: a recorded demo of a tool you know well, an architecture diagram you can talk through, or a certification in the product area. BLS notes that candidates without a degree sometimes qualify through sales experience combined with technical experience or training, a route open to developers, testers and technical support staff.

What changes when the sales job is remote?

The selling itself is the same, but the medium changes, and that rewards some habits more than others.

• Written prospecting carries the load. With no office floor or trade show, your first impression is usually an email or LinkedIn message. GitLab asks its sales development staff for strong writing skills and excellent written and spoken English.
• Demos happen on video. Screen sharing, clear audio, a tidy desktop and a backup plan for a dropped connection become part of the job.
• The CRM (customer relationship management system) is your manager's window into your work. Nobody overhears your calls, so activity and pipeline are judged from what you log, which is why GitLab's BDR roles ask for exceptional Salesforce hygiene.
• Territory decides your hours. Covering North America or Europe often means working into the Indian evening to overlap with prospects; our guide to async work and time zones explains how to plan for that.
• Admin doesn't disappear. BLS notes that sales representatives also analyse sales statistics, prepare reports and handle administrative duties.

Which sales role should you start with?

Choose based on what you already have evidence for, not on the title that sounds most senior.

• No sales experience, a strong writer and comfortable hearing no: SDR or BDR. GitLab's stated path runs from SDR to BDR, after which people interview for roles such as inside sales and account executive for small and mid-sized businesses (SMB).
• Customer support, client servicing or teaching background: customer success or account management, where patience and follow-through count for more than cold outreach.
• Technical background in development, testing, IT support or data: sales engineering or solutions roles, sometimes after a period in technical support or as a CSM on a technical product.
• Already closing deals at an Indian business-to-business company: AE roles, where you can show results in rupees and explain what you sold, to whom and over what sales cycle.

Whichever you pick, lead your CV with results someone could check, such as meetings booked, renewals kept or deals closed. Our résumé guide covers how to present them, and the LinkedIn guide matters more than usual here, because prospects and hiring managers will both look you up.

A practice kit for your first remote sales application

1. Write a mock outreach sequence. Pick a real company you would sell to and one buyer role, then write four touches spread over two weeks: a first email, a follow-up that adds one new idea, a LinkedIn note and a polite closing email. Keep each short enough to read on a phone and tie it to something specific about that company.
2. Record a short demo. Choose a free tool you know well and record a five-minute screen-share demo for an imagined buyer: their problem, the three features that solve it and a clear next step. Watch it back and cut the filler.
3. Get hands-on with a CRM. Salesforce describes Trailhead as its free online learning platform, and modules such as Sales Pipeline Basics explain how a pipeline is built and managed.
4. Run your job search like a pipeline. Track each application as an opportunity with a stage and a next step. It is genuine CRM practice and gives you a concrete example to discuss in interviews.
5. Rehearse the role-play. Practise a discovery call or mock presentation with a friend on video, then review the recording before the real interview.