Forward Deployed Engineer / Implementation Engineer
Free to start · No card · 5 credits the moment you sign up
Job description
Forward Deployed Engineer / Implementation Engineer
Remote, Montreal, QC, Canada. Full time.
Must be located in QC, Canada. Travel up to 25 percent: team meetings, customer site visits when a customer asks for one, and occasional industry events.
About CWS
CWS builds and runs the security and cloud infrastructure companies depend on. We design, deploy, tune and operate production platforms across Montreal, QC, Canada: SIEM onboarding and detection engineering, cloud identity and access, edge and firewall platforms, security programs, data protection, and secure cloud environments built as code. We do not hand off at go-live. We run the managed service on top of what we build, so the systems we deploy stay tuned and defensible.
We work through technology partners and directly with customers. Every engineer here works directly with the founders and owns a real customer outcome from day one.
Role & Responsibilities
As a Forward Deployed Engineer, you own the customer engagement end to end: you scope the work, architect the solution, build and configure it, prove it holds up, and hand over a system the customer's team can run without you. You are both the engineer and the person accountable for the result.
You carry one to three engagements at a time, spanning cloud and infrastructure delivery (AWS, Google Cloud, infrastructure as code, networking, edge and firewall platforms) and security delivery (tool implementation, tuning, and assessments).
- Deploy, configure and integrate security and cloud platforms in customer environments, and prove they work before you hand them over.
- Plan and run your engagements: milestones, dependencies, acceptance criteria, and a weekly status the customer can read in two minutes.
- Raise risks early, and bring options and a recommendation with them.
- Write the as-built documentation and runbooks, run the knowledge transfer, and train the customer's team so they can operate without you.
- Contribute to managed-service work on platforms we run: health checks, tuning, and renewal assessments.
- Help scope new work: effort estimates, technical input to statements of work, and kickoff material.
- After each engagement, write down what changed between the plan and what it took, and turn it into an asset the team reuses.
Qualifications
- Three to five years in security engineering, DevSecOps or platform engineering, or software engineering, including at least one year delivering into environments you did not own.
- Hands-on AWS, and working knowledge of Azure or Google Cloud: identity, networking, compute, storage, logging.
- Networking you can troubleshoot: DNS, routing, VPN, firewalls, load balancing, TLS.
- Infrastructure as code (Terraform or similar) and version control as daily habits.
- Python or TypeScript at a level where you build your own tooling.
- Security fundamentals across identity, endpoint, network and cloud posture, and the ability to explain a finding to a non-technical owner.
- Clear written and spoken English. You write your own status updates, as-builts and runbooks.
- Comfort working on your own. You take an ambiguous problem, break it down, decide what to build and what to configure, and ask for help early when you need it.
You do not need to match every line. If you meet most of them and you learn fast, apply.
Nice to have:
- Certifications: a cloud provider certification (security specialty preferred), a firewall or edge platform certification, a SIEM or security operations certification, CISSP, Security+ or a GIAC certification, or Kubernetes.
- Delivery experience in a consulting, professional services or managed security firm, where you owned a schedule and a customer relationship.
- French, spoken and written. Part of our delivery is in French.
- Detection engineering or security automation.
- Compliance context: SOC 2, ISO 27001, HIPAA, PCI DSS.
Compensation and benefits
- Competitive salary
- Unlimited paid time off
- Dedicated mental health days
- Performance bonuses
- Learning and certification stipend
- Home office equipment
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for CWS. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.