JOB: Video Engineer Lead- (Video Compression Algorithm, H.264) - Austin, TX

Lead Video Engineer -  (Video Compression Algorithms, H.264-HD)

Location:  Austin, TX  (Full Time/employee)-

Contact:
Dee Dee Dial, Sr. Exec/Technology Recruiter
Pedley-Richard & Assoc.
512/418-3260
Email:   dddial@pedley-richard.com
(Note: all resumes are submitted in confidence and will NOT be forwarded to 
any client company without the expressed consent of the individual.)

Company Profile:
Our client is a innovative and successful pre-IPO provider of new to market 
video communications systems.  This is an opportunity to work with leaders 
who have had record success of setting new trends in video communications 
technology and successfully delivering several generations of new product to 
market. You will be part of a exciting, fast-paced, start-up organization 
that offers the stability of backing from some of the leading venture 
capital firms in the country and the leadership of experienced entrepreneurs 
and managers who have tenured background in successful start up 
organizations.  This is your chance to be part of the beginning stages of 
technology that will set a new standard in video communications industry.


Responsibilities:
As Video Algorithm Engineer and hands on Team Lead you will participate in 
the architecture, analysis, design, development and implementation of the 
Video capabilities in a next generation video communication system. You will 
have the opportunity to work with technical leaders and innovators in the 
industry. You will be responsible for keeping your team on track and focused 
on delivering our product in a timely fashion. As team lead, you will guide 
and review designs, assign work, help define schedules, review bug reports, 
mentor team members, and develop every aspect of the project yourself.

You will have excellent communication skills and the ability to work both 
independently and as a member of a small team. You will have the desire to 
work in a fast paced environment, developing cutting edge technologies in a 
professional engineering environment.

Qualifications:

.8+ years of experience and intimate knowledge of multiple video compression 
algorithms including H.261, H.263, and especially H.264 (H.26L)

.Significant experience developing validation test suites for those 
algorithms

.Experience should also include expert level ability developing SW 
validation test suites for the validation of HW implementation

.Experience fine tuning those algorithms for maximum quality in a real time 
systems

. SW: Expert level C & C++, Assembly, Real Time Language
. Protocols: H.261, H.263, H.264 (H.26L)
. Education: Undergraduate Degree required, Graduate degree preferred, or 
equivalent years of industry experience considered.
. Interest and ability to be a full time employee and reside in Austin, TX


Dee Dee Dial, Sr. Executive/Technology Recruiter
Pedley-Richard & Assoc., Inc.
Direct  dial:  512/418-3260
Email:  dddial@pedley-richard.com
7719 Wood Hollow Dr., #216
Austin, TX  78731
www.pedley-richard.com

Strategic recruitment solutions for the technology world

"
Education: Undergraduate Degree required, Graduate degree preferred, or

equivalent years of industry experience considered.
"

That's interesting: how many years of industry experience make up a
undergraduate or graduate degree?

Regards,
Andor

On 27 Apr 2005 04:53:00 -0700, Andor <an2or@mailcircuit.com> wrote:

> "
> Education: Undergraduate Degree required, Graduate degree preferred, or
>
> equivalent years of industry experience considered.
> "
>
> That's interesting: how many years of industry experience make up a
> undergraduate or graduate degree?
>
> Regards,
> Andor


Believe it or not, some people acquire knowledge by reading, working
with the technology, and solving real-world problems.  Sort of like
they do in school, only with a more practical focus.  Reality TV for
education, only better.

Cheers,
Larry G.

On Wed, 27 Apr 2005 12:30:04 -0500, the renowned Larry G
<no.one@nowhere.com> wrote:

>On 27 Apr 2005 04:53:00 -0700, Andor <an2or@mailcircuit.com> wrote:
>
>> "
>> Education: Undergraduate Degree required, Graduate degree preferred, or
>>
>> equivalent years of industry experience considered.
>> "
>>
>> That's interesting: how many years of industry experience make up a
>> undergraduate or graduate degree?
>>
>> Regards,
>> Andor
>
>
>Believe it or not, some people acquire knowledge by reading, working
>with the technology, and solving real-world problems.  Sort of like
>they do in school, only with a more practical focus.  Reality TV for
>education, only better.
>
>Cheers,
>Larry G.

Sure, it happens, but it's pretty rare, IMHO, for people to acquire
deep theoretical knowledge that way. Perhaps Andor's point is that the
two are virtually orthogonal requirements. 


Best regards, 
Spehro Pefhany
-- 
"it's the network..."                          "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com

"Andor" <an2or@mailcircuit.com> wrote in message 
news:1114602780.508431.113430@l41g2000cwc.googlegroups.com...
> "
> Education: Undergraduate Degree required, Graduate degree preferred, or
>
> equivalent years of industry experience considered.
> "
>
> That's interesting: how many years of industry experience make up a
> undergraduate or graduate degree?

the US government seem to think it is 10 years.

tim

"Andor" <an2or@mailcircuit.com> wrote in message 
news:1114602780.508431.113430@l41g2000cwc.googlegroups.com...
> "
> Education: Undergraduate Degree required, Graduate degree preferred, or
>
> equivalent years of industry experience considered.
> "
>
> That's interesting: how many years of industry experience make up a
> undergraduate or graduate degree?
>

It depends on if one has 10 years of real experience or only 1 year of 
experience 10 times.

Delete the "years of" and it makes more sense.  Then, an interviewer might 
ask how did you get that equivalent experience?  And, secondarily, how many 
years did it take *you* to get that "equivalence".

Fred 

Spehro Pefhany wrote:
> On Wed, 27 Apr 2005 12:30:04 -0500, the renowned Larry G
> <no.one@nowhere.com> wrote:
> 
> 
>>On 27 Apr 2005 04:53:00 -0700, Andor <an2or@mailcircuit.com> wrote:
>>
>>
>>>"
>>>Education: Undergraduate Degree required, Graduate degree preferred, or
>>>
>>>equivalent years of industry experience considered.
>>>"
>>>
>>>That's interesting: how many years of industry experience make up a
>>>undergraduate or graduate degree?
>>>
>>>Regards,
>>>Andor
>>
>>
>>Believe it or not, some people acquire knowledge by reading, working
>>with the technology, and solving real-world problems.  Sort of like
>>they do in school, only with a more practical focus.  Reality TV for
>>education, only better.
>>
>>Cheers,
>>Larry G.
> 
> 
> Sure, it happens, but it's pretty rare, IMHO, for people to acquire
> deep theoretical knowledge that way. Perhaps Andor's point is that the
> two are virtually orthogonal requirements. 
> 
> 
> Best regards, 
> Spehro Pefhany

I was lucky when I workd for the Navy.  I was working for an ONR sponsor 
on a program that required a bit of theoretical knowledge and at the 
same time going to grad school part time.  The work and school 
dovetailed very nicely. The theory was for lack of a better term, 
practical.

Spehro Pefhany wrote:


> Sure, it happens, but it's pretty rare, IMHO, for people to acquire
> deep theoretical knowledge that way. Perhaps Andor's point is that the
> two are virtually orthogonal requirements. 

I got my B.E.E. when the director of the lab I worked in said, "You're 
doing an engineer's work, you ought to get paid like on. Go get a 
degree." Two years later, one of the job offers I got was less than what 
I had been making when he pushed me out, but the one I took ended me up 
as an MTS at RCA Labs. I never got another degree, but I had a couple of 
Ph.D.s who worked as my assistant at one time or another. The part I'm 
proud of is two of my technicians becoming full-fledged MTSs.

Jerry
-- 
Engineering is the art of making what you want from things you can get.
�����������������������������������������������������������������������

Stan Pawlukiewicz wrote:

> I was lucky when I workd for the Navy.  I was working for an ONR
sponsor
> on a program that required a bit of theoretical knowledge and at the
> same time going to grad school part time.  The work and school
> dovetailed very nicely. The theory was for lack of a better term,
> practical.

That's a very efficient way of learning, isn't it? I did basically
the same thing. Worked for an oil company, trying to solve a very
practical problem by means of theoretically heavy DSP.

On the plus side, one learns a lot very fast. On the down side,
few other people appear to have similar experiences. So it's
a problem capitalizing on this kind of experience in the long term.
The theoretical people see one's practical experience. The
practitioners see the theoretical side. And the laymen see a
voodoo whitch doctor.

Oh well.

Rune

Rune Allnor wrote:
> Stan Pawlukiewicz wrote:
> 
> 
>>I was lucky when I workd for the Navy.  I was working for an ONR
> 
> sponsor
> 
>>on a program that required a bit of theoretical knowledge and at the
>>same time going to grad school part time.  The work and school
>>dovetailed very nicely. The theory was for lack of a better term,
>>practical.
> 
> 
> That's a very efficient way of learning, isn't it? I did basically
> the same thing. Worked for an oil company, trying to solve a very
> practical problem by means of theoretically heavy DSP.
> 
> On the plus side, one learns a lot very fast. On the down side,
> few other people appear to have similar experiences. So it's
> a problem capitalizing on this kind of experience in the long term.
> The theoretical people see one's practical experience. The
> practitioners see the theoretical side. And the laymen see a
> voodoo whitch doctor.
> 
> Oh well.
> 
> Rune
> 

You never know what portion of your resume will get you an interview.

An agency sent my resume out "shotgun style".
The CEO of a small company saw it and *to quote him* just had to meet 
someone who could demonstrably claim such a strange academic and work 
history. He didn't think I would accept the job. But he did want to meet 
me. Looking back, perhaps I should have taken the job, not because it 
was so great ( it wasn't ), but to work for someone with that attitude.