Associate software engineer - security and compliance at BBD at Data Science Dojo

Role overview

In a world where one overlooked vulnerability can derail entire AI initiatives, security engineers are being asked to do more than ever: anticipate threats, automate compliance, and safeguard trust at scale. With AI adoption surging, our customers demand ironclad security, privacy, and compliance across SOC 2, HIPAA, GDPR, and beyond. We need an Associate Software Engineer – Security and Compliance who can architect frameworks, automate compliance, and embed security into the DNA of our p

Responsibilities

• Design, build and operate production software for security and compliance software.
• Collaborate with product, design, security and engineering partners.
• Improve reliability, performance, testing, automation and documentation.
• Turn customer and operational requirements into maintainable systems.

Qualifications

• Relevant professional software engineering experience in the stated domain.
• Strong systems thinking, communication and software design skills.
• Ability to work effectively in a distributed team.

Technology in this role

• CAN: In a world where one overlooked vulnerability can derail entire AI initiatives, security engineers are being asked to do more than ever: anticipate threats, automate compliance, and safeguard trust at .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Associate software engineer - security and compliance position at Data Science Dojo is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “In a world where one overlooked vulnerability can derail entire AI initiatives, security engineers are being asked to do more than ever: anticipate threats, automate compliance, and safeguard trust at scale. With AI…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the security area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Design, build and operate production software for security and compliance software.”; “Collaborate with product, design, security and engineering partners.”; “Improve reliability, performance, testing, automation and documentation.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Relevant professional software engineering experience in the stated domain.”; “Strong systems thinking, communication and software design skills.”; “Ability to work effectively in a distributed team.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are CAN: In a world where one overlooked vulnerability can derail entire AI initiatives, security engineers are being asked to do more than ever: anticipate threats, automate compliance, and safeguard trust at .. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel.

Benefits

• Remote Americas or worldwide arrangement as stated in the official posting.
• Opportunity to work on software used by technology customers.

About Data Science Dojo

Data Science Dojo provides education and professional training in data science, machine learning, analytics and AI. Its programs include bootcamps, online courses, workshops and corporate learning designed around practical skills and applied projects rather than theory alone.

The organization also publishes technical learning resources and serves both individual learners and enterprise teams. Roles can support instruction, curriculum, software platforms, data products or customer programs. Candidates should check whether the vacancy is a full-time employee, contract mentor or instructor position and confirm the expected teaching, delivery schedule and learner audience in the original posting.

Browse job categories

Related jobs

• Corporate Security Lead, DLP and EDR — Money Forward Vietnam
• Senior Software Engineer, Code Security at GitLab — GitLab
• Staff Software Engineer, Static Analysis at GitLab — GitLab
• Lead Security Engineer, Red Team and Threat Intelligence at Grab — Grab
• Security Engineer at Deepgram — Deepgram
• Senior Security Engineer, Offensive Security at Docker — Docker