Delivery Manager (Software Development) Offline

Delivery Manager (Software Development)

Location: [Specify remote/hybrid/onsite]
Reports To: Solution Architect & CTO
Experience: •  7+ years in software development or delivery-related roles, with at least 3–5 years managing or leading cross-functional technical execution. 

About the Role

We're hiring a Delivery Manager to ensure our software development efforts stay on track, move forward daily, and meet their goals with precision. You’ll coordinate tasks across teams, track progress, and take accountability for execution — participating from whiteboard concept to release, and beyond into patching and evolution.

This is a hands-on operational role with room to grow into Product Ownership, but always under close supervision of technical leadership.

What You’ll Do

• Manage daily execution of multiple development streams.
• Break down work, assign tasks, and keep delivery pipelines moving.
• Maintain clear, updated status on progress, blockers, and output quality.
• Review and verify output (AI tools welcome), ensuring alignment with goals.
• Interpret goals from Solution Architects and turn them into detailed team action.
• Track and support releases, patches, and ongoing product evolution.
  
   

Who You’ll Work With

• Full Stack Engineers
• DevOps, DB, and Integration Specialists
• Front-End and Back-End Developers
• Technical Leadership 

Skills & Experience Needed

• 7+ years in software development or delivery-related roles, with at least 3–5 years managing or leading cross-functional technical execution. 
• Background as a lead developer is a strong advantage.
• Excellent at reading, writing, and organizing technical documentation.
• Confident managing software delivery cycles, timelines, and quality.
• Solid understanding of CI/CD pipelines — how they work, how to leverage them for delivery speed and quality. (Execution responsibility lies with DevOps.)
• Familiar with cloud services (AWS, Azure).
• Exposure to .NET Core, VueJS, PostgreSQL, MongoDB is a plus.
• Understands the nuances and trade-offs between monolith, microservice, and headless architectures.
• Hands-on understanding of integration work between systems and services, including nuances between remote (API-based) and local (cloud-premise) integrations.
• While we have established delivery practices, we are open to enabling proven workflows, tools, or processes the candidate is experienced with — provided they fit into our delivery and governance models.

Don’t Apply If

• You’re viewing this role as a springboard to higher-title roles — this position is about delivery and execution, not title collecting or strategic posturing.
• You prefer talking over doing, focus on appearances, or rely on presentation over output.
• You see documentation as a formality instead of a core working tool.
• You’re primarily interested in project management-style coordination — this is deeper and more technical.
• You're a meeting dweller — we maintain a strict culture of minimal, focused meetings, and expect progress to happen in code, documents, and real outputs, not calendar time and broad-brush statements.

Why This Role?

This role is for people who like building real things and ensuring they ship, evolve, and survive. You’ll stay close to code, real work, and outcomes. Product Owners in our company do eventually take on serious responsibility over live products — but only after proving their ability to deliver and maintain them effectively.

Why This Role Matters?

This is a delivery-critical role, not a support or coordination function. Your impact is visible in shipped software, working systems, and team clarity. If you thrive on clarity, ownership, and real outcomes — this is a fit.

To Apply

Please send the following directly (no need for LinkedIn links or cover letters):

• A concise summary of your experience managing or driving delivery in software teams. Focus on what was shipped and how you helped make it happen.
• One paragraph describing a real-world situation where you helped unblock or push through a delivery issue involving multiple teams or disciplines. Include your role, the context, and the outcome — keep it specific and short.
• (Optional but encouraged) A sample of documentation, task breakdown, or roadmap planning that you authored or led.
• Your CV or equivalent document listing work history and projects.

Important: We’re interested in how you work, not how you present yourself. Keep it clear and to the point — substance over style.