Any
P45k-P90k/month, depending on experience
TBD
Jun 6, 2026
# PAY
Starting monthly compensation in PHP, based on experience, proof of work, expected weekly hours, and fit.
We are cost-conscious because we are still early-stage, but we will pay fairly for someone who can actually solve the right problems.
This may start part-time or ramp up over time depending on workload, performance, and mutual fit.
# ROLE TYPE
Remote contractor role. Long-term opportunity for the right person.
# COMPANY
Atlas Cybertech
---
# ABOUT THE COMPANY
Atlas Cybertech is a Canadian AI automation and systems company building internal platforms, CRM infrastructure, automation workflows, and operational systems.
We are early-stage and moving quickly toward revenue. That means we need to get our baseline systems live fast, without creating a fragile mess that breaks later.
Good-enough, working systems are better than perfect systems that never launch. But “good enough” still needs to be clear, testable, and maintainable.
We are not looking for AI hype, random tool-stacking, or “automate everything” thinking.
We are looking for someone who can help us build practical MVP systems quickly, especially around GoHighLevel, AI-assisted workflows, no-code/low-code tools, automations, integrations, and internal operations.
---
# ROLE SUMMARY
This is a *GoHighLevel-heavy role.*
GoHighLevel is one of the most important platforms in our business, so you must have real hands-on GHL experience.
This role is not GHL-only, but strong GHL ability is central.
You will help build and improve Atlas Cybertech’s internal systems across:
- GoHighLevel
- CRM workflows
- No-code/low-code tools
- Automations
- Forms and intake flows
- System of Record structures
- Internal portals or dashboards
- AI-assisted documentation and SOPs
- Light AI-assisted workflows
- API/webhook-based integrations where needed
We are especially interested in someone who is personally excited about AI and actively experiments with AI tools, AI coding assistants, agentic workflows, automation tools, and new ways to use AI to build faster and work smarter.
You do not need to be a full-stack software developer or AI engineer.
You do need to be technically sharp, AI-curious, systems-minded, and capable of figuring things out.
---
# JOB MISSION
Your mission is to help get Atlas Cybertech’s internal operating stack online quickly, then improve it over time.
The first priority is helping us get our core MVP systems configured, connected, tested, documented, and usable.
The goal is to create systems that:
- Reduce manual work
- Help us move toward revenue faster
- Keep data reasonably clean
- Avoid silent failures
- Make workflows easier to understand
- Make automations easier to troubleshoot
- Support future client delivery
- Can be documented, maintained, and handed off later
This role is ideal for someone who naturally asks:
- How do we get this live quickly without making a mess?
- Where is the bottleneck?
- What data should live where?
- What happens if this automation fails?
- What is the simplest working version?
- How can AI help us build, document, or troubleshoot faster?
- How can another person maintain this later?
---
# WHAT YOU'LL WORK ON
You may help with:
- Building and improving GoHighLevel workflows, pipelines, tags, custom fields, calendars, forms, automations, snapshots, triggers, and integrations.
- Setting up and troubleshooting GHL sub-accounts, workflow logic, CRM stages, and client-style account structures.
- Helping structure data in systems like SmartSuite, Airtable, or similar tools.
- Connecting forms, CRM, automations, dashboards, portals, and documentation workflows.
- Building no-code/low-code automations using tools like Make, Zapier, n8n, or similar platforms.
- Troubleshooting broken workflows, triggers, integrations, data-sync issues, and automation failures.
- Creating AI-assisted SOPs, workflow maps, field maps, process notes, Loom walkthroughs, and system documentation.
- Helping build internal systems for hiring, onboarding, lead handling, client intake, follow-up, and operations.
- Supporting AI-assisted workflows where AI helps the process but does not become the source of truth.
- Using AI-assisted light coding where appropriate for small scripts, API calls, webhook troubleshooting, data transformations, or internal workflow helpers.
- Improving system reliability, error visibility, speed of execution, and handoff readiness.
You do not need to be a professional writer, but you do need to care about leaving clear notes and using AI tools to make documentation faster and easier.
---
# IMPORTANT ARCHITECTURE PRINCIPLE
We separate tools by role.
- The System of Record is the main source of truth for important business data.
- GoHighLevel is the CRM and workflow layer.
- Forms are for intake.
- Portals and dashboards are for viewing or interacting with data.
- Automation tools move data and trigger workflows.
- AI tools can assist, but they do not own the process.
GoHighLevel is very important, but it is not automatically the System of Record for everything.
If this distinction makes sense to you, this role may be a strong fit.
---
# REQUIRED EXPERIENCE
You should have real experience with:
- GoHighLevel workflows, pipelines, tags, custom fields, triggers, calendars, forms, and automations.
- GHL troubleshooting and workflow behavior.
- CRM setup, pipeline logic, and automation logic.
- No-code/low-code automation tools such as Make, Zapier, n8n, or similar.
- Basic API/webhook concepts.
- Data fields, records, statuses, permissions, and workflow stages.
- Troubleshooting broken automations or integrations.
- Clear documentation, SOPs, workflow maps, or process notes.
- Explaining technical decisions in plain English.
- Using AI tools to improve speed, research, documentation, troubleshooting, or technical implementation.
You should also have strong personal interest in AI.
Ideally, you already spend some of your own time testing, researching, or experimenting with tools like ChatGPT, Claude, Gemini, DeepSeek, Codex-style tools, AI coding assistants, AI agents, automation agents, or other AI tools.
You do not need to be a full-stack software developer or AI engineer.
You do need to be technically sharp enough to understand workflows, data movement, integration logic, AI-assisted workflows, prompting, failure points, and system handoff.
---
# HIGH-PRIORITY EXPERIENCE
These are especially valuable:
- GoHighLevel snapshots
- GHL SaaS mode
- GHL agency/sub-account setup
- GHL AI features or AI Employee-style workflows
- Client account cloning or snapshot deployment
- Twilio or SMS/calling workflows
- A2P / SMS approval workflows
- AI appointment-setting bots
- AI voice/SMS/chat workflows
- Advanced AI tools, AI coding tools, agentic tools, or automation agents
The more experience you have with GHL and AI-assisted systems, the better.
---
# STRONG BONUS EXPERIENCE
These are not all required, but they are useful:
- SmartSuite
- Airtable
- Fillout
- Softr
- Noloco
- Bubble / Glide / Loveable
- Google Workspace / Google Drive
- Microsoft 365
- Meta /
- Lead forms, UTM tracking, pipeline attribution, or conversion tracking
- KPI dashboards or funnel reporting
- Lightweight JavaScript, Python, JSON, or API troubleshooting
- Experience supporting agencies, consultants, founder-led companies, or service businesses
You do not need to be a media buyer, but paid ads platform literacy is a plus because many systems will connect to lead generation workflows.
---
# THIS ROLE IS *NOT* FOR YOU IF
Please do not apply if:
- You are mainly a VA with light tool experience.
- You only know basic GHL admin tasks.
- You only build funnels and landing pages.
- You only know simple Zapier automations.
- You describe yourself mainly as a prompt engineer.
- You want a CTO, executive, or management title.
- You prefer custom code before checking simpler options.
- You add new tools before understanding the current system.
- You automate unstable workflows without mapping them first.
- You do not like documenting your work.
- You give vague answers like “I can automate everything.”
- You rely on AI-generated answers without real examples.
- You are not personally interested in learning and testing new AI tools.
This role is not for beginners.
---
# WORKING STYLE
This role is a good fit if you are:
- Strong with GoHighLevel.
- Highly interested in AI tools and automation.
- Practical and MVP-minded.
- Systems-minded.
- Strong at troubleshooting.
- Fast, but not reckless.
- Comfortable figuring things out independently.
- Clear in written and spoken English.
- Comfortable working directly with a founder.
- Willing to use AI to speed up documentation and technical work.
- Able to explain tradeoffs clearly.
- Willing to challenge weak ideas respectfully.
- Focused on building systems that other people can maintain later.
We want speed, but not reckless speed.
Good-enough, working systems are better than perfect systems that never launch. But “good enough” still needs to be clear, testable, and maintainable.
---
# AUTHORITY BOUNDARIES
You will be expected to recommend, build, test, troubleshoot, and document systems.
However:
- You do not choose new core platforms without approval.
- You do not turn GHL into the System of Record by default.
- You do not add tools without a clear reason.
- You do not build custom-code dependencies unless clearly justified and approved.
- You do not redesign the core architecture without discussion.
The founder makes final architecture and platform decisions.
Your role is to recommend, execute, document, and improve.
---
# HIRING PROCESS
The hiring process is designed to avoid long live interviews.
Shortlisted applicants may complete:
- A short recorded screening
- A more detailed scenario-based assessment
- One paid practical task if selected as a finalist
- A short 10-15 minute founder call as the final step
The paid practical task is only for finalists. We do not ask many candidates to do unpaid project work.
---
# HOW TO APPLY
At the top of your application, write this exact phrase:
*Atlas Systems*
Then answer the questions below.
Please answer all screening questions directly in your application. Applications that do not answer the questions will not be considered.
Generic AI-written answers will be rejected. Use specific examples from systems you have personally built, fixed, documented, improved, or tested.
---
# APPLICATION QUESTIONS
1. Evidence of Ability
In 3-5 bullet points, describe the strongest evidence of your ability for this role.
Focus on difficult systems, GoHighLevel builds, automations, workflow problems, AI-assisted builds, or technical issues you personally solved.
2. Proof of Work
Share any relevant proof of work.
Examples:
- Loom videos
- Screenshots
- Diagrams
- SOPs
- Documentation
- Portfolio links
- Workflow maps
- Case studies
Do not share confidential client data.
3. Tool and Skill Experience
List the main tools or tool categories you have real experience with.
For each category, mention the specific tools, what you personally used them for, and your approximate skill level from 1-10.
Categories:
- GoHighLevel / CRM systems:
Workflows, pipelines, snapshots, SaaS mode, sub-accounts, automations, troubleshooting
- Automation tools:
Make, Zapier, n8n, Pabbly, Relay, or similar
- No-code/low-code tools:
Airtable, SmartSuite, Fillout, Softr, Noloco, Bubble, Glide, or similar
- AI tools / AI coding / agentic tools:
ChatGPT, Claude, Codex-style tools, Gemini, DeepSeek, AI agents, AI coding tools, automation agents, or similar
- API / webhook / data integration work:
Webhooks, JSON, API calls, data transformations, scripts
- Paid ads / lead-flow systems:
Meta Ads, lead forms, tracking, attribution, conversion events, UTM/source tracking
- SMS/calling systems:
Twilio, A2P, calling/SMS workflows, notification systems
- Business ops tools:
Google Workspace, Microsoft 365, ClickUp, Notion, Slack, Google Sheets
You are not expected to know every tool listed above.
These are examples to help you explain your experience clearly.
GoHighLevel experience is the most important.
Strong AI interest and automation ability are also very important.
The more relevant tools and systems you know, the better.
4. Availability and Starting Compensation
Please provide the following:
- Desired starting monthly compensation in PHP for the first 1-3 months while onboarding, learning our systems, and ramping up.
- Number of hours per week this monthly amount assumes.
- Maximum hours per week you are available to work consistently.
- Target long-term monthly compensation in PHP after the first 1-3 months, assuming strong performance and good fit.
- Usual work window in Philippine time, such as morning, afternoon, evening, late night, overnight, or flexible.
- Earliest available start date.
---
# FINAL NOTE
We are cost-conscious because we are still early-stage, but we will pay fairly for someone who can actually solve the right problems.
We are looking for the best mix of capability, reliability, speed, judgment, AI interest, GHL ability, and reasonable cost.
If you enjoy building systems, solving technical puzzles, experimenting with AI tools, improving workflows, and making operations run better, this role may be a strong fit.