Senior C# / Azure Developer (AI & API… at Bolder Apps -… · Tashkent

We're hiring a C# developer who can architect and ship production-grade backend systems from day one. This starts as a contract engagement with the explicit intent to convert to full-time. You'll design scalable APIs, manage Azure infrastructure, and integrate AI capabilities directly into the product — not as a side feature, as core architecture. If you've built serious .NET systems on Azure and you've worked with LLMs beyond the tutorial level, we want to talk. Bolder Apps is a product development studio that partners with US-based startups and established companies to build and scale innovative digital products. We specialize in AI-powered development, full-cycle product creation, and engineering team augmentation. Our mission: build bolder, faster, and smarter.

Our Culture & Values (read before applying)

We move fast. We take ownership. We work with AI, not against it. And we expect everyone to bring ideas, not wait for instructions.

There are no daily checklists, no micromanagement, and no corporate politics. Instead, you'll have autonomy, trust, and a team that's always ready to help you grow. At Bolder Apps, impact matters more than titles, and curiosity matters more than seniority.

If you want a place where you can level up fast and actually see your work making a difference — welcome aboard.

Responsibilities:

• Design, build, and maintain high-performance Web APIs using C# and .NET Core — clean architecture, no shortcuts, built to last

• Architect and manage cloud infrastructure on Azure: App Services, Functions, SQL Database, Service Bus, Key Vault, and Entra ID

• Integrate LLMs and AI features directly into the application ecosystem — Azure OpenAI, semantic search, vector databases, embeddings

• Participate in foundational system design decisions with an eye on long-term maintainability, not just the current sprint

• Document codebase logic and API endpoints clearly enough that the next engineer doesn't need to ask you how anything works

• Communicate architectural and AI trade-offs to non-technical stakeholders in plain language, in writing, without being asked twice

• C# and .NET mastery. Advanced proficiency in C# on .NET 6/8+. You write async code naturally, use LINQ without abusing it, and your Entity Framework Core usage won't embarrass you in a code review. You understand OOP and SOLID well enough to apply them, not just cite them.

• Azure ecosystem. You've deployed and managed real applications on Azure — not just followed a tutorial. App Services, Functions, Key Vault, Azure Active Directory/Entra ID. You know what breaks at scale and how to design around it before it does.

• API architecture. Deep understanding of RESTful design, microservices, API gateways, rate limiting, and performance tuning. OAuth2 and JWT aren't concepts you look up — they're things you've implemented, debugged, and secured in production.

• AI integration. Practical experience with LLMs in production: OpenAI API, Azure OpenAI, prompt engineering, semantic search, embeddings, or vector databases like Pinecone or Azure AI Search. You've built intelligent features into a real product, not a demo.

• Product ownership mindset. You build for the long haul. You think about what happens six months after you ship, not just whether the PR passes CI. This is a contract-to-hire role — we're evaluating fit for a permanent position from day one.

• Documentation discipline. You document as you build. API endpoints, architectural decisions, data flows — clear enough that the codebase can be handed off without a knowledge transfer call.

• Proactive communicator. You flag blockers early, explain trade-offs clearly, and don't disappear between check-ins. Async, in writing, with enough context that nobody needs to follow up.

• Contract engagement with a defined path to full-time conversion — not "maybe someday," a real track

• Fully remote, US timezone

• Direct access to decision-makers — no PM layers between you and the people who own the product

• Real architectural ownership from day one — you're not implementing tickets, you're making design decisions

• Tooling budget for APIs, infrastructure, and whatever you need to do the job well

• A peer network of senior engineers and agentic builders working on overlapping projects