Technical Lead DevOps & Security
Free to start · No card · 5 credits the moment you sign up
Job description
About US:-
Must-have skills:-
Azure platform security (primary):-
- Microsoft Entra ID (Azure AD): app registrations, service principals, OAuth2 scopes, delegated vs application permissions, On-Behalf-Of (OBO) token flows, consent model, resource-scoped permissions (Exchange App RBAC, RSC-style scoping)
- Azure API Management (APIM): authoring and staging policies, per-client policy keyed on client ID, correlation-ID handling, content-safety and token-limit policies
- Azure networking: NSGs, firewall / egress rules, private endpoints / private connectivity, subnet segmentation
- Azure observability: Azure Monitor diagnostic settings, Log Analytics, Microsoft Sentinel, OpenTelemetry, KQL for validation and evidence queries
Engineering and DevOps:-
- Reading and reasoning about application source code to derive least-privilege scope (which MCP servers, tools, and Graph resources an agent actually calls, read vs write, target resources). This is the load-bearing skill for DC-IAM-1
- Building a shared instrumentation library / SDK (structured event emission, schema conformance, mandatory-by-design)
- CI/CD and staged promotion through environments (DEV to UAT), infrastructure-as-config discipline
- Comfort with a native-first, GA-only stance: prefer existing generally-available Azure controls over custom code; no preview-tier dependencies
Security engineering practice:
- Default-deny and least-privilege as defaults
- Fail-closed design (a control failure must never become a bypass)
- Proving enforcement with a negative test (the disallowed path is shown to be blocked, not just the allowed path working)
- Producing audit-grade evidence: before/after permission exports, allow/deny matrices, tamper/bypass tests, control-design and procedure writeups
Nice to Have:-
- PlainID or another externalized policy decision point (PDP) / policy-based access control
- AI agent platforms, LLM gateways, MCP (Model Context Protocol) hubs and connectors
- LangSmith or similar LLM tracing tools Postgres (the MCP hub registration / scope model runs on it)
- Prior work in a regulated / financial-services environment and familiarity with control-audit expectations (design gates, ARB / TRC / SOC sign-off)
- Guardrail and content-safety tooling (Azure Content Safety, Prompt Shields, Groundedness)
Working conditions and expectations
- Ground rules: native-first and GA-only; default-deny; fail closed for high-risk; one correlation ID end to end; confirm before changing shared platform config (APIM, network, identity changes affect every agent, so stage in DEV/UAT and validate before handoff)
- Release model: build and stage each control through DEV then UAT, complete positive and negative validation and sign-off at UAT, then hand off to the client, who promotes to PROD through their own change management
- Cadence: two-week sprints; MVP (audit-defensible, may be manual or lean on an existing process) for 7 of 8 controls by 9/25, then hardening to fully operational with evidence by mid-November
- Collaboration: coordinate with client platform (Calvin's team), Cloud (network segmentation), and SecOps (dashboards, log-schema ingestion); design gates reviewed by ARB / TRC / SOC before UAT-to-client handoff
- The real floor on speed is the DEV-to-UAT promotion cadence and per-control validation, not coding time. We build with AI coding agents assisting, so mechanical authoring compresses; the validation and sign-off floor does not
What success looks like:-
- 7 of 8 platform controls at a minimally defensible (audit-holds-up) state by 9/25, DC-OBS-9 shortly after
- Each control shipped with the three-artifact trio: control design, documented procedures, and a test plan with evidence including the negative test
- Full McKinsey-built set hardened to fully operational with evidence by mid-November
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Srijan Technologies. 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.