Enterprise Sales Manager
- .
- Requirements / Qualifications / Skills: The "The Ideal Candidate" section lists many items: "You’ll Likely Thrive In This Role If You Have 2–3 years of sales experience, minimum. This is a hard bar. Have no degree or institution filter - what you've done matters more than where you studied. Have real phone stamina and are comfortable maintaining a high-volume calling motion every day. Know how to prioritise a large prospect universe: which 50 of 500 companies to work first, and why. Have strong commercial judgement and understand what a deal is worth and what it costs to serve. Are highly organised and disciplined about pipeline management, follow-ups and execution. Communicate exceptionally well in both verbal and written communication. Are comfortable adapting your pitch and approach based on the person, organisation and context. Take strong ownership from first outreach through closing and first transaction. We hire exceptional people for their craft, not travel enthusiasts. We solve hard problems that happen to touch global travel and government infrastructure."
These are requirements/qualifications/skills. We could split into Requirements (experience, phone stamina, prioritisation, commercial judgement, organisation, communication, adaptability, ownership) and Skills maybe overlapping. But we need to avoid thin sections. Perhaps combine into one section "Requirements" or "Qualifications". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have content for Requirements/Qualifications/Skills. Could make a single section "Requirements" containing all. Or split into Requirements and Skills but that may be thin. Better to have one section "Requirements" with all points.
- Benefits: The section "What You Can Expect Atlys is built by a small team..." includes bullet list: "Competitive compensation and equity so you participate in the value you help create. Comprehensive health insurance covering you and your family, plus annual preventive health check-up on us. A thoughtful leave policy with paid time off and company holidays, because great work also requires real time off. Lunch, high tea and dinner at the office, so the basics are taken care of while we build together. Learning & development credits to invest in courses, books, conferences and tools that help you get better at your craft. Relocation support to make moving closer to the team as seamless as possible. Great tools to do your best work, including high-spec equipment and software. An office designed for more than just work, with pickleball, table tennis, PlayStation, an arcade game room, an F1 simulator and even a full flight simulator." Also mention values etc but those are not benefits. So we have Benefits content.
- Pay: Not explicitly mentioned; there is "Competitive compensation and equity" but that's under Benefits. No specific pay numbers. So we should NOT create Pay section because no specific pay stated.
- Schedule: Not mentioned. So no Schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Benefits.
We need to use
for each heading. Use
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. The intro "About Atlys" maybe considered boilerplate? It's about company mission. Might be considered part of About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The "About Atlys" is not a heading but could be considered part of About the role? The posting includes "About Atlys" then "Our mission is to enable...". That is company overview. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that content somewhere. Where? Could be part of About the role section as prose before the role specifics. Or we could have a separate section "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit company overview under About the role perhaps as a preamble. Thus About the role section will contain the company mission paragraph plus the role description paragraphs. We need to not repeat the job title as heading. No job title given explicitly; we can ignore. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none visible besides maybe "Read them before you apply." That's application instruction? It says "Read them before you apply." That's about values. Might be considered application instruction? It's about reading values before apply. Might be considered boilerplate? Probably we should remove lines like "Read them before you apply." and "If this environment energizes you, you’ll probably thrive here. If it doesn’t, it’s better to know that upfront. Come build the intelligence layer for global travel". That's more motivational but maybe considered part of Benefits? Not exactly. It's more about culture. Could be considered part of Benefits? Not exactly. Might be considered part of "What You Can Expect". Actually after benefits they talk about values and then "Read them before you apply. If this environment energizes you, you’ll probably thrive here. If it doesn’t, it’s better to know that upfront. Come build the intelligence layer for global travel". That's a call to action, which is application instruction. Should be removed. Thus we will keep only substantive content: company mission, role description, responsibilities list, ideal candidate list, benefits list. Now format. About the role:
About the role
thencontaining mission and role description paragraphs. We need to ensure we don't lose any detail. Let's extract mission paragraph: "About Atlys Our mission is to enable every person on Earth to travel freely. Travel should feel exciting. Instead, too much of it is still defined by paperwork, uncertainty, and processes that were never designed for travellers. Atlys is changing that. We’re building an AI-first platform that removes friction and uncertainty from travel. To date, we’ve processed visas for 1M+ travellers across 127 countries. But we’re still early." Then role description paragraphs: There are multiple paragraphs under "The Role". Let's combine them. First "The Role Our partners - card networks, banks, airlines, travel platforms, fintechs - are mostly many times our size. The job is to get a decision-maker to take the call, then build a construct that works commercially for both sides. The second part is the hard part. A visa is a low-frequency purchase. A partnership only works if you find the moment in the partner's own customer journey where we belong, and structure the economics so they have a reason to care. There's no playbook." Second "The Role Most companies handle business-travel visas badly — an office manager or travel desk stitching together agents and embassy appointments, nobody owning it until something breaks three days before a flight. Atlys for Business fixes that. The bar is 30 new accounts live every month. You won't dial blind. We process visas for over a million travellers, so we already know which companies send people abroad on business. That's your list. The job is working it in the right order. You source, pitch, close and onboard. Ops and support take the day-to-day after that; you keep the commercial relationship and grow it." Third "The Job Convert 30 new organisations into active Atlys for Business customers every month. Make 50+ calls a day, alongside email and LinkedIn outreach. The volume isn't optional. Run high-volume demos and keep your calendar consistently filled. Adapt your pitch to every prospect - a travel desk at a 5,000-person manufacturer and an EA at a 200-person startup need different conversations. Own onboarding through the first transaction - signed but never booked isn't closed. Maintain a disciplined, transparent pipeline with clear next steps and no surprises. Grow commercial relationships with customers after they go live." We could treat the third as responsibilities, but we already have responsibilities list. However the third includes same items as responsibilities list. To avoid duplication, we should not duplicate content. The responsibilities list we will output as
- . So we should not repeat those sentences in prose. So we need to extract only the role description that is not covered by responsibilities list. The first two paragraphs are about role context. The third is essentially responsibilities list. So we will include first two paragraphs in About the role prose.
Thus About the role prose: mission paragraph + first two role paragraphs.
Now Responsibilities: we will list the items from the third paragraph as bullet list.
Now Requirements: we need to extract from "The Ideal Candidate" section.
Let's list each bullet:
- You’ll Likely Thrive In This Role If You Have 2–3 years of sales experience, minimum. This is a hard bar.
- Have no degree or institution filter - what you've done matters more than where you studied.
- Have real phone stamina and are comfortable maintaining a high-volume calling motion every day.
- Know how to prioritise a large prospect universe: which 50 of 500 companies to work first, and why.
- Have strong commercial judgement and understand what a deal is worth and what it costs to serve.
- Are highly organised and disciplined about pipeline management, follow-ups and execution.
- Communicate exceptionally well in both verbal and written communication.
- Are comfortable adapting your pitch and approach based on the person, organisation and context.
- Take strong ownership from first outreach through closing and first transaction.
- We hire exceptional people for their craft, not travel enthusiasts.
- We solve hard problems that happen to touch global travel and government infrastructure.
We need to preserve all substantive information. Some sentences are somewhat fluff but we keep.
We can format as
- each. Now Benefits: list from "What You Can Expect" section. List: - Competitive compensation and equity so you participate in the value you help create. - Comprehensive health insurance covering you and your family, plus annual preventive health check-up on us. - A thoughtful leave policy with paid time off and company holidays, because great work also requires real time off. - Lunch, high tea and dinner at the office, so the basics are taken care of while we build together. - Learning & development credits to invest in
- . So we should not repeat those sentences in prose. So we need to extract only the role description that is not covered by responsibilities list. The first two paragraphs are about role context. The third is essentially responsibilities list. So we will include first two paragraphs in About the role prose.
Thus About the role prose: mission paragraph + first two role paragraphs.
Now Responsibilities: we will list the items from the third paragraph as bullet list.
Now Requirements: we need to extract from "The Ideal Candidate" section.
Let's list each bullet:
- You’ll Likely Thrive In This Role If You Have 2–3 years of sales experience, minimum. This is a hard bar.
- Have no degree or institution filter - what you've done matters more than where you studied.
- Have real phone stamina and are comfortable maintaining a high-volume calling motion every day.
- Know how to prioritise a large prospect universe: which 50 of 500 companies to work first, and why.
- Have strong commercial judgement and understand what a deal is worth and what it costs to serve.
- Are highly organised and disciplined about pipeline management, follow-ups and execution.
- Communicate exceptionally well in both verbal and written communication.
- Are comfortable adapting your pitch and approach based on the person, organisation and context.
- Take strong ownership from first outreach through closing and first transaction.
- We hire exceptional people for their craft, not travel enthusiasts.
- We solve hard problems that happen to touch global travel and government infrastructure.
We need to preserve all substantive information. Some sentences are somewhat fluff but we keep.
We can format as
- for any list of duties/requirements/benefits. Use