上海招聘

Product line:产品线与主要角色定位
1.基于硬件/网络及多种虚拟化技术的Iaas云计算产品中间件系统的开发。
2.负责Service级Middleware开发。

Responsibilities:工作职责描述
1.根据功能说明书设计模块级软件产品。
2.C++/Java开发部署子系统。
3.单元/集成测试。
4.软件维护工作。

Requirements:任职基本要求
1.计算机相关行业本科以上学历，3-5年以上C++编程经验(必须)
2.精通Linux系统下的C/C++编程,良好的编程规范（必须）
3.能力要求（至少熟悉其中两项）（必须）
1）熟悉Linux/Unix，包括内核和系统管理与系统定制
2 ) 熟悉Bash/python等多种开发语言尤佳
3）熟悉虚拟化技术KVM/Qemu/Xen/HP/IBM VM
4）熟悉网络设备如交换机,路由器,防火墙,F5的功能
4. 有面向对象（OO）的设计与开发经验。
5. 良好的英语读写能力
6. 勇于承担责任，良好的团队精神和沟通能力

Additional Requirements:优选要求
1.云计算、虚拟化、IAAS、PAAS经验尤佳。
2.熟悉JAVA编程优先。

应聘者请看清要求，must为必须满足部分，合则约见。

As every software engineer would have known, enterprise business App System is well-designed to be customer-oriented, whose interests can be completely - at least fairly easy to be - handled by the system.

What if looking at it from resource's angle ? Is there any corresponded operation-oriented App System that all resource-faced activity and computation could be well-modeled too ?

Unfortunately, NO.

Such a unbalanced situation raises up big concerns in nowadays Enterprise Resource Pool and App Deliver System - if having one - where the App Computation and App Operation process have not been consistently defined. Please try following questions:
Is your VMWare / IBM / Cisco tool be able to freely launched in the data center ? why not ?
Is your App Resource Network be able to accommodate one more App Instance ? it cannot or simply you are just not sure about it ?
Who to share resource with whom is better ? why ?
How to make sure a bunch of devices, each of which caters for multiple of workloads respectively, are well-configured so that the supported App can be always in good situation ?
Well, I am pretty sure no one can answer them properly without modelling such various of App Computation & Operation processes into an Operation System.

Down to this line, if you agree with me, I'd like to be greeting you - welcome to Next Generation of Resource Pool & App Delivery technology !

By Formal Method that reduces All App Structure & operation & computation process into Meta-data Ontology constructed with Formal Logic and Math integrity, any of App Behavior's semantic can be verified and validated ( during run-time), therefore system always know if " Operation & Computation X, use resource Y, reaching goal Z" - modelling problem resolved !

Now you might be realizing what we are doing:
using abstract machine to infer abstract code( a.k.a. Meta-data ) --> being positive ? --> transforming abstract machine into Virtual & physical system and Meta-data substantial source-code or device commands --> data center resource & its operation are automatically triggered and modeled as well.

Because Formal Method is so well-known as machine-process-able, so that above verification & validate and transformations are self-run-able without human's interference, which makes critical sense to practical operations because we strongly believe that in future, all data center operations are to be done by source code, but not human's hands.

Are you interested in this ? please feel free to let me know what you want to know.
E-mail: hr@tnsoft.com.cn

Company Quick facts:
* Tech startup - offering next generation of Resource Pool & App Delivery technology to enterprise operation software ( IaaS ) market
* US-found; R&D and marketing operates in Mainland China
* Independent software product vendor, focusing on Bank and Geophysical ( oil ) industry with existing customers segment
* Building and maintaining 20+ R&D elite with high-end tech standards and capability in Shanghai
* Don't be bothered about website please - we don't demonstrate our tech over there
* Tech-oriented company culture, and learning is always mandatory