The Christian programmer, the AI researcher, the product manager at a software company: these people often feel a tension that others around them do not. The secular world says technology is inherently progressive and good. Some Christians say it is inherently dangerous and suspect. Neither position is adequate, and neither is rooted in a serious reading of what Scripture actually teaches about work, creation, and human purpose.
There is a better account. And it begins in the first two chapters of Genesis.
The Mandate to Build
"God blessed them and said to them, 'Be fruitful and increase in number; fill the earth and subdue it. Rule over the fish in the sea and the birds in the sky and over every living creature that moves on the ground.'" (Genesis 1:28)
The word "subdue" here is kabash in Hebrew, a strong word that implies active mastery, ordering of something that is currently raw or unordered. This is not a permission slip for exploitation. It is a commission to bring the capacities embedded in creation to order and productive use. Human beings were designed to take the raw material of the world and make something of it.
Genesis 2:15 adds a second layer: "The Lord God took the man and put him in the Garden of Eden to work it and take care of it." The two verbs here are significant:
- Abad, to work or till, implies productive engagement
- Shamar, to keep or take care of, implies stewardship, responsibility, and protection
The creation mandate is not just "build things." It is "build things well, and take responsibility for what you build."
Building sophisticated technology, including artificial intelligence, falls within this mandate. Christians do not need to apologize for working in technology. The work itself, when done with integrity and care, is an expression of the image of God and an answer to the commission given in Eden.
The Vocation of Christian Technologists

A vocation is not just a job. It is a calling that connects daily work to a larger purpose. For Christian technologists, the connection is direct: they have access to some of the most powerful tools humanity has ever created, and they are building systems that will shape how billions of people think, communicate, work, and access information.
That is not a neutral position. It is a position of enormous influence, which means it is also a position of enormous responsibility.
Christian engineers working in AI are not neutral technical contributors. They bring to their work a set of commitments that the field desperately needs:
- They believe human beings have inherent dignity that should not be reduced to data points
- They believe accountability matters and that those who build powerful systems are responsible for their effects
- They believe there are things that should not be optimized, traded, or automated away
- They believe truth is something that corresponds to reality, because reality was made by a God who does not lie
These commitments are not a liability in technology work. They are exactly what responsible technology development requires, and they are underrepresented in the field.
What the Mandate Does Not Authorize
The creation mandate is not a blank check. Genesis 11 records the story of Babel, a project of impressive technical collaboration aimed at making a name for its builders and concentrating human power in a single place. God's response was not admiration for the engineering. It was disruption of a project that had become oriented around human glorification rather than the purposes for which human creativity was given.
The Babel warning is worth taking seriously now. AI systems that concentrate enormous decision-making power in the hands of a small number of companies, without accountability or transparency, bear more than a passing resemblance to the Babel dynamic. The question is "who does this serve, who controls it, and what does it do to those who depend on it?"
Christian technologists are positioned to ask those questions from inside the systems being built. That is part of what the mandate requires. Abad and shamar, building and keeping, are both part of the commission.
Practical Implications for Christian Tech Workers

If you are a Christian working in AI or software, a few things follow directly from this framework.
Your work matters before God. You do not need to compartmentalize faith and code. The quality of your work, the integrity of your design decisions, the care you bring to questions of safety and fairness: these are spiritual acts performed in response to a divine commission.
You have standing to raise concerns that others may not raise. Working in a field does not make you complicit in every use of that field's outputs. The relevant question is whether your own work and the systems you personally build reflect the mandate's obligations: building well, taking care, and refusing to participate in designs that degrade human dignity or concentrate harmful power. You are responsible for your contribution, not for every application of a general technology.




