You own the system, not the ticket
The engineer who designs a system builds it, secures it, deploys it, and watches it run. If you want an architecture handed to you and a queue to work through, this is the wrong shape of job.
CareersOwn the System,
Own the System,
Not the Ticket
There are no openings listed on this site. That is not a soft no — it means the roles are not posted, not that the inbox is closed. If you build systems end to end and want to do it across 20 disciplines rather than one, write to us with what you have built.
- 20
- Engineering Disciplines
- 15
- Industries Served
- 8
- Stage Delivery Pipeline
The Engineering Bar
You treat security as a design decision
Authentication model, data boundaries, blast radius, audit trail — settled during architecture. An engineer here should be able to say what an attacker would try before anyone schedules a test.
You learn the domain well enough to argue
Requirements arrive from people who know their business and not your constraints. The useful engineer is the one who understands the workflow well enough to say a requirement is wrong, and why.
You refuse to estimate what isn't scoped
Guessing a number to end an uncomfortable conversation is the most expensive habit in this industry. Define the work, then price it — the same rule that applies to the firm applies to you.
You operate what you ship
Observability, scaling, and cost are part of the build, not somebody else's phase. Systems here keep running after launch, and the people who wrote them are the ones watching the telemetry.
You go broad before you go deep
Range across the 20 disciplines matters more than mastery of one framework. Most engagements need a data platform, an identity model, and infrastructure before they need a favourite library.
The Work
What you would actually be building.
The practice covers 20 engineering disciplines applied across 15 industries. Nobody works in one column of this table for long — a hospice charting app needs offline mobile, an identity model, and an audit trail before it needs anything clever.
AI & Intelligence
- AI DevelopmentLLMs · Agents · RAG
- AI AgentsAutonomous · Workflow
Software Engineering
- Custom SoftwareBespoke · Scalable
- SaaS DevelopmentMulti-tenant · API-first
- Enterprise SoftwareMission-critical · Secure
Security & Infrastructure
- CybersecurityRed Team · SIEM · SOC
- Cloud InfrastructureAWS · GCP · Azure
- DevOpsCI/CD · IaC · K8s
Business Systems
- Mobile ApplicationsiOS · Android · PWA
- CRM DevelopmentCustom · Integrated
- ERP DevelopmentFinance · Ops · HR
- AutomationRPA · Workflow · AI
- API DevelopmentREST · GraphQL · gRPC
- Data PlatformsPipelines · BI · ML
- Managed ITMSP · Monitoring · Support
- Security OperationsSOC · Threat Intel
Industry-Specific
- Healthcare TechnologyHIPAA · EHR · HL7
- Logistics TechnologyDispatch · TMS · GPS
- Transportation SoftwareFleet · Routing · ELD
- Government TechnologyMunicipal · Federal
How to apply
No roles are posted, so there is nothing to apply to — only someone to write to. A speculative message that describes real systems is treated the same as a response to a posting would be.
Email [email protected]
One address, no portal, no form that discards your formatting. Put “engineering” somewhere in the subject so it routes to the right inbox.
Lead with what you have built
Systems you designed, repositories we can read, a problem you owned from architecture through production. A list of technologies tells us far less than one system explained honestly, including what you would do differently.
An engineer reads it, not a recruiter
The same people who would work alongside you read the message, which is also why it is worth writing about the engineering rather than about yourself in the abstract.
Before you write
Two pages will tell you more about the day-to-day than any job description could, because they describe the work as it is sold — which is the work as it is done.
How the firm works
Discovery before code, security as a design constraint, and the 8-stage pipeline every system runs through.
The security practice in depth
Offensive testing, defensive architecture, and operations — the standard every other discipline here is held to.
The AI Discovery Center
The tool that turns a described problem into a system definition. Use it on a problem of your own and you will know what the first week here feels like.
No opening to answer? Write anyway.
Tell us what you have built and what you want to build next. Client work goes through the contact form; engineering applications go straight to the inbox below.
Answers
Frequently Asked Questions
Whether roles are open, how to apply when none are posted, and what the firm looks for in an engineer.
Is SoftwarePros hiring?
SoftwarePros does not list open roles on this site. Speculative applications are still welcome: email [email protected] with what you have built, and an engineer reads it. There is no application portal and no requisition list to check — the inbox is the process, and a strong message describing real systems is worth more than a posting to reply to.
How do I apply to SoftwarePros?
Applications to SoftwarePros go to [email protected]. Lead with what you have built — systems you designed, code you can show, problems you owned from architecture through production — rather than a list of technologies. Because no roles are posted, say plainly what kind of work you want and which of the disciplines and industries the firm works in you want to do it in.
What does SoftwarePros look for in engineers?
SoftwarePros looks for engineers who own systems end to end: people who design an architecture and then build, secure, deploy, and operate it. That means treating security as a design constraint rather than a later audit, learning a client's domain well enough to argue with the requirements, and refusing to estimate work that has not been scoped. Breadth across disciplines counts for more than depth in a single framework.
What kind of work would I do at SoftwarePros?
Work at SoftwarePros spans 20 engineering disciplines across 15 industries: AI systems including LLM applications, retrieval-augmented generation, and autonomous agents; custom software, SaaS, and enterprise platforms; cybersecurity from penetration testing through security operations; and cloud infrastructure, DevOps, and data platforms. Every project runs the same eight-stage pipeline, so an engineer sees a system from definition through production.